I have the following docker-compose xml  web:   build: nginx/.   container_name: nginx   ports:     - "80:80"   links:     - "openchain"   restart: always wallet:   build: wallet/.   container_name: wallet   ports:     - "81:81"   restart: always   read_only: false   volumes:     - ./www:/usr/share/nginx/html:rw   working_dir: /user/share/nginx/html openchain:   build: openchain/.   ports:     - "8080"   volumes:     - ./data:/openchain/data   restart: always   And the following conf for web and wallet respectively  worker_processes 4;  events { worker_connections 1024; }  http {     server {         listen 80;          location / {             proxy_pass http://127.0.0.1:8080/;              proxy_http_version 1.1;             proxy_set_header Upgrade $http_upgrade;             proxy_set_header Connection "upgrade";         }     } }   and  worker_processes 4;  events { worker_connections 1024; }  http {  server {     listen 81;      location / {         root /usr/share/nginx/html;     } }   }  when I run docker ps I get      05e351c8f8db        openchain_web         "nginx -g 'daemon off"   5 seconds ago       Up 5 seconds        0.0.0.0:80-&gt;80/tcp, 443/tcp    nginx     e7401ea7c5bc        openchain_wallet      "nginx -g 'daemon off"   5 seconds ago       Up 5 seconds        80/tcp, 443/tcp, 0.0.0.0:81-&gt;81/tcp   wallet     40439fdb1c69        openchain_openchain   "dotnet openchain.dll"   5 seconds ago       Up 5 seconds        0.0.0.0:32774-&gt;8080/tcp        openchain_openchain_1   But when I try to access the port openchain_openchain via proxy openchain_web I get the subject error  I'm new to docker so I'm not sure I'm proxying correctly with the nginx  Can you tell me what I did wrong?  P.S. I can access wallet just fine
120419
I have the following docker-compose.yml file:  version: '3' services:     server:         build:             context: ../../             dockerfile: ./packages/website/Dockerfile         command: node /cutting/index.js         environment:             PORT: 8000             NODE_ENV: production         restart: always     nginx:         build:             context: ./             dockerfile: ./nginx/Dockerfile         command: tail -f /dev/null         depends_on:             - server         ports:             - "8000:8000"         restart: always   And the following nginx.conf:  worker_processes 1;  user nobody nogroup; pid /tmp/nginx.pid; error_log /tmp/logs/nginx.error.log;  events {     worker_connections 1024;     accept_mutex off; }  http {     include mime.types;     default_type application/octet-stream;     access_log /tmp/logs/nginx.access.log combined;     sendfile on;      server {         proxy_http_version 1.1; # this is essential for chunked responses to work          listen   80; ## listen for ipv4; this line is default and implied         listen   [::]:80 default ipv6only=on; ## listen for ipv6         client_max_body_size 4G;         server_name frontend;          gzip on;         gzip_disable "msie6";         gzip_vary on;         gzip_proxied any;         gzip_comp_level 6;         gzip_buffers 16 8k;         gzip_http_version 1.1;         gzip_types application/javascript text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;          keepalive_timeout 5;          location /static/  {             alias /static/;         }          location  / {             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;             proxy_set_header Host $http_host;              # UNCOMMENT LINE BELOW IF THIS IS BEHIND A SSL PROXY             #proxy_set_header X-Forwarded-Proto https;              proxy_redirect off;             proxy_pass   http://localhost:8000;         }     } }   If this creates 2 containers how can I get nginx to see the localhost:8000 on the other container?
115072
I have several servers running on the same machine, some with http only, some with both http and https.  There are several server blocks defined in separate files which are included from the main config file.  I have set up a "default" server for http which will serve a generic "maintenance page" to requests that don't match any of the other server_names in the other config files.  The http default server works as expected, it uses the server_name "_" and it appears first in the list of includes (because I have observed that in the case of duplicate server_names across servers, the one appearing first is used).  This works great.  I would expect the same exact server block (only switching "listen 80 default_server" to "listen 443 default_server" and also instead of serving page "return 444") however it does not.  Instead, it appears that the new default https server is actually grabbing all incoming https connections and causing them to fail, although the other server blocks have more appropriate server_names for the incoming requests.  Removing the new default https server will cause semi-correct behavior to resume: the websites with https will all load correctly; but the websites without https will all be routed to the first https server in the include files (which according to the docs, if no "default_server" appears, then the first server block to appear will be "default").  So my question is, what is the correct way to define a "default server" in nginx for ssl connections?  Why is it that when I explicitly set a "default_server" it gets greedy and grabs all connections whereas when I implicitly let nginx decide the "default server" it works like I would expect (with the incorrect server set as default and the other real servers behaving correctly)?  Here are my "default servers".  Http works without breaking other servers.  Https breaks other servers and consumes all.  server {     listen 443 ssl default_server;     server_name _;      access_log /var/log/nginx/maintenance.access.log;     error_log /var/log/nginx/maintenance.error.log error;      return 444; }  server {     listen *:80 default_server;     server_name _;     charset utf-8;      access_log /var/log/nginx/maintenance.access.log;     error_log /var/log/nginx/maintenance.error.log error;      root /home/path/to/templates;      location / {         return 503;     }      error_page 503 @maintenance;      location @maintenance {         rewrite ^(.*)$ /maintenance.html break;     } }   Any of you see what might be wrong here?
111640
I have set $conf['reverse_proxy'] = TRUE; in settings.php, but the IP address logged in the flood table is 127.0.0.1, not the one passed through the X-Forwarded-For header. Nginx is configured to send the X-Forwarded-For header to Apache, but it seems Drupal isn't recognizing it.  This is pretty bad because a few failed logins can lockout for everyone.  How can I make Drupal use the IP passed within the X-Forwarded-For header?
20359
Trying to open a http website on any web browser (event telnet) gives a ‘ERR_CONNECTION_REFUSED’ or ‘connection timed out’.  However, the same sites can be opened using https. I tried doing a traceroute and it works fine.  I am new to OS X but have experience with Linux. How do I go about troubleshooting this issue?  Update  I think I've tracked down the culprit to a rule in pf (firewall).  The result of sudo pfctl -s nat is:  No ALTQ support in kernel ALTQ related functions disabled rdr pass inet proto tcp from 192.168.0.101 to any port = 80 -&gt; 127.0.0.1 port 9882   192.168.0.101 is the current ip address of the computer.  I tried to remove the rule with sudo pfctl -F all, but it is back after a few seconds. I didn't find the rule in the default configurations (/etc/pf.conf). And disabling pf with sudo pfctl -d has no effect on it.  Is this a malware issue?
122218
Clicking on  doesn't connect me with the meta S.Ex.SE site.  EDIT: For some entry points, . Observation courtesy Gilles.  I consider it a pity that the devs have not paid attention to this issue nor have indicated that they noted the problem. While HTTPS is not yet official on this network, I refrain from using unencrypted connections. I can't participate in metas, oh well.  EDIT #2 (2015-11-07) - with the switch to CloudFlare SSL the problem looks finally resolved.  EDIT #3 (2015-11-17) - still getting 403 Forbidden from CloudFlare. D'rats!..  EDIT #4 (2016-01-11) - We're still there. It's 2016 already... Starting a bounty.
59766
I'm trying to verify that a couple of our servers can communicate via certain ports before migrating some of our services to them, and that they're not blocked by our organizations firewall ACLs.  Makes Sense  [mrduki@mybox1~]$ nc -ul 40000 --- [mrduki@mybox2~]$ nc -zvuw2 mybox1.com 40000 Connection to mybox1.com 40000 port [udp/*] succeeded!   Doesn't Make Sense  [mrduki@mybox1~]$ nc -ul 40000 [mrduki@mybox1~]$ ^C --- [mrduki@mybox2~]$ nc -zvuw2 mybox1.com 40000 Connection to mybox1.com 40000 port [udp/*] succeeded!   In fact, if I do a port scan from 40000-40100, every single port succeeds.   If I do the same tests without -u (so that it tests TCP instead of UDP), I get 40000 (tcp) timed out: Operation now in progress errors, as I would expect (since I have no such TCP service listening on 40000).  Doing a sudo netstat -alnp | grep LISTEN on mybox1 though shows no such services listening on these ports. So what am I missing?
69843
I have two domains: staging.abc.com and www.example.com pointing to the same server IP in my DNS. I don't have a site enabled/available for staging.abc.com, but I have one for www.example.com. However, whenever I access staging.abc.com, it points to www.example.com.  Here are my confs. My /etc/nginx/nginx.conf is default. I didn't change anything.  I don't have a sites-available/default. It's been removed.  # sites-available/example server {   listen 80;   server_name example.com;   return 301 http://www.example.com$request_uri; }  server {   listen 80;   listen [::]:80;    root /home/deployer/example;   index index.php index.html index.htm;    server_name www.example.com;    location ~* .(jpg|jpeg|png|gif|ico|css|js|woff)$ {   expires 30d;   }    location / {     try_files $uri $uri/ /index.php?q=$uri&amp;$args;   }    error_page 404 /404.html;    error_page 500 502 503 504 /50x.html;   location = /50x.html {     root /usr/share/nginx/html;   }    location ~ \.php$ {     try_files $uri =404;     fastcgi_split_path_info ^(.+\.php)(/.+)$;     fastcgi_pass unix:/var/run/php5-fpm.sock;     fastcgi_index index.php;     include fastcgi_params;     fastcgi_read_timeout 300;   }    include /home/deployer/example/nginx.conf; }   # nginx.conf user www-data; worker_processes 4; pid /run/nginx.pid;  events {         worker_connections 768;         # multi_accept on; }  http {          ##         # Basic Settings         ##         charset utf-8;         sendfile on;         tcp_nopush on;         tcp_nodelay on;         keepalive_timeout 65;         types_hash_max_size 2048;         # server_tokens off;         proxy_read_timeout 300;          # server_names_hash_bucket_size 64;         # server_name_in_redirect off;          include /etc/nginx/mime.types;         default_type application/octet-stream; ...   I tried inserting this to the http block but to no avail:  server {     listen      80;     server_name "";     return      444; }   Here's what I want to achieve:   Changes are preferably done on sites-available. The server should not resolve any connection (returns 444) for all domain names that have not been assigned to any app.
49459
All of the examples I've seen of using upstream (for load balancing) in nginx look like this:  upstream  backend  {   server   backend1.example.com:8080          max_fails=3  fail_timeout=30s;   server   backend2.example.com:8080          max_fails=3  fail_timeout=30s;   server   backend3.example.com:8080          max_fails=3  fail_timeout=30s; }   It seems repetitive to re-set max_fails and fail_timeout for each backend, when typically they are always the same. Is it possible to set max_fails and fail_timeout for all of the backend servers at once?
24719
I'm trying to follow the  (on my Ubuntu 10.04 VM).  The first step is:  sudo add-apt-repository ppa:linaro-maintainers/toolchain   But when I run that I get:  Error reading https://launchpad.net/api/1.0/~linaro-maintainers/+archive/toolchain: &lt;urlopen error [Errno 110] Connection timed out&gt;   I'm guessing the problem is with my configuration for my employer's proxy server, particularly for HTTPS.  When I opened  in Firefox, I got "The connection has timed out".  I then went into Firefox Preferences -> Advanced -> Network -> Settings... and set HTTP Proxy to "gateway" and Port to 8080, and checked "Use this proxy server for all protocols".  Then the page loaded.  This supports my theory.  I've tried setting the http_proxy and https_proxy environment variables (both lower and upper case):  $ set | grep -i proxy HTTPS_PROXY=https://gateway:8080 HTTP_PROXY=http://gateway:8080 http_proxy=http://gateway:8080 https_proxy=https://gateway:8080   I also tried changing them to:  $ set | grep -i proxy HTTPS_PROXY=gateway:8080 HTTP_PROXY=gateway:8080 http_proxy=gateway:8080 https_proxy=gateway:8080   And I tried adding this second line to /etc/apt/apt.conf:  Acquire::http::proxy "http://gateway:8080/"; Acquire::https::proxy "https://gateway:8080/";   But I continue to get the same error.  How do I troubleshoot this?  Update: I followed the instructions in the  to  and got further:  $ sudo add-apt-repository ppa:linaro-maintainers/toolchain Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 1DD749B890A6F66D050D985CF1FCBACA7BE1F97B gpg: requesting key 7BE1F97B from hkp server keyserver.ubuntu.com gpgkeys: HTTP fetch error 7: couldn't connect to host gpg: no valid OpenPGP data found. gpg: Total number processed: 0   I wonder if the "HTTP fetch error" means I also need to add "Defaults env_keep = http_proxy" to /etc/sudoers...  Update #2: I added:  Defaults env_keep="http_proxy" Defaults env_keep="https_proxy"   ...as in , but I still get the same "gpgkeys: HTTP fetch error 7: couldn't connect to host" error.  And this is curious:  $ sudo env | grep proxy https_proxy=https://gateway:8080   ...because http_proxy isn't there.  Any advice is appreciated.  Update #3: Since the host of my VM is a laptop, I took it home and tried there (with no proxies):  $ sudo add-apt-repository ppa:linaro-maintainers/toolchain Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 1DD749B890A6F66D050D985CF1FCBACA7BE1F97B gpg: requesting key 7BE1F97B from hkp server keyserver.ubuntu.com gpg: key 7BE1F97B: public key "Launchpad Linaro Overlay PPA" imported gpg: Total number processed: 1 gpg:               imported: 1  (RSA: 1)   It worked.  So problem is related to proxy configuration.  But I suppose I have a workaround.
39135
I have a site at hostgator, using their "Business account". It's cheap, and comes with a private SSL cert. HOWEVER, their MySQL settings are such that any db connection goes stale fairly quickly, and then the hostgator staff try to convince you to use a VPS or dedicated server at multiple times the expense.  I'm creating and deploying WebAPIs, which can have a 'conversation' which exceeds 60 seconds. When this occurs, the db connection handle is stale, causing any db operations after my timeout to fail.  I'm in the process of implementing the following solution, but am curious if anyone else has solved this issue (where they can not modify their my.ini or my.cnf to give MySQL more resources) in a similar or completely different manner.  last part of a hook_update:  $ret = db_query( "UPDATE {my_table} set field1 = '%s', field2 = %d ... WHERE vid - %d", $node-&gt;field1, $node-&gt;field2, ... $node-&gt;vid ); if (!$ret) {        // get private storage directory for this node:        $cexStorage    = _cex_front_getCexStore();        $nodeFilesPath = DRUPALROOT.'/'.$cexStorage.'/'.$node-&gt;storeDir;        $fname         = $nodeFilesPath.'/recover.node';         $readyToWrite  = serialize( $node );        file_put_contents( $fname, $readyToWrite );        if (file_exists( $fname )) {          _dbgReport( 'seems to have worked!' );        }     }   Then this is called in my hook_form, right after I determine that node->nid is valid:  function _cex_front_recover_node( &amp;$node ) {   if (!isset($node-&gt;storeDir)) {      _dbgReport( '**************************** _cex_front_recover_node: no storeDir!!!' );      return;   }    // get private storage directory for this node:   $cexStorage    = _cex_front_getCexStore();   $nodeFilesPath = DRUPALROOT.'/'.$cexStorage.'/'.$node-&gt;storeDir;   $fname         = $nodeFilesPath.'/recover.node';   if (file_exists( $fname )) {     $recovered = file_get_contents( $fname );     if ($recovered) {       // no longer needed:       unlink( $fname );       $recoveredNode = unserialize( $recovered );       // restore the key values I need to proceed with this node:       $node-&gt;stage = $recoveredNode-&gt;stage;       $node-&gt;rnid  = $recoveredNode-&gt;rnid;       $node-&gt;iris  = $recoveredNode-&gt;iris;       cex_front_update( $node );     }     else {       _dbgReport( '********* failed to read "'.$fname.'"' );     }   } }   I'll be pairing the logic down to only store the key fields I need, but this works! Sure beats upgrading my server at 3x the expense. Anyone else doing something like this?
78999
I have a brand new VM with CenotOS 7 Minimal Installation.  What I want to happen is to configure Nginx to serve static files from a directory on localhost:80.  My directory is /home/kenny/projects/kcrypt/dist/.  Here are the contents of my /etc/nginx/nginx.conf:  # this is set to root in order to rule out # any permission related issues. user root;      worker_processes auto; error_log /var/log/nginx/error.log; pid /run/nginx.pid;  include /usr/share/nginx/modules/*.conf;  events {     worker_connections 1024; }  http {     log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '                       '$status $body_bytes_sent "$http_referer" '                       '"$http_user_agent" "$http_x_forwarded_for"';      access_log  /var/log/nginx/access.log  main;      sendfile            on;     tcp_nopush          on;     tcp_nodelay         on;     keepalive_timeout   65;     types_hash_max_size 2048;      include             /etc/nginx/mime.types;     default_type        application/octet-stream;      server {         listen       80 default_server;         listen       [::]:80 default_server;         root         /home/kenny/projects/kcrypt/dist/;         index index.html;          location / {         }     } }   when I run curl http://localhost I get this response:  &lt;html&gt; &lt;head&gt;&lt;title&gt;403 Forbidden&lt;/title&gt;&lt;/head&gt; &lt;body bgcolor="white"&gt; &lt;center&gt;&lt;h1&gt;403 Forbidden&lt;/h1&gt;&lt;/center&gt; &lt;hr&gt;&lt;center&gt;nginx/1.12.2&lt;/center&gt; &lt;/body&gt; &lt;/html&gt;   I have tried giving all kinds of permissions to any directories that I can think of.   In the end I configured Nginx to run as root.   I have reinstalled the OS multiple times already and can't get it to work.   P.S.   This is what I found in /var/log/nginx/error.log  2018/02/27 21:33:19 [error] 15689#0: *1 open() "/home/kenny/projects/kcrypt/dist/index.html" failed (13: Permission denied), client: ::1, server: , request: "GET / HTTP/1.1", host: "localhost" 2018/02/27 21:33:35 [error] 15690#0: *2 open() "/home/kenny/projects/kcrypt/dist/index.html" failed (13: Permission denied), client: 127.0.0.1, server: , request: "GET / HTTP/1.1", host: "127.0.0.1" 2018/02/27 21:33:38 [error] 15690#0: *3 open() "/home/kenny/projects/kcrypt/dist/index.html" failed (13: Permission denied), client: ::1, server: , request: "GET / HTTP/1.1", host: "localhost"   I don't get what it wants... I have given it all the permissions that I can.   This is what I have in the root directory:  [root@vm3 dist]# ll total 368K drwxrwxrwx. 2 root root   98 Feb 26 23:16 . drwxrwxrwx. 6 root root  234 Feb 27 21:26 .. -rwxrwxrwx. 1 root root 1.2K Feb 26 23:16 favicon.ico -rwxrwxrwx. 1 root root 1.7K Feb 26 23:16 index.html -rwxrwxrwx. 1 root root 175K Feb 26 22:53 index.js -rwxrwxrwx. 1 root root  297 Feb 26 23:16 manifest.json -rwxrwxrwx. 1 root root 179K Feb 26 22:53 styles.css   P.S. 2  I have tried putting my static files in /var/www/kcrypt/dist/, but with no result.  I still get the same error messages:   2018/02/27 23:18:11 [error] 16157#0: *1 open() "/var/www/kcrypt/dist/index.html" failed (13: Permission denied), client: ::1, server: , request: "GET / HTTP/1.1", host: "localhost" 2018/02/27 23:20:58 [error] 16535#0: *1 open() "/var/www/kcrypt/dist/index.html" failed (13: Permission denied), client: ::1, server: , request: "GET / HTTP/1.1", host: "localhost" 2018/02/27 23:21:30 [error] 16564#0: *1 open() "/var/www/kcrypt/dist/index.html" failed (13: Permission denied), client: ::1, server: , request: "GET / HTTP/1.1", host: "localhost"
86185
I'm scanning a server which should have a pretty simple firewall using iptables: by default everything is DROPped besides RELATED and ESTABLISHED packets. The only type of NEW packets allowed are TCP packets on port 22 and 80 and that's it (no HTTPS on that server).  The result of nmap on the first 2048 ports gives 22 and 80 as open, as I expect.  However a few ports appear as "filtered".  My question is: why do port 21, 25 and 1863 appear as "filtered" and the 2043 other ports do not appear as filtered?  I expected to see only 22 and 80 as "open".  If it's normal to see 21,25 and 1863 as "filtered", then why aren't all the other ports appearing as "filtered" too!?  Here's the nmap output:  # nmap -PN 94.xx.yy.zz -p1-2048  Starting Nmap 6.00 ( http://nmap.org ) at 2014-06-12 ... Nmap scan report for ksXXXXXX.kimsufi.com (94.xx.yy.zz) Host is up (0.0023s latency). Not shown: 2043 closed ports PORT     STATE    SERVICE 21/tcp   filtered ftp 22/tcp   open     ssh 25/tcp   filtered smtp 80/tcp   open     http 1863/tcp filtered msnp   I really don't get why I have 2043 closed ports:  Not shown: 2043 closed ports   and not 2046 closed ports.  Here's an lsof launched on the server:  # lsof -i -n COMMAND   PID USER   FD   TYPE   DEVICE SIZE NODE NAME named    3789 bind   20u  IPv4     7802       TCP 127.0.0.1:domain (LISTEN) named    3789 bind   21u  IPv4     7803       TCP 127.0.0.1:953 (LISTEN) named    3789 bind  512u  IPv4     7801       UDP 127.0.0.1:domain  sshd     3804 root    3u  IPv4     7830       TCP *:ssh (LISTEN) sshd     5408 root    3r  IPv4 96926113       TCP 94.xx.yy.zz:ssh-&gt;aa.bb.cc.dd:37516 (ESTABLISHED) sshd     5411    b    3u  IPv4 96926113       TCP 94.xx.yy.zz:ssh-&gt;aa.bb.cc.dd:37516 (ESTABLISHED) java    16589    t   42u  IPv4 88842753       TCP *:http-alt (LISTEN) java    16589    t   50u  IPv4 88842759       TCP *:8009 (LISTEN) java    16589    t   51u  IPv4 88842762       TCP 127.0.0.1:8005 (LISTEN)   (note that Java / Tomcat is listening on port 8009 but that port is DROPped by the firewall)
106734
I've set up a simple GeoServer on a Ubuntu server, behind an NGINX reverse proxy. The proxy is at map.mydomain.com and passes incoming port 80 requests on a subdomain to another internal port. I can access the web interface all no problems, log in etc. But whenever I try to use most buttons (save/apply/etc) I get a CORS error: &quot;Origin does not correspond to request&quot;. This is a snapshot of the request on clicking one of these buttons:  I have followed the below to enable CORS, but no luck. This is the default GeoServer 2.18.0 install, so it is using Jetty.  All I can figure is somewhere, some bits of Jetty may be expecting 127.0.0.1 rather than maps.ourdomain.com but for the life of me I can't figure out how or why it's only on button clicks! proxy config:     proxy_pass http://127.0.0.1:3201/$1$is_args$args;     proxy_http_version 1.1;     proxy_set_header Host $host;     proxy_set_header X-Real-IP $remote_addr;     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
31509
I have a rather large and slow (complex data, complex frontend) web application build in RoR and served by Puma with nginx as reverse proxy. Looking at the nginx error log, I see quite a few entries like:  2014/04/08 09:46:08 [warn] 20058#0: *819237 an upstream response is buffered to a temporary file      /var/lib/nginx/proxy/8/47/0000038478 while reading upstream,      client: 5.144.169.242, server: engagement-console.foo.it,      request: "GET /elements/pending?customer_id=2&amp;page=2 HTTP/1.0",      upstream: "http://unix:///home/deployer/apps/conversationflow/shared/sockets/puma.sock:/elements/pending?customer_id=2&amp;page=2",      host: "ec.reputationmonitor.it",      referrer: "http://ec.foo.it/elements/pending?customer_id=2&amp;page=3"   I am rather curious as it's very unlikely that the page remains the same for different users and different user interactions, and I would not think that buffering the response on disk is necessary/useful.  I know about proxy_max_temp_file_size and setting it to 0, but it seems to me a little bit awkward (my proxy tries to buffer but has no file where to buffer to... how can that be faster?).  My questions are:   How can I remove the [warn] and avoid buffering responses? Is it better to turn off proxy_buffering or to set proxy_max_temp_file_size to 0? Why? If nginx buffers a response: When does it serve the buffered response, to whom, and why? Why nginx turns proxy_buffering on by default and then [warn]s you if it actually buffers a response? When does a response trigger that option? When it takes > some seconds (how many?) to serve the response? Is this configurable?   TIA, ngw.
93373
I had problem doing sudo apt update for manually added repositories (I had problem with nodejs and docker) with my Ubuntu 17.10 VM running in VirtualBox. The error I get is Could not handshake: An unexpected TLS packet was received.  The following are steps that I took when trying to add docker repository and the output. The same thing happened when I tried to add nodejs as well.  sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - OK sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt-key fingerprint 0EBFCD88 pub   rsa4096 2017-02-22 [SCEA]       9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88 uid           [ unknown] Docker Release (CE deb) &lt;docker@docker.com&gt; sub   rsa4096 2017-02-22 [S]  sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" [sudo] password for sdnc-dev:  sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt update  Ign:1 https://download.docker.com/linux/ubuntu artful InRelease Err:2 https://download.docker.com/linux/ubuntu artful Release   Could not handshake: An unexpected TLS packet was received. Hit:3 http://us.archive.ubuntu.com/ubuntu artful InRelease Get:4 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB] Get:5 http://us.archive.ubuntu.com/ubuntu artful-updates InRelease [78.6 kB]        Get:6 http://us.archive.ubuntu.com/ubuntu artful-backports InRelease [72.2 kB] Get:7 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages [226 kB] Get:8 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 Packages [222 kB] Get:9 http://us.archive.ubuntu.com/ubuntu artful-updates/main Translation-en [101 kB] Get:10 http://us.archive.ubuntu.com/ubuntu artful-updates/universe i386 Packages [91.9 kB] Get:11 http://us.archive.ubuntu.com/ubuntu artful-updates/universe amd64 Packages [92.8 kB] Get:12 http://us.archive.ubuntu.com/ubuntu artful-updates/universe Translation-en [52.9 kB] Reading package lists... Done               E: The repository 'https://download.docker.com/linux/ubuntu artful Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.   Here is the details of my setup:     VM: Ubuntu 17.10    VirtualBox 5.2.8 r121009 (Qt5.6.2)    I am behind corporate proxy.   Does anyone know how to fix this?
103160
The problem is that the main site uses the HTTPS protocol, and the GeoServer does not accept requests over the protocol , gives an error message &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;ows:ExceptionReport xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:ows=&quot;http://www.opengis.net/ows&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; version=&quot;1.0.0&quot; xsi:schemaLocation=&quot;http://www.opengis.net/ows http://test.geoportal.samgau.com/geoserver/schemas/ows/1.0.0/owsExceptionReport.xsd&quot;&gt; &lt;ows:Exception exceptionCode=&quot;InvalidParameterValue&quot; locator=&quot;typeName&quot;&gt;     &lt;ows:ExceptionText&gt;Could not locate {https://test.geoportal.samgau.com}001_1132201_ads_lin in catalog.&lt;/ows:ExceptionText&gt; &lt;/ows:Exception&gt;&lt;/ows:ExceptionReport&gt;....  If I change the protocol to HTTP, then everything is ok GeoServer message: 2020-09-22 18:24:06,311 ERROR [geoserver.ows] - org.geoserver.wfs.WFSException: Could not locate {https://test.geoportal.samgau.com}001_1132201_ads_lin in catalog. I can't figure out which direction to look in. There is very little information on the Internet about this. What should I do and how should I organize the work?
99154
I'm trying to figure out how to set a default host for my nginx installation. I found this article in the nginx Wiki:    Unfortunately, this doesn’t work. After restarting I get this:  Restarting nginx: nginx: [emerg] unknown directive "http" in /etc/nginx/sites-enabled/catchall:1 nginx: configuration file /etc/nginx/nginx.conf test failed   After removing the http directive I get this:  Restarting nginx: nginx: [emerg] unknown log format "main" in /etc/nginx/sites-enabled/catchall:7 nginx: configuration file /etc/nginx/nginx.conf test failed   I’m on Ubuntu 10.04.3 where I’m using the official nginx PPA. Version 1.0.9 of nginx is running.