Remote Sonarr - Nginx
|
Posts: 6
Threads: 1
Joined: Oct 2015
Reputation:
0
[Not Solved]
Oct 16, 2015, 02:22 PM
Problem:
Bad Request - Invalid Hostname
HTTP Error 400. The request hostname is invalid.
The configuration of nginx and sonarr is below.
Portfoward on Router - Port 80 - TCP
*******************************************************************************************
Nginx Configuration
server {
listen 80;
server_name sjdaniel.chickenkiller.com, 192.168.1.83;
#charset koi8-r;
#access_log logs/host.access.log main;
location /sonarr {
proxy_pass http://127.0.0.1:8989;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
*******************************************************************************************
Sonarr
Bind Adress: 192.168.1.83
Port Number 8989
Url Base: /sonarr
Enable SSL: NO
Authentication: YES
********************************************************************************************
Posts: 38
Threads: 11
Joined: Jul 2015
Reputation:
3
[Not Solved]
Oct 16, 2015, 05:49 PM
Can you access it via ngix inside your own network. aka use the internal IP address of the box running nigx aka 192.168.#.#/sonarr
if you can do that then the issue is with your DYNDNS server not having the correct IP address. most of the time when the issue is with sonar you get an error message in the 500s
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
Oct 16, 2015, 05:54 PM
One more thing to check is going to your dynamic DNS address, you should see Welcome to nginx! if you don't it is because you need to port forward port 80 from your router to your box running nginx.
Posts: 38
Threads: 11
Joined: Jul 2015
Reputation:
3
[Not Solved]
Oct 16, 2015, 06:47 PM
(Oct 16, 2015, 05:54 PM)Mike Wrote: One more thing to check is going to your dynamic DNS address, you should see Welcome to nginx! if you don't it is because you need to port forward port 80 from your router to your box running nginx.
It could also be that the DynDns is not updated to the correct IP address
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
Oct 16, 2015, 07:27 PM
Definitely lorddark462, trying to access from the external IP instead of dynamic DNS would be a good idea too.
Is nginx running on the same box as sonarr? If it isn't you will have to change 127.0.0.1 to the local IP of the box running sonarr.
Posts: 6
Threads: 1
Joined: Oct 2015
Reputation:
0
[Not Solved]
Oct 17, 2015, 09:46 AM
(This post was last modified: Oct 17, 2015, 09:53 AM by dcnilas11.)
(Oct 16, 2015, 05:49 PM)lorddark462 Wrote: Can you access it via ngix inside your own network. aka use the internal IP address of the box running nigx aka 192.168.#.#/sonarr
if you can do that then the issue is with your DYNDNS server not having the correct IP address. most of the time when the issue is with sonar you get an error message in the 500s
I was trying this in 2 computers. One at home that is the goal, but because it gave me some problems i try in another one at work.
At work was better, and it was when this error appear. But at least when i use the inter nal ip adress, a message from nginx appear.
So today i tried to do everything again at home.
Sonarr is running ok - but now on 38082 like the tutorial
Deluge also good
The account in http://freedns.afraid.org is created and Afraid Updater running
Nginx i made also like the tutorial, then i started in Command Prompt, and it seems ok. But when in the browser i put 127.0.0.1, just appear a blank page. And also when i press Ctrl+Alt+Del to see the processes running i can't see nginx.
Quote:One more thing to check is going to your dynamic DNS address, you should see Welcome to nginx! if you don't it is because you need to port forward port 80 from your router to your box running nginx.
I don't see like i said above.
But i have already portforward in my router the port 80 (TCP), not UDP.
Quote:Definitely lorddark462, trying to access from the external IP instead of dynamic DNS would be a good idea too.
Is nginx running on the same box as sonarr? If it isn't you will have to change 127.0.0.1 to the local IP of the box running sonarr.
Yes, nginx is running on the same pc. PC with Windows 10 Home, i don't know if it makes any difference.
Thank you all.
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
Oct 17, 2015, 09:55 AM
Which tutorial uses port 38082?
nginx isn't running and may be blocked by your firewall if you are on Windows 10 in which case you'll need to make a firewall rule to allow nginx.
You may also need to run nginx as an Administrator.
What happens when you start nginx from the c:\nginx folder?
Posts: 6
Threads: 1
Joined: Oct 2015
Reputation:
0
[Not Solved]
Oct 17, 2015, 10:32 AM
(Oct 17, 2015, 09:55 AM)Mike Wrote: Which tutorial uses port 38082?
nginx isn't running and may be blocked by your firewall if you are on Windows 10 in which case you'll need to make a firewall rule to allow nginx.
You may also need to run nginx as an Administrator.
What happens when you start nginx from the c:\nginx folder?
Sorry, I thought it was from you, but it was form CuttingCords:
http://www.cuttingcords.com/home/ultimat...-up-sonarr
If i start from commandprompt with Administrator: just appear a fast black window and nothing more.
If i start from the folder with right click and Administrator, don't do nothing but no error also.
And nginx don't appear int process list.
Curious is: In command prompt if i write your line of code: c:\nginx-1.8.0>nginx -s reload
Message: nginx: [error] CreateFile<> "c:\nginx-12.8.0/logs/nginx.pid" failed <2: FormatMessage<> error:<15100>>
I have already open the nginx exe in windows firewall to all.
But with ports is working:
Sonarr: http://daso.crabdance.com:38082 and then it stays http://daso.crabdance.com:38082/sonarr/
Deluge: http://daso.crabdance.com:38081
But http://daso.crabdance.com/sonarr is not working.
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Not Solved]
Oct 17, 2015, 12:27 PM
There you go, that's the error, there is a typo somewhere in the nginx.conf file because it is trying to create a pid file in a folder that doesn't exist (nginx-12.8.0 should be nginx-1.8.0).
Find that line and change it then start nginx again, should work then.
Posts: 6
Threads: 1
Joined: Oct 2015
Reputation:
0
[Not Solved]
Oct 17, 2015, 12:52 PM
(Oct 17, 2015, 12:27 PM)Mike Wrote: There you go, that's the error, there is a typo somewhere in the nginx.conf file because it is trying to create a pid file in a folder that doesn't exist (nginx-12.8.0 should be nginx-1.8.0).
Find that line and change it then start nginx again, should work then.
But that was an error from me writing.
The error when I type nginx -s reload is this:
Message: nginx: [error] CreateFile<> "c:\nginx-1.8.0/logs/nginx.pid" failed <2: FormatMessage<> error:<15100>>
1.8 not 12.8
|
|
Recent Posts
|
About Swap
jonescelinaa Apr 10, 2024, 06:58 AM
|
Tracker Status: Error Connection Time Out
jonesPhedra Apr 04, 2024, 08:17 AM
|
Split Tunnel Docker Containers
jonesPhedra Mar 27, 2024, 03:10 AM
|
Plex server not powerful enough, but only with s...
jonesPhedra Mar 27, 2024, 03:02 AM
|
game Geometry Dash Scratch
jonescelinaa Jan 31, 2024, 04:21 AM
|
Latest unread posts | Unanswered posts |
|