New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue]: Cannot connect after upgrading to 10.9.0 #11534
Comments
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems. |
I was able to fix this by deleting my network.xml |
Same issue but deleting network.xml doesn't fix it for me |
So I got Jellyfin working, but base URL support seems to be broken -- at least for me |
You need to clear browser cache after setting base url, otherwise the old server setting is still stored in browser's local storage which obviously won't work. I agree we could handle this better but for now this is what you have to do. |
Thank you, that fixed it for me. |
Had similar issue and can confirm that deleting the network.xml and restarting the service fixed the issue for me. Only network related change I had done was to allow some remote IPs in 100.64.0.0/10 range (so that I can access the server over Tailscale). Things are working flawlessly otherwise. |
i deleted the xml file from: My current xml file:
UPDATE: Got it working, i have hyper-v installed (so i have virtual nics) ages ago and i had to do this: |
having the same issue, only thing which works is to restart jellyfin.service but if i restart the system, its the same |
i have same issue on window |
same problem for me: [11:54:33] [ERR] [1] Main: Kestrel failed to start! This is most likely due to an invalid address or port bind - correct your bind configuration in network.xml and try again [11:54:33] [FTL] [1] Main: Error while starting server |
issue not resolved in 10.9.1 also, after reboot i have to restart jellyfin.service to make it work |
The original issue is about a stale network config, and if that does not fix the issue for you, then this is not the same issue and please file a new one with complete logs and environment info so that we can look at it. Closing as the original issue is resolved. We are having two other known cause issues:
If none of the above applies to you, please, file a new issue. Thank you. |
Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "223.11.142.10" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake." |
Please describe your bug
I cannot access/connect. I even tried curling via localhost
Reproduction Steps
Jellyfin Version
10.8.13
if other:
10.9.0
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
Code of Conduct
The text was updated successfully, but these errors were encountered: