[Solved] Can't access web UI on LAN.

Get help, report and discuss bugs.
Post Reply
Mssol94
Posts: 3
Joined: 30 Aug 2017, 09:40

[Solved] Can't access web UI on LAN.

Post by Mssol94 » 30 Aug 2017, 09:49

I'm having problems with accessing the web UI on LAN. I have set the ControlIP as 0.0.0.0. I've also tried to ping the IP-address with the port number without a response. I can access Sonarr and Radarr on the same computer.
Last edited by Mssol94 on 30 Aug 2017, 14:42, edited 1 time in total.

hugbug
Developer & Admin
Posts: 6585
Joined: 09 Sep 2008, 11:58
Location: Germany (NRW)

Re: Can't access web UI on LAN.

Post by hugbug » 30 Aug 2017, 10:06

Check Firewall on PC where NZBGet runs.

Mssol94
Posts: 3
Joined: 30 Aug 2017, 09:40

Re: Can't access web UI on LAN.

Post by Mssol94 » 30 Aug 2017, 10:42

I can't see that theres anything wrong with the firewall settings.

Image

hugbug
Developer & Admin
Posts: 6585
Joined: 09 Sep 2008, 11:58
Location: Germany (NRW)

Re: Can't access web UI on LAN.

Post by hugbug » 30 Aug 2017, 10:55

Mssol94 wrote:
30 Aug 2017, 09:49
I've also tried to ping the IP-address with the port number
What do you mean? You can't ping a port.

ControlIP and ControlPort are the only options to set in NZBGet.
If NZBGet is accessible from local computer then it has to be a network issue:
  • check if using correct IP and port in browser;
  • check Firewall settings on both computers;
  • maybe your router blocks the port.

Mssol94
Posts: 3
Joined: 30 Aug 2017, 09:40

Re: Can't access web UI on LAN.

Post by Mssol94 » 30 Aug 2017, 11:15

Ok, I thought i could ping a port. But i have located the problem. I can access it when i turn off the firewall, so there must be something wrong with the rules. I tried adding a rule that allows inbound connections to NZBGet and i also tried to add a rule that allows inbound connections to the specific port, but it still doesn't work.

Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests