Jump to content

Cannot Connect via Connect


negativzeroe

Recommended Posts

negativzeroe

My server is remote enabled, just noticed the issue today. Android app and app.emby.media on any remote device say the server is offline. If I plug in http://DDNS:8096/ it's good.

 

I've tried removing and re-adding the emby connect account on the server to no avail.

Link to comment
Share on other sites

negativzeroe

Yes, it has IP:8096 under LAN address, and DDNS:8096 directly under it under WAN address.

Again this had to have happened within the week as I was playing music on it at work last week.

Edited by negativzeroe
Link to comment
Share on other sites

negativzeroe

apphost.js:1:4387
triggering app resume event
apphost.js:1:4262
Error opening web socket: Error: Cannot open web socket without access token.
apiclient.js:1:15871
begin connectToServer
connectionmanager.js:1:19988
tryReconnect: http://<LOCALIP>:8096|http://<DDNS> :8096
connectionmanager.js:1:10867
getTryConnectPromise http://<LOCALIP>:8096
connectionmanager.js:1:9720
ConnectionManager requesting url: http://<LOCALIP>:8096/system/info/public
connectionmanager.js:1:2483
fetchWithTimeout: timeoutMs: 20000, url: http://<LOCALIP>:8096/system/info/public
connectionmanager.js:1:1893
fetchWithTimeout: timed out connecting to url: http://<LOCALIP>:8096/system/info/public
connectionmanager.js:1:2283
ConnectionManager request failed to url: http://<LOCALIP>:8096/system/info/public
connectionmanager.js:1:2852
Reconnect failed to http://<LOCALIP>:8096
connectionmanager.js:1:10023
Blocked loading mixed active content “http://<LOCALIP>:8096/system/info/public”[Learn More]
connectionmanager.js:1:2093
getTryConnectPromise http://<DDNS> :8096
connectionmanager.js:1:9720
ConnectionManager requesting url: http://<DDNS> :8096/system/info/public
connectionmanager.js:1:2483
fetchWithTimeout: timeoutMs: 20000, url: http://<DDNS> :8096/system/info/public
connectionmanager.js:1:1893
fetchWithTimeout: timed out connecting to url: http://<DDNS> :8096/system/info/public
connectionmanager.js:1:2283
ConnectionManager request failed to url: http://<DDNS> :8096/system/info/public
connectionmanager.js:1:2852
Reconnect failed to http://<DDNS> :8096
connectionmanager.js:1:10023
Will-change memory consumption is too high. Budget limit is the document surface area multiplied by 3 (911872 px). Occurrences of will-change over the budget will be ignored.
selectserver.html
Link to comment
Share on other sites

negativzeroe

@@Luke Same as before, cannot connect to server. Note this is from adding my connect account via the server under user properties.

 

 

 

If I manually add a server, put DDNS for the address (without hypertext), it does not work. If I actually type out the hypertext (http://DDNS) it does work and proceeds to prompt for login, so it's something with adding it under user properties maybe? However I should note, that I have another server that is also set up the same way under user properties and is also going through HTTP and it does work. Only difference is that is a Linux server. Both are on 3.4.1.0. Hopefully this little bit of extra info helps.

 

Edit with both screenshots.

post-23438-0-63707400-1528220478_thumb.png

post-23438-0-73709500-1528220482_thumb.png

Edited by negativzeroe
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...