HTML5 viewer is not available
Quote from LosscutNice on 14/03/2025, 02:13First of all, thank you for making such a good product
The server PC is running Windows 11 with the latest spacedesk driver and the client devices are running Android and Windows 10 with the latest OS and Chrome.
And the server PC and client devices are all connected to the same wifi.
Wifi connection and Usb connection are all working fine.
The problem is that when I go to the HTML5 viewer site http://viewer.spacedesk.net with the client device and enter the ip address of the server pc, it says Could not connect. Connection Timeout. Make sure your Server-IP is correct.
How can I troubleshoot the problem to use HTML5?
First of all, thank you for making such a good product
The server PC is running Windows 11 with the latest spacedesk driver and the client devices are running Android and Windows 10 with the latest OS and Chrome.
And the server PC and client devices are all connected to the same wifi.
Wifi connection and Usb connection are all working fine.
The problem is that when I go to the HTML5 viewer site http://viewer.spacedesk.net with the client device and enter the ip address of the server pc, it says Could not connect. Connection Timeout. Make sure your Server-IP is correct.
How can I troubleshoot the problem to use HTML5?
Quote from spacedesk Renz on 14/03/2025, 05:40Hi @losscutnice,
The issue with the HTML5 viewer is still under investigation. In the meantime, a workaround you can do to use the HTML5 viewer is to save it locally. To save the page locally, please refer to the Documentation under the section “Run on Any Machine in HTML5 Web Browser“.
Thank you.
Hi @losscutnice,
The issue with the HTML5 viewer is still under investigation. In the meantime, a workaround you can do to use the HTML5 viewer is to save it locally. To save the page locally, please refer to the Documentation under the section “Run on Any Machine in HTML5 Web Browser“.
Thank you.
Quote from dgitter on 17/07/2025, 20:09Renz,
I’ve been battling with this for a year now, and no one has responded to my posts. This recommendation is the first quasi-solution I have seen and does work with chrome on a PC. Can you tell me what is unique about saving the file locally that makes things work? It may help me troubleshoot the issue elsewhere.
Renz,
I’ve been battling with this for a year now, and no one has responded to my posts. This recommendation is the first quasi-solution I have seen and does work with chrome on a PC. Can you tell me what is unique about saving the file locally that makes things work? It may help me troubleshoot the issue elsewhere.
Quote from spacedesk Renz on 18/07/2025, 11:23Hi @dgitter,
The problem is simple: spacedesk HTML5 Viewer hasn’t been maintained for many years! It does not support modern secure encrypted HTTPS and WSS Internet Protocols.
Modern Web Browsers do still allow the old unencrypted cocmmunication protocols, but only for local use (not over the Internet).
BTW: We are planning to update spacedesk HTML5 Viewer to HTTPS,WSS and H264 within the next months. Then it will be fully functional again and even perform much better than before.
Hi @dgitter,
The problem is simple: spacedesk HTML5 Viewer hasn’t been maintained for many years! It does not support modern secure encrypted HTTPS and WSS Internet Protocols.
Modern Web Browsers do still allow the old unencrypted cocmmunication protocols, but only for local use (not over the Internet).
BTW: We are planning to update spacedesk HTML5 Viewer to HTTPS,WSS and H264 within the next months. Then it will be fully functional again and even perform much better than before.
Quote from dgitter on 18/07/2025, 16:02Thanks for that information. That makes sense, and I wish you would have shared that on one of the other threads previously. I believe that those requirements can be bypassed in Chrome, but since my issue is on a SmartTV that ties my hands. That is also preventing me from using a local file, as indicated in your work-around solution (which works perfectly on the PC I tested that on).
Please try to remember to respond to this thread, or otherwise inform me, when you guys roll out that update, as my client would also pay for a commercial license once made available.
Also as an FYI, since I was again dealing with this issue while onsite yesterday, I discovered a competing product called Deskreen from a developer in Ukraine. I am now using it as a workaround on the SmartTV, but his product is not as polished and user-friendly as SpaceDesk. It doesn’t run as a driver in the background on the PC, and connecting the Browser requires the user to enter a unique pairing key each time, making using a bookmark impractical. So I am pleased to tell them today that you guys finally responded, and he is only a few months away from being able to use SpaceDesk again.
Hoping the “next months” mean sometime in 2025. 😉
Thanks again!
Thanks for that information. That makes sense, and I wish you would have shared that on one of the other threads previously. I believe that those requirements can be bypassed in Chrome, but since my issue is on a SmartTV that ties my hands. That is also preventing me from using a local file, as indicated in your work-around solution (which works perfectly on the PC I tested that on).
Please try to remember to respond to this thread, or otherwise inform me, when you guys roll out that update, as my client would also pay for a commercial license once made available.
Also as an FYI, since I was again dealing with this issue while onsite yesterday, I discovered a competing product called Deskreen from a developer in Ukraine. I am now using it as a workaround on the SmartTV, but his product is not as polished and user-friendly as SpaceDesk. It doesn’t run as a driver in the background on the PC, and connecting the Browser requires the user to enter a unique pairing key each time, making using a bookmark impractical. So I am pleased to tell them today that you guys finally responded, and he is only a few months away from being able to use SpaceDesk again.
Hoping the “next months” mean sometime in 2025. 😉
Thanks again!
Quote from spacedesk Renz on 21/07/2025, 03:45Hi @dgitter,
Thanks also for bringing this up. We will make sure to inform this thread once the new HTML5 viewer is out.
Hi @dgitter,
Thanks also for bringing this up. We will make sure to inform this thread once the new HTML5 viewer is out.
Quote from dgitter on 17/11/2026, 16:25Renz,
It’s been over a year since you stated that an HTML5 update will be out in a few months. Where are you at with this. We have multiple SmartTVs sitting idle that were deployed when it was originally working. It passed our Proof of Concept tests, and then a few months later it stopped working.
Dave
Renz,
It’s been over a year since you stated that an HTML5 update will be out in a few months. Where are you at with this. We have multiple SmartTVs sitting idle that were deployed when it was originally working. It passed our Proof of Concept tests, and then a few months later it stopped working.
Dave
Quote from spacedesk Renz on 18/11/2026, 13:54Hi @dgitter,
Unfortunately, the HTML5 Viewer has been discontinued and will not be supported anymore.
Hi @dgitter,
Unfortunately, the HTML5 Viewer has been discontinued and will not be supported anymore.
Quote from dgitter on 18/11/2026, 15:22WOW, I can’t even express my disappoint with that. For months you said it was being worked on and would be done in a couple of months, without any status updates. Now to hear that it was abandoned is mind blowing. Gives new meaning to “Delay, Delay, Die….”
It was a perfectly working solution for nearly a year, until it wasn’t. It allowed a clean solution with most Smart TVs, with no additional hardware. I don’t get it. You released an iOS version that is useless for this scenario (I can’t stick and iPad behind the TV), but still no tvOS version that would work and be a perfect cost effective alternative with a minimal footprint. How about a Linux based viewer? With that we can build a solution on a Rasberry Pi. You’ve left me no alternative other that sticking an EXPENSIVE Windows PC (like a NUC) back there or using difficult to support / secure Android devices.
Is there anything useful on the roadmap for me? 🙁
WOW, I can’t even express my disappoint with that. For months you said it was being worked on and would be done in a couple of months, without any status updates. Now to hear that it was abandoned is mind blowing. Gives new meaning to “Delay, Delay, Die….”
It was a perfectly working solution for nearly a year, until it wasn’t. It allowed a clean solution with most Smart TVs, with no additional hardware. I don’t get it. You released an iOS version that is useless for this scenario (I can’t stick and iPad behind the TV), but still no tvOS version that would work and be a perfect cost effective alternative with a minimal footprint. How about a Linux based viewer? With that we can build a solution on a Rasberry Pi. You’ve left me no alternative other that sticking an EXPENSIVE Windows PC (like a NUC) back there or using difficult to support / secure Android devices.
Is there anything useful on the roadmap for me? 🙁