External Access on custom Domain doesn't work when running as service

[bulkcarrier]

Just like the title says .

I have a custom domain www customdomain com that points to my server running windows 10.

When running the app normally I am able to get to the SABNZBD interface from internally and from externally from my phone.

I then installed SABNZBD as a service using the same config file. It starts up and when I run the SABNZBD shortcut it opens the
web interface but with the local machine ip and I cannot access the web interface from my phone using my public ip or custom domain.
Even changed config value to 0.0.0.0 to allow everything and that also doesn't work. I just get a timeout when accessing from external.

I have confirmed that it's the same config file because my custom hostname www customdomain com is configured in both.

Is this a problem that my firewall is blocking the custom domain or is there a problem with custom domains when running as a service.

Is there log files I can look at ?

[sander]

First things first: can you access SABnzd, from your phone on 4G (not Wifi), on your public IP address?

[bulkcarrier]

Can access when running as exe on 4G and Wifi from my phone.

Cannot access when running as service on 4G and Wifi from my phone.

Even on the local machine I cannot used the FQDN when running as service whereas I can when running as EXE

Funny think for me is when I run it as EXE and I say to open browser it open to www customdomain com /sabnzbd/.

But when I run it as service and ask it to open the web interface it opens a browser to the local ip address /sabnzbd/.

[sander]

OK, then even further back-to-basics:

Check on which IP address SABnzbd as a service is listening:

As admin run CMD:

Code: Select all

C:\>netstat -aon | find /i "8080"
  TCP    127.0.0.1:8080         0.0.0.0:0              LISTENING       13868

So, yes on port 8080, but on IP address 127.0.0.1, which is local only.

So ... what does your Windows show when 1) running exe and 2) running as service ... ?