Nginx not re-directing to host
-
@wirestyle22 So how did you configure Fedora?
Take it back to the stupid level to find what you are doing different.
Here are the screens for Fedora 25.
https://mangolassi.it/topic/13498/how-to-install-fedora-25-minimal -
@jaredbusch My installation is identical with the exception of guest agents. I can't imagine that would affect whether or not a
.conf
file was read though. This would all be self-contained, no? -
@wirestyle22 said in Nginx not re-directing to host:
@jaredbusch My installation is identical with the exception of guest agents. I can't imagine that would affect whether or not a
.conf
file was read though. This would all be self-contained, no?Should be of course. Your experience is abnormal. I set this up 3 times last night wile making these instructions.
-
Either your config messed up somewhere or SELinux is interfering.
-
@black3dynamite said in Nginx not re-directing to host:
Either your config messed up somewhere or SELinux is interfering.
It should error if there a syntax problem though right? It should be reading any .conf in conf.d.
-
sudo tail -5 /var/log/nginx/error.log
2018/03/11 23:42:31 [error] 681#0: *14 connect() failed (113: No route to host) while connecting to upstream, client: 192.168.1.1, server: nc.skynetli.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://192.168.1.202:80/favicon.ico", host: "nc.skynetli.com", referrer: "http://nc.skynetli.com/"
-
@wirestyle22 ok, so your proxy cannot talk to your backend server is seems.
So a networking issue.
Can you ping 192.168.1.202 from your proxy?
Can you SSH into it from your proxy? -
@jaredbusch I can do both
-
@wirestyle22 said in Nginx not re-directing to host:
failed (113: No route to host) while connecting to upstream
I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.
-
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
failed (113: No route to host) while connecting to upstream
I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.
Unsure where to really look config-wise to resolve it. From what I see, everything is correct
-
What ports see you using to communicate with the upstream server?
-
@wirestyle22 said in Nginx not re-directing to host:
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
failed (113: No route to host) while connecting to upstream
I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.
Unsure where to really look config-wise to resolve it. From what I see, everything is correct
I usually try to setup the port on the configuration:
proxy_Pass http://192.168.1.202:80;
-
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
failed (113: No route to host) while connecting to upstream
I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.
Unsure where to really look config-wise to resolve it. From what I see, everything is correct
I usually try to setup the port on the configuration:
proxy_Pass http://192.168.1.202:80;
I noticed that JB didn't specify the port in his most recent guide but did in his original guide (was port 80). I tried both ways with the same result.
-
@coliver said in Nginx not re-directing to host:
What ports see you using to communicate with the upstream server?
That's specified in
proxy_Pass
correct? Port 80 if I am correct. I'm reaching the end of my knowledge with nginx. I was trying to test this to manage my SSL certs with a reverse proxy for learning purposes.Syntax: proxy_pass URL; Default: — Context: location, if in location, limit_except Sets the protocol and address of a proxied server and an optional URI to which a location should be mapped. As a protocol, “http” or “https” can be specified. The address can be specified as a domain name or IP address, and an optional port: proxy_pass http://localhost:8000/uri/;
-
@wirestyle22 said in Nginx not re-directing to host:
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
failed (113: No route to host) while connecting to upstream
I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.
Unsure where to really look config-wise to resolve it. From what I see, everything is correct
I usually try to setup the port on the configuration:
proxy_Pass http://192.168.1.202:80;
I noticed that JB didn't specify the port in his most recent guide but did in his original guide (was port 80). I tried both ways with the same result.
Port is not required for 80 or 443 because those are default.
I can post another example I guess.
-
@jaredbusch said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
@dbeato said in Nginx not re-directing to host:
@wirestyle22 said in Nginx not re-directing to host:
failed (113: No route to host) while connecting to upstream
I am seeing a 502 bad gateway on your link. Which obviously point to that upstream issue.
Unsure where to really look config-wise to resolve it. From what I see, everything is correct
I usually try to setup the port on the configuration:
proxy_Pass http://192.168.1.202:80;
I noticed that JB didn't specify the port in his most recent guide but did in his original guide (was port 80). I tried both ways with the same result.
Port is not required for 80 or 443 because those are default.
I can post another example I guess.
For sure. I just noticed a difference, not assuming it's wrong. Thanks
-
So two things:
-
I must have typo'd when opening ports on the Nextcloud server as the proper ports were not actually open as @coliver mentioned.
-
I also found a typo in my config.php
Working. I knew I did something wrong.
Thank you for all of the help @scottalanmiller and @dbeato
-
-
I see I get no credit for figuring it out
-
@scottalanmiller Sorry! I was tallking to dbeato and got distracted