Yeah, it was a network issue. tcpdump helped.
Thanks
> On Dec 18, 2017, at 1:39 PM, Francis Daly wrote:
>
> On Mon, Dec 18, 2017 at 01:31:57PM -0600, Joel Parker wrote:
>
> Hi there,
>
>> network connectivity, firewall, etc. are all configured correctly but still
>> having issues when trying
On Mon, Dec 18, 2017 at 01:31:57PM -0600, Joel Parker wrote:
Hi there,
> network connectivity, firewall, etc. are all configured correctly but still
> having issues when trying to hit the proxy. It's is very strange, since the
> ports are listening. I even turned off the firewall and the same iss
Yeah,
network connectivity, firewall, etc. are all configured correctly but still
having issues when trying to hit the proxy. It's is very strange, since the
ports are listening. I even turned off the firewall and the same issues.
Joel
On Mon, Dec 18, 2017 at 1:26 PM, Francis Daly wrote:
> On
On Mon, Dec 18, 2017 at 01:21:41PM -0600, Joel Parker wrote:
Hi there,
> I have seen this a lot on google but have not been able to find a suitable
> solution. My firewall is setup correctly.
This looks like something that nginx can not do anything about.
> curl localhost - works
> curl 172.31.
I have seen this a lot on google but have not been able to find a suitable
solution. My firewall is setup correctly.
I am listening on port 80
netstat -anltp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program n
Thanks Maxim, that explains it
Would be nice if documentation mentioned this fact, or nginx would spit out
some errors about the conflicting config ;)
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257064,257107#msg-257107
___
nginx mailing l
Hello!
On Thu, Mar 05, 2015 at 09:58:37PM -0500, Fry-kun wrote:
> So it looks like the ssl config is valid per-port only. If I set up a server
> on a different port with different ssl config, it works.
> Is this a bug or is it by design?
This is by design. Before some protocol-specific handshak
"Connection refused", generally means that your server (sometimes this can
be a firewall too - although firewalls tend to more often just silently drop
packets) is sending a RST packet to an attempt to connect. Check with
netstat and see if Nginx is bound to your public IP on :443
As for your que
So it looks like the ssl config is valid per-port only. If I set up a server
on a different port with different ssl config, it works.
Is this a bug or is it by design?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257064,257086#msg-257086
__
Also noticed that http-level config causes www.foo.com to show errors on
https://www.200please.com/
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257064,257065#msg-257065
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailma
Hi all,
I have a strange problem with nginx:
I tried to harden the TLS stack by setting default to recommended values
from https://wiki.mozilla.org/Security/Server_Side_TLS but one server has to
keep backward compatibility -- so I set it up as
http {
ssl_protocols TLSv1.1 TLSv1.2;
ssl_ciphers
11 matches
Mail list logo
