> (I guess you either removed the INPUT DROP rule; or added an explicit
> "allow 443" beside the "allow 80" rule that was already there.
> Whichever
> it was, it was "make the local firewall allow the traffic get to
> nginx".)
Right, the allow 443 actually existed but there was a rule above it tha
On Tue, Aug 25, 2020 at 07:49:07AM -0400, nathanpgibson wrote:
Hi there,
> Turned out there was an INPUT DROP rule in iptables (but not in ip6tables),
> although I am using ufw as a firewall. Now https works and my nginx
> redirects are functioning as expected!
Great that you found and fixed the
Turned out there was an INPUT DROP rule in iptables (but not in ip6tables),
although I am using ufw as a firewall. Now https works and my nginx
redirects are functioning as expected!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,289099,289186#msg-289186
__
Thanks so much, Francis Daly! This is a huge help in isolating the problem.
Based on the nginx access log, IPv6 requests to port 443 are getting to
nginx but IPv4 requests to port 443 are not. But they are getting to
tcpdump. All I see there is a bunch of packets with the tcpflag [S]. I take
it t
bably work better.
You also indicate that most visitors get a connection timeout message,
while some get through.
Do your nginx logs indicate that all of the ones that get through are
using IPv6, not IPv4? That might also point at IPv4 being blocked.
(Or: do your nginx logs indicate that all o
Just wondering if anyone has further thoughts on what to try here?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,289099,289172#msg-289172
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Thanks for the reply, Thomas.
> You said this is "shared hosting" - when you say "shared hosting" do you
> mean this is *not* a dedicated machine but one machine out of many in a
> shared environment?
Sorry, I meant virtual hosting.
> Have you tested briefly by disabling your firewall just to s
end? You're passing everything to 8080 which suggests
the backend might be having issues too.
Thomas
On 8/13/20 3:04 PM, nathanpgibson wrote:
> Hi All,
> Newbie question. I posted this on Stack Overflow but haven't gotten any
> replies yet.
> https://stackoverflow.com/question
Hi All,
Newbie question. I posted this on Stack Overflow but haven't gotten any
replies yet.
https://stackoverflow.com/questions/63391424/why-do-i-get-connection-timeout-on-ssl-even-though-nginx-is-listening-and-firewa
Most/many visitors to my site https://example.org get a connection ti
Hi,
I am using nginx/1.12.0 as reverse proxy with Apache/2.2.15
Relevant configuration is:
upstream backend {
ip_hash;
server 127.0.0.1:8080; # IP goes here.
}
server {
listen 2x; # IP goes here.
server_name www.somesite;
# Set proxy headers for the passthrough
proxy_set_header Host $ho
Hi
I have an nginx setup on multiple download servers. I've setup a monitor
server to check my servers at interval and when the servers seem to be at
their peak I get connection timeout from my servers. I've set limit_conn 64
for each remote_ip
to make sure one user can't hog th
On Tue, May 05, 2015 at 04:00:11PM -0400, GuiPoM wrote:
Hi there,
> I just tried to put debug as for example : "access_log
> /var/log/nginx/access.log debug;"
>
> But:
> Restarting nginx: nginx: [emerg] unknown log format "debug" in
> /etc/nginx/nginx.conf:36
> nginx: configuration file /etc/ng
I will do so.
Two questions:
1/ In my config file /etc/nginx/nginx.conf, in section http, I already have
the logging entries defined :
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
I just tried to put debug as for example : "access_log
/var/log/nginx/access.log debug;"
On Mon, May 04, 2015 at 02:19:45PM -0400, GuiPoM wrote:
Hi there,
> Thank you for your answer. I can reproduce on demand ! BUTI am not familiar
> with nginx.
> Could you give me some hints what to activate in order to provide useful
> information for debugging ?
You could follow http://nginx.or
Thank you for your answer. I can reproduce on demand ! BUTI am not familiar
with nginx.
Could you give me some hints what to activate in order to provide useful
information for debugging ?
I must connect through a proxy server but I will never be able to get the
logs from there. I can get some lo
On Sat, May 02, 2015 at 10:52:31AM -0400, GuiPoM wrote:
Hi there,
> I have no clue why it is not working. So I took the computer from my office
> location and I did the test from another location, with a standard internet
> access: I have no issue at all.
>
> It means that only the network betwe
I have no clue why it is not working. So I took the computer from my office
location and I did the test from another location, with a standard internet
access: I have no issue at all.
It means that only the network between the computer and the nginx server
makes this error appears, it must have no
It must have a positive impact, I am now able to access the server using
HTTP, but not using HTTPS.
nginx is running on my raspberry, port 80 for http, for 443 for https.
External ports are routed to according internal ports.
So HTTP is fine, HTTPS still returns an ERR_TUNNEL_CONNECTION_FAILED fro
Try it with:
sendfileon;
tcp_nodelayon;
tcp_nopush off;
Best regards,
Mihai Vintila
On 4/22/2015 8:42 AM, GuiPoM wrote:
Short update, as I am still struggling with this problem: Same issue for
HTTP, if I route an external port to nginx on my raspberry. But if I route
to
Short update, as I am still struggling with this problem: Same issue for
HTTP, if I route an external port to nginx on my raspberry. But if I route
to another HTTP server, everything works fine from my work office. So this
must have something to do with nginx, but I have absolutely no idea where to
Hello,
nginx is the HTTP server that is provided with my home automation software,
jeedom. It is installed on my Raspberry Pi2.
Everyting is working fine, I can connect from my internal network and from
outside.
But, when connecting from work, I get an error (navigator displays and
certificate is
Thank you for your reply Maxim, that's exactly what's happening. It's
closing the socket for all the other requests I try, but not that one. I
guess the problem is farther down the line somewhere.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254687,254743#msg-254743
___
Hello!
On Fri, Nov 07, 2014 at 05:52:31PM -0500, jpherbst wrote:
> Hello,
>
> I have nginx 1.6.1 setup in front of uwsgi 2.0.7 using uwsgi_pass, which has
> been working very well for me except for one request. When I make the
> failing request uwsgi processes the request and returns the respon
Hello,
I have nginx 1.6.1 setup in front of uwsgi 2.0.7 using uwsgi_pass, which has
been working very well for me except for one request. When I make the
failing request uwsgi processes the request and returns the response in less
than a second, but nginx just sits there with an open connection t
We're having following issue with nginx and php-fpm, please have a look on
logs :
2013/12/26 16:43:24 [error] 9906#0: *37001 upstream timed out (110:
Connection timed out) while reading response header from upstream, client:
192.252.214.240, server: search.com, request: "GET
/search/es/index_video
25 matches
Mail list logo
