Local Host Not working when no local network - (emby server exiting after launch)

[Piperel 4]

When android server is offline, It appears to be attempting to run the server off the devices mac address and not from local host. The result is that if the device is not connected to wifi or cell service, an emby client on the same device will not work as it has in the past. I am running emby android server and client from my Retroid pocket 5. I use it to view emby both from the device or by streaming to a roku on the network, screen cast, or over the retroid pocket 5s hotspot to my phone or other device. 

[Luke 42077]

Quote

It appears to be attempting to run the server off the devices mac address and not from local host.

Hi there, can you please describe what you mean by this in more detail? Thanks.

[Piperel 4]

Sure. If I turn of the wifi on this device and open the server I see http://[fe80::7043:7043:18ff:fedd:582b%3]:8096. At this point sometimes the server crashes. sometimes the client does not recognizes the host and sometimes it pops in and works. The only consistent way on this devices since the last update to see the content is to be connected to an outside network.

[Piperel 4]

This android device runs Android 13 without a sim card. I believe it use to show http://localhost:8096 when offline in the past and would work perfectly on the local client. 

[Luke 42077]

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[Piperel 4]

hardware_detection-63899165097.txthardware_detection-63899165048.txthardware_detection-63899165037.txthardware_detection-63899164987.txtembyserver-63899165091.txtembyserver-63899165043.txtembyserver-63899165033.txtI hope this helps.

[Piperel 4]

MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: hostname nor servname provided, or not known (www.mb3admin.com:443)
     ---> System.Net.Http.HttpRequestException: hostname nor servname provided, or not known (www.mb3admin.com:443)
     ---> System.Net.Sockets.SocketException (0xFFFDFFFF): hostname nor servname provided, or not known
       at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
       at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)

[ebr 16168]

17 hours ago, Piperel said:

MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: hostname nor servname provided, or not known (www.mb3admin.com:443)
     ---> System.Net.Http.HttpRequestException: hostname nor servname provided, or not known (www.mb3admin.com:443)
     ---> System.Net.Sockets.SocketException (0xFFFDFFFF): hostname nor servname provided, or not known
       at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
       at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)

 

On 11/18/2025 at 3:20 PM, Piperel said:

when offline

If you are offline, the above would be expected - there is no DNS and no way to route to an internet address.  Perhaps this lack of any DNS also makes "localhost" not resolve.  What happens if you use the device IP?

[Piperel 4]

I understand although it did resolve as local host in past versions and could be used offline such as when I was on the road. It would be amazing to get the offline working again so that an android device could have both the server and client and could be used independently and not just to stream to other devices on a network. 

[Luke 42077]

Are you connected to any kind of router that provides a local network?

[Luke 42077]

Also try using 127.0.0.1 instead of localhost.

[Piperel 4]

24 minutes ago, Luke said:

Are you connected to any kind of router that provides a local network?

No I am shutting the wifi completely off on the device. 

[Piperel 4]

27 minutes ago, Luke said:

Also try using 127.0.0.1 instead of localhost.

When trying both http://localhost or 127.0.0.1 I receive the text: Unable to Reach Server. Now just for fun I installed a webserver on the same device and put it under the same conditions and that server functioned properly and as expected. I think if you were to change your code so it did not error out but served its content on localhost. I feel it might be successful. 

[ebr 16168]

29 minutes ago, Piperel said:

When trying both http://localhost or 127.0.0.1 I receive the text: Unable to Reach Server. Now just for fun I installed a webserver on the same device and put it under the same conditions and that server functioned properly and as expected. I think if you were to change your code so it did not error out but served its content on localhost. I feel it might be successful. 

I'm pretty sure you are never getting to our software.  It is the network layer that is not routing to us.  If you've disabled the network, it isn't going to work though...

[Piperel 4]

17 hours ago, ebr said:

I'm pretty sure you are never getting to our software.  It is the network layer that is not routing to us.  If you've disabled the network, it isn't going to work though...

I am wondering then why it worked before and also for any other server app I have ever installed on this device. Is this something you guys could look into correcting? Thank you.

[Piperel 4]

You have a great product and having an Android server really sets you apart especially when not used in the traditional sense, but turned on as wanted has huge benefits. Like taking your media with you on cruises, camping, road trips, traveling, or even work. It allows you keep your info on the local network without exposing yourself to the full internet. It also helps prevent the need for data usage or firewall issues. There are times when you might not want to expose yourself to the local network or there is no local network available. It would be good to get this working again for times like that. I have full faith you guys can restore that feature weather it was originally intended or not it is something that did set your service apart. 

Edited November 21, 2025 by Piperel

[Neminem 1515]

2 hours ago, Piperel said:

cruises, camping, road trips, traveling

Should you not just enjoy your travle / trip

2 hours ago, Piperel said:

or even work

Get back to work  

[ebr 16168]

23 hours ago, Piperel said:

Is this something you guys could look into correcting?

The issue is at the network layer on the device. That is not something the app can control.

[Luke 42077]

@Piperelhas this helped?

[sa2000 673]

On 18/11/2025 at 20:10, Piperel said:

If I turn of the wifi on this device and open the server I see http://[fe80::7043:7043:18ff:fedd:582b%3]:8096

for some reason it is picking up ipv6 ip address

Have you tried leaving wifi enabled - but not connected to any wifi network and then try 127.0.0.1:8096 ?

 

[Piperel 4]

Thank you I will give that a shot and report back and report back after the holiday. 

[Luke 42077]

OK please keep us posted. Thanks.

[Piperel 4]

On 11/25/2025 at 2:41 PM, sa2000 said:

for some reason it is picking up ipv6 ip address

Have you tried leaving wifi enabled - but not connected to any wifi network and then try 127.0.0.1:8096 ?

 

I gave this a try and still ended up with the same issue. Again this worked in earlier versions. Is this a bug that will need to be addressed in the next update?

[sa2000 673]

which version change resulted in this no longer working ? is it the server or the app?

Do you recall the version numbers combinations for Emby for Android app and Emby Server for Android?

[Piperel 4]

1 hour ago, sa2000 said:

which version change resulted in this no longer working ? is it the server or the app?

Do you recall the version numbers combinations for Emby for Android app and Emby Server for Android?

The server app began having this issue I believe after 4.8.11.0. I believe it worked on 4.8.11.0 just not after.