My UMS server is unreachable
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
My UMS server is unreachable
Hi,
First of all, I would like to thank you for a great media server.
I have been using UMS for a long time with very few issues. After upgrading to version 15.8.2 on a Windows 11 pc, I have not been able to play videoes on my Sharp smart tv from UMS. When I open UMS on my pc, I get a warning that UMS is unreachable. I am attaching my debug files and a screenshot of this warning. How should I fix this issue?
Best regards,
Thor Eric Vågen Jægtnes
First of all, I would like to thank you for a great media server.
I have been using UMS for a long time with very few issues. After upgrading to version 15.8.2 on a Windows 11 pc, I have not been able to play videoes on my Sharp smart tv from UMS. When I open UMS on my pc, I get a warning that UMS is unreachable. I am attaching my debug files and a screenshot of this warning. How should I fix this issue?
Best regards,
Thor Eric Vågen Jægtnes
Re: My UMS server is unreachable
You did not attach your logs. See the section in red above.
It might just be that you need to refresh the page in the browser if it was open before updating or before UMS was fully initialised after starting.
It might just be that you need to refresh the page in the browser if it was open before updating or before UMS was fully initialised after starting.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
Re: My UMS server is unreachable
Hi am am sorry for not uploading the logfiles. I am trying to do this again.
I uninstalled UMS and installed version 15.8.1. Now the media server works. Could this be an issue with version 15.8.2? It was after installing version 15.8.2 that the issue accured.
I uninstalled UMS and installed version 15.8.1. Now the media server works. Could this be an issue with version 15.8.2? It was after installing version 15.8.2 that the issue accured.
- Attachments
-
- ums_dbg_2026-09-19-17-27.zip
- (2.63 MiB) Downloaded 29 times
Re: My UMS server is unreachable
I did not see any errors but did see an exception about the web socket failing to open
I guess this is what transfers the data to the browser.
I don't see why it did not open, just that the result was "null", so maybe something on your computer was blocking it.
I think some of the old Java binaries are being changed due to official support dropping soon so the devs have started to update this.
I know V16 will be using JDK25 where it was previously JDK17, but some of that change may have slipped into the the main branch after work started on V16.
It may be your firewall or antivirus saw the change and blocked it so you might have to manually add it to be allowed.
Code: Select all
DEBUG 2026-09-19 17:25:55.051 [webgui-server-98] net.pms.network.webguiserver.WebSocketEndpoint WebSocket connection opened: fdc165af-d9c7-46c6-9b57-dff318efc89f
DEBUG 2026-09-19 17:25:55.056 [webgui-server-98] net.pms.network.webguiserver.WebSocketEndpoint WebSocket error: null
TRACE 2026-09-19 17:25:55.056 [webgui-server-98] net.pms.network.webguiserver.WebSocketEndpoint Error details: {}
java.nio.channels.ClosedChannelException
at org.eclipse.jetty.websocket.core.internal.WebSocketSessionState.onEof(WebSocketSessionState.java:174)
at org.eclipse.jetty.websocket.core.WebSocketCoreSession.onEof(WebSocketCoreSession.java:220)
at org.eclipse.jetty.websocket.core.WebSocketConnection.fillAndParse(WebSocketConnection.java:546)
at org.eclipse.jetty.websocket.core.WebSocketConnection.onOpen(WebSocketConnection.java:676)
at org.eclipse.jetty.io.AbstractEndPoint.upgrade(AbstractEndPoint.java:423)
at org.eclipse.jetty.server.internal.HttpConnection$HttpStreamOverHTTP1.succeeded(HttpConnection.java:1661)
at org.eclipse.jetty.server.HttpStream$Wrapper.succeeded(HttpStream.java:250)
at org.eclipse.jetty.server.internal.CompletionStreamWrapper.succeeded(CompletionStreamWrapper.java:45)
at org.eclipse.jetty.server.internal.HttpChannelState.completeStream(HttpChannelState.java:738)
at org.eclipse.jetty.server.internal.HttpChannelState$HandlerInvoker.run(HttpChannelState.java:836)
at org.eclipse.jetty.server.internal.HttpConnection.onFillable(HttpConnection.java:420)
at org.eclipse.jetty.server.internal.HttpConnection$FillableCallback.succeeded(HttpConnection.java:1790)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:54)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:1009)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1240)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1194)
at java.base/java.lang.Thread.run(Unknown Source)
DEBUG 2026-09-19 17:25:55.061 [webgui-server-98] net.pms.network.webguiserver.WebSocketEndpoint WebSocket connection closed: fdc165af-d9c7-46c6-9b57-dff318efc89fI don't see why it did not open, just that the result was "null", so maybe something on your computer was blocking it.
I think some of the old Java binaries are being changed due to official support dropping soon so the devs have started to update this.
I know V16 will be using JDK25 where it was previously JDK17, but some of that change may have slipped into the the main branch after work started on V16.
It may be your firewall or antivirus saw the change and blocked it so you might have to manually add it to be allowed.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
Re: My UMS server is unreachable
Hi,
thank you very much for your help! It was the firewall blocking the UMS. I removed the blocking in my firewall, and now UMS works perfectly
thank you very much for your help! It was the firewall blocking the UMS. I removed the blocking in my firewall, and now UMS works perfectly
