Accessing GUI issue

I installed NZBDrone on another computer without the service. The problem is when I access the GUI, I can only access it via http://localhost:8989 and not through the other names like 127.0.0.1, hostname, FQDN, etc. It’s just going through with localhost and that’s very weird. I can confirm that this not a DNS problem as the hostname/IP address of the computer (192.168.x.x) can be resolved properly. I’m trying to access this GUI on the same computer, so no network involved here.

And then I tried reinstalling it but this time with the service and it worked. I manually deleted the service using sc delete and just run the nzbdron.exe /icon shortcut, and the problem is fixed.

Why does it behave that way when initially installed without the service?

I got no idea i have tested my with hostname and with the static IP and Localhost on the actual machine it is installed on and all work fine but then i am using the service by default

perhaps a firewall issue i find most issue with things over a network either boils down to permissions or firewall :smile:

is there a reason you are not wanting to use the service my guess is perhaps you just want to run NzbDrone on demand which i don’t think it will really perform at it’'s peak that way as it is not usually always running and watching for new episodes plus the fact everytime you reboot you gotta remember to start it up which in the past things i had set like this i always forgot and then realised like two days later then had to backtrack and grab stuff

Its how Windows handles webserver registration. Running it once as admin will fix it: https://github.com/NzbDrone/NzbDrone/wiki/Installation#windows

@protocol77

I don’t want it to run as a service because doing so will break access permissions to network shares unless you modify it to run as a user instead of the local system default. I’ll be running it as a startup program anyway so all is good.

@markus101

That makes sense, so when I reinstalled it as a service that made it run like as admin already which fixed the problem, right? Is this true for all web servers?

In the link you’ve posted, why is it saying that the nzbdrone package is a zip file? It’s an exe file now, right?

Correct, service runs as system by default, which is similar to admin. All web servers that use http.sys (a Windows component), this is currently the only way to do it for .net apps.

That makes sense. Thanks.