mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: Cannot connect after upgrading to 10.9.0 #5683
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Inovvia on GitHub (May 11, 2024).
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
@jellyfin-bot commented on GitHub (May 11, 2024):
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.
@Inovvia commented on GitHub (May 11, 2024):
I was able to fix this by deleting my network.xml
@goratchet766 commented on GitHub (May 12, 2024):
Same issue but deleting network.xml doesn't fix it for me
@goratchet766 commented on GitHub (May 12, 2024):
So I got Jellyfin working, but base URL support seems to be broken -- at least for me
@gnattu commented on GitHub (May 12, 2024):
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.
@steffbp commented on GitHub (May 12, 2024):
Thank you, that fixed it for me.
@piyushrungta25 commented on GitHub (May 12, 2024):
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.
@Cl4whammer commented on GitHub (May 12, 2024):
i deleted the xml file from:
C:\ProgramData\Jellyfin\Server\config
After system/service restart no new xml file was genereated, so i went to network settings and pressed the save button. After that new xml file generated. But still can only access server with localhost, other pcs cant load the page, even with fresh browsers.
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:
https://github.com/jellyfin/jellyfin/issues/11548#issuecomment-2106100017
@chiragkrishna commented on GitHub (May 12, 2024):
having the same issue, only thing which works is to restart jellyfin.service
sudo systemctl restart jellyfin.servicebut if i restart the system, its the same
@faisalalsalm commented on GitHub (May 12, 2024):
i have same issue on window
@spupuz commented on GitHub (May 12, 2024):
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
@chiragkrishna commented on GitHub (May 13, 2024):
issue not resolved in 10.9.1 also, after reboot i have to restart jellyfin.service to make it work
@gnattu commented on GitHub (May 13, 2024):
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:
veth*pattern to connect to outside should setIgnoreVirtualInterfacestofalseas described in #11548, this affects Hyper-V users on Windows most.If none of the above applies to you, please, file a new issue. Thank you.
@daixy2021 commented on GitHub (May 20, 2024):
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."