Moving SSL termination to the edge increased the instance of 502 errors

Hi All, We installed nginx as load balancer/failover in front of two upstream web servers. At first SSL terminated at the web servers and nginx was configured as TCP passthrough on 443. We rarely experiences 502s and when it did it was likely due to tuning/tweaking. About a week ago we moved

Re: domain only reachable with https:// in front

ahhh that's right, thanks for all your help guys ! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,277546,277561#msg-277561 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: domain only reachable with https:// in front

Your ISP is blocking port 80, so you cannot get redirected to HTTPS. http://www.dslreports.com/faq/11852 On Tue, Nov 28, 2017 at 6:17 PM, Jeff Dyke wrote: > I think it is unfortunate that certbot does it this way, with an if > statement, which i believe is evaluated in every request. I use some

Re: cts-submit

Am 27.11.2017 um 22:21 schrieb Ángel: > On 2017-11-26 at 14:17 +0100, A. Schulze wrote: >> Hello, >> >> experiments with nginx-ct ¹) show that I need a tool to submit a certificate >> to some public logs. >> cts-submit ²) seems useful. But it require me to install php on every host >> :-/ >> >>

Re: domain only reachable with https:// in front

I think it is unfortunate that certbot does it this way, with an if statement, which i believe is evaluated in every request. I use something like the following (with your names): server { listen 80 default_server; listen [::]:80 default_server; server_name pstn.host www.pstn.host; return

Re: domain only reachable with https:// in front

hi, thanks for answering, shouldn't that forward everything to https? so shouldn't it work with just pstn.host? instead of https://pstn.host Posted at Nginx Forum: https://forum.nginx.org/read.php?2,277546,277548#msg-277548 ___ nginx mailing list ngi

Re: domain only reachable with https:// in front

Hi, you have : if ($scheme != "https") { return 301 https://$host$request_uri; } # managed by Certbot in your config, that redirects everything to https. Mit freundlichen Grüßen / best regards Alexander Naumann artcom venture GmbH - Ursprüngliche Mail - Von: "pstnta"

domain only reachable with https:// in front

Hi, I'm using nginx as reverse proxy for guacamole, I can only reach my domain with https://pstn.host or https://www.pstn.host, it won't work without https or with even with https. here's my sites-enabled/pstn.host https://pastebin.com/raw/dKiEi72q any ideas what's wrong or missing? thanks! Po

Re: Nginx cache returns MISS after a few hours, can't be set up to cache "forever"

Can you count the number of files that are in your cache and whether or not it's changing with time? Then compare with the number of unique cache keys (from your web server log) When the server starts returning a MISS - does it only do this for newer objects that haven’t been requested before? D

Re: Nginx cache returns MISS after a few hours, can't be set up to cache "forever"

Hi, On Tue, Nov 28, 2017 at 12:32:32PM +0100, m...@1984.cz wrote: > Hi, > > I am trying to cache files "forever". Unfortunately in about 2-6 hours the > cache starts to return MISS again. This is the setting: > > --- > > proxy_cache_path /var/cache/nginx-cache levels=1:2 keys_zone=mycache:10m

Nginx cache returns MISS after a few hours, can't be set up to cache "forever"

Hi, I am trying to cache files "forever". Unfortunately in about 2-6 hours the cache starts to return MISS again. This is the setting: --- proxy_cache_path /var/cache/nginx-cache levels=1:2 keys_zone=mycache:10m max_size=20g inactive=10y; proxy_cache_valid 10y; "Expires" header returned by

upstream zone size

What is a reasonable value for upstream zone size? I'm just shooting in the dark with 64k right now. Running 64bit Linux. The official NGINX documentation does not elaborate on it, and I can't find anything useful on Google. upstream backends { zone example_zone 64k; keepalive 8l; ser