Cannot connect to localhost suddenly

[AmyB0001 1]

Hi guys.

 

Been having a massive problem with emby since last night. I've suddenly not been able to open the the emby dashboard when starting the server. I've tried all sorts of things to get this working. I've resetting my browser, flushed my IP and renewed, reset my router. I've tried a different network connection even on a different web browser. Ended up uninstalling emby and installing the beta version to no avail. I've also used a system restore but still the same. 

 

I'm tearing my hair out trying to get this to work. Everything was fine yesterday until late last night.

 

I've attached the emby log.

 

Any help would be much appreciated!

embyserver.txt

[Abobader 3464]

Hello AmyB0001,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[rbjtech 5284]

Are you trying to load from the emby server itself - IP 192.168.0.21 ?

http://192.168.0.21:8096

if trying from another client but on the same network - then it may be your server firewall is blocking.    Also check it is set to 'private' network as opposed to 'Public'

From a command prompt as admin (on the emby server) - also worth checking Emby is listening -

netstat -i | find "8096"

 

Edited October 4, 2024 by rbjtech

[AmyB0001 1]

It's all on the same machine. Firewall is turned off. Its been on for 3 years with emby and worked fine, strange that it just stopped. The connection is private network not on public. 

I did the dirty and tried to see if jellyfin server would work but same problem. I've checked if 8096 is even listening on CMD, but that's all fine.

I'm stumped.

[rbjtech 5284]

so JF uses the same port (8096) so it's possible JF is blocking the use of that port - but the emby log shows it loading fine.

What does the browser show - can you do a screen grab of the error message ?

What about using Curl to see if you get any http response as it is listening ?

curl -Is http://192.168.0.21:8096

 

[AmyB0001 1]

Sorry I'm unfamiliar with Curl language. Do I need to download software?

I have uninstalled pretty much everything except emby now. Still the same.

Also this is the error message I'm getting:

[rbjtech 5284]

curl is just a command line executable - it's built into Windows 10 & 11.

It's a utility to send http requests - GET or POST for example - so you can send Emby API tasks etc.

In the above example - it's just sending Emby a 'hello' and Emby should reply with a HTTP/1.1 302 Found

[AmyB0001 1]

I've tried that command and it gives nothing back. No reply, no error or anything. Think I might do a fresh windows install when I get home later. I will let you know the outcome

[Carlo 4561]

Hi,

Are you able to ping 192.168.0.21 ?

from command line:

ping 192.168.0.21

[rbjtech 5284]

12 minutes ago, Carlo said:

Hi,

Are you able to ping 192.168.0.21 ?

from command line:

ping 192.168.0.21

he is on the localhost ..

If he can't ping himself, then we really are in trouble .. 

[Carlo 4561]

It happens! 

VPNs, tunnels and some other type of software can do this.
Typically, when there is multiple IPs from different subnets or VLANs and the routing table gets messed up.

Not common, but would still like to rule this out, since it's so easy to test.

Carlo

 

[AmyB0001 1]

Just a quick update. Reinstalled windows and voila, localhost now loads correctly!

 

Now I have a problem with the VPN. Emby won't connect remotely when it's on!

[GrimReaper 4740]

Just now, AmyB0001 said:

Now I have a problem with the VPN. Emby won't connect remotely when it's on!

Does your VPN provider support port forwarding? Have you configured it? Or set split-tunneling, if that method preferred? 

[AmyB0001 1]

I'm using surfshark with a dedicated IP address. Added Emby app to the bypass list. Funny enough been testing lots of different ports and they seem to be all closed even with port forwarding set up on the router.

[rbjtech 5284]

This is maybe a common misconception that by using a standard client VPN on your emby server means the remote connection will use the VPN end point - simply put IT DOES NOT.   By using a VPN on the emby server, all you are doing is using the VPN for any OUTBOUND connections - ie web traffic and emby metadata.      Any INCOMING connections (ie your remote users) will be using your normal public IP address.

Now as @GrimReapersays above SOME VPN providers allow you to actually port forward from the VPN Public address - using the VPN tunnel back via your public IP address.   However, this needs to be setup and of course the remote clients need to use the VPN address, not your public IP address.  This will also be dynamic - the VPN provider may provide a way to use this via DDNS.

[Carlo 4561]

Adding to what @GrimReaperand @rbjtechmentioned you want to make sure the VPN is started before Ember Server.  This allows Emby to detect the additional network and IP range.  You then configure Emby to use the VPN network for external connections as well as setting the default extremal IP Emby Server uses to communicate with clients so all remote requests go through the VPN.

You will need to configure the VPN to port forward a port to your Emby Server which essentially makes a port available on the VPN connection for unsolicited inbound access that doesn't get blocked/firewalled.

[Luke 42079]

@AmyB0001 please let us know if this helps. Thanks.