The web interface works well and smoothly for about five minutes. After that, it becomes inaccessible via the browser. However, you can still use it correctly and without any issues on the computer that runs it. If you close and restart it, it works fine again for another five minutes. This problem did not exist in previous versions.
I'm running Windows 10 22H2.
I'm not sure what other information I can provide to help you better understand the problem.
P.S.: I'm not sure if this problem still exists in QLC+ 4.14.1-1. I had to downgrade to 4.14.0 due to an issue with the audio, as mentioned in other threads.
web interface stops working
- mcallegari
- Posts: 4932
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Which browser are you using?
Do you close and re-open the browser during those 5 minutes or leave it open?
Do you close and re-open the browser during those 5 minutes or leave it open?
-
- Posts: 8
- Joined: Tue Feb 25, 2025 9:10 pm
- Real Name: Alessandro
Hi everyone,
I came across this topic by chance but I'll take this opportunity to tell you what happened to me about it.
I also use QLC+ 4 on Windows 10. During a show I use an iPad with the Safari browser to connect to the web interface. I've never had any problems, however a few nights ago the web interface stopped working. In any case, it was always possible to use QLC on the Windows PC that was running the software.
In my case too, after finishing the show, I tried closing and reopening the program and the problem was solved.
A possible cause of the problem that I imagined is that, since there weren't many light changes in that show, the iPad often went into standby, turning off the screen. When I went to unlock it, maybe the Wi-Fi also went into standby and consequently when the Wi-Fi also turned on again, it was as if there was a bug with the socket ports that after standby were seen as "already occupied". But it's just my thought.
I came across this topic by chance but I'll take this opportunity to tell you what happened to me about it.
I also use QLC+ 4 on Windows 10. During a show I use an iPad with the Safari browser to connect to the web interface. I've never had any problems, however a few nights ago the web interface stopped working. In any case, it was always possible to use QLC on the Windows PC that was running the software.
In my case too, after finishing the show, I tried closing and reopening the program and the problem was solved.
A possible cause of the problem that I imagined is that, since there weren't many light changes in that show, the iPad often went into standby, turning off the screen. When I went to unlock it, maybe the Wi-Fi also went into standby and consequently when the Wi-Fi also turned on again, it was as if there was a bug with the socket ports that after standby were seen as "already occupied". But it's just my thought.
- mcallegari
- Posts: 4932
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
The current websocket implementation allows multiple and simultaneous connections.
Also, QLC+ continuosly sends a keepalive message to the browser to keep the connection up.
If the network interface goes down, then most likely the connection is closed, but a F5 or CTRL+F5 on the browser side should resume it.
In any case I doubt this is a QLC+ issue.
Also, QLC+ continuosly sends a keepalive message to the browser to keep the connection up.
If the network interface goes down, then most likely the connection is closed, but a F5 or CTRL+F5 on the browser side should resume it.
In any case I doubt this is a QLC+ issue.
-
- Posts: 8
- Joined: Tue Feb 25, 2025 9:10 pm
- Real Name: Alessandro
This is strange. That evening, in fact, I also remember trying to connect from the Safari browser on my iPhone, but it was inaccessible from there too. I also tried, during the show, to turn the iPad's wi-fi off and on again but there was nothing to do. I also tried from the same PC that was running QLC+, but nothing to do too.mcallegari wrote: ↑Sun Mar 16, 2025 5:09 pm The current websocket implementation allows multiple and simultaneous connections.
But, just to know, maybe there is a command to run on the prompt or directly from the QLC+ software with which you can restart the websocket?
-
- Posts: 27
- Joined: Tue Dec 03, 2024 10:59 am
- Real Name:
I'm experiencing this issue too.
-
- Posts: 9
- Joined: Tue Feb 25, 2025 12:25 pm
- Real Name: bill kolias
I was testing the new version and thought the issue was resolved, but it’s still happening. The problem occurs very randomly and takes much longer now.mcallegari wrote: ↑Sat Mar 15, 2025 5:54 pm Which browser are you using?
Do you close and re-open the browser during those 5 minutes or leave it open?
I’m using Chrome on another Windows computer, and the page remains open the entire time. Based on my previous experience, even if I closed the tab, I could reopen it at any time. Even if the tab timed out, refreshing would make it work again. However, that’s no longer the case.
I’ve recorded a short video to demonstrate the issue.
https://youtube.com/shorts/zIIJmDVxemk
Ps:if you press stop and again play it works again normally
- mcallegari
- Posts: 4932
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
The thing is that web interface haven't been touched from 4.14.0 to 4.14.1 so QLC+ should behave the same
-
- Posts: 8
- Joined: Tue Feb 25, 2025 9:10 pm
- Real Name: Alessandro
I'm checking right now, and I had this bug with version 4.14.0. I haven't upgraded to 4.14.1 yet.mcallegari wrote: ↑Mon Mar 17, 2025 8:39 am The thing is that web interface haven't been touched from 4.14.0 to 4.14.1 so QLC+ should behave the same
-
- Posts: 9
- Joined: Tue Feb 25, 2025 12:25 pm
- Real Name: bill kolias
Yes, as I mentioned, I first encountered this problem in version 4.14.0.mcallegari wrote: ↑Mon Mar 17, 2025 8:39 am The thing is that web interface haven't been touched from 4.14.0 to 4.14.1 so QLC+ should behave the same
-
- Posts: 28
- Joined: Sat Aug 03, 2024 9:03 pm
- Real Name:
Hi, this might have been fixed by https://github.com/mcallegari/qlcplus/pull/1749. If you are willing to test, then try to grab a development build. See the download page, section "Development Builds" on how to obtain one.