GET connection errors (REFUSED/TIMED_OUT) on app.emby.media to remote server

[pomm 1]

My Emby server is hosted at dediseedbox.com.

Page refreshes and navigation work almost all of the time but occasionally they throw a network error. Sometimes when this happens the Emby page fails to load. A page refresh always sorts it out.

These errors ONLY happen when I use the server via app.emby.media, if I connect directly to {removed}.dediseedbox.com:{their emby port}/web/index.html#! it works perfectly 100% of the time.

Examples of network error are:

• GET https://{removed}.dediseedbox.com:8920/emby/system/info/public net::ERR_CONNECTION_REFUSED
• GET http://172.17.0.146:8096/emby/LiveTv/Channels?userId={removed}-Emby-Client-Version=4.6.3.4&X-Emby-Token=c033c8a… net::ERR_CONNECTION_TIMED_OUT

Are these requests going to the wrong place? I would have expected everything to be requested via app.emby.media.

Anyway, I was wondering whether I need to fix something in my Emby network settings?

Thanks.

[Luke 42079]

They are requested from your directly browser to the address listed, not from our servers. So because of that, I can't really tell you the reason for connection errors in your own network environment.

Connection refused makes it appear like you have something rejecting the request altogether, perhaps a reverse proxy?

 

[pomm 1]

I think that the Connection Refused error is because the request is directed to dediseedbox.com:8920 but that's wrong when the emby server is located at dediseebox.com:60493/web. This only happens for requests to that specific path (emby/system/info/public) and when using app.emby.media to access the emby server.

I have no idea what 172.17.0.146 is, or why any emby requests would go there.

Wouldn't a reverse proxy error also cause issues when I use the dediseedbox.com:60493/web route to emby?

Ta

[Luke 42079]

Quote

but that's wrong

Check the local and remote addresses that are displayed on your emby server dashboard. When you use app.emby.media, or any of our apps besides your built-in web app, they will always test both addresses to see which one should be used. It will test local address first, followed by any manual addresses that you may have entered into the app, followed by the remote address.

So you're saying it's wrong, and I'm saying, well the app isn't just making up the address, it is coming from somewhere.

[Luke 42079]

But the fact that you might see a failed attempt occasionally in the console is nothing to worry about - that is just the app going through the process of figuring out which address to use.

The only time you really would worry is if they all fail and you can't connect at all.

[pomm 1]

6 minutes ago, Luke said:

well the app isn't just making up the addresses

 

I'll check what you suggested and keep digging.

[pomm 1]

Unrelated (I think) but is this js error of interest to you?

 

connectionmanager.js?v=4.6.3.4:1
Uncaught Error: item or serverId cannot be null
at ConnectionManager.value (connectionmanager.js?v=4.6.3.4:1)
at dockedtabs.js?v=4.6.3.4:1
at setMode (dockedtabs.js?v=4.6.3.4:1)
at HTMLDocument.onViewShow (dockedtabs.js?v=4.6.3.4:1)
at viewmanager.js?v=4.6.3.4:1

[Luke 42079]

No, I would start by checking the addresses displayed on your server dashboard. First thing to do is make sure those values are correct because those addresses are what Emby apps will use to try and connect to your server.