Hello All,
I've been talking to Bob over at Proscan and he suggests seeing if anyone else is having this issue.
I have 2 different instances of Proscan on 2 different PCs with different licenses, both at different locations and different internet; you get the point.
The issue I am having is that both feeds are auto-pausing the playback at sporadic times and I cannot seem to narrow down the issue. One location is running the latest version, 23.4, while the other is still on 23.3.
The 23.4 feed used to be accessed via the IP and port directly, however, in the last month, we started having timeouts. We could not access the page unless we stopped the web server, changed the port, and then updated the port on the router. This would work for a day or two. I did later discover that using a self signed certificate and forcing an ssl warning page helped get past the endless loading page that was blank. Since I discovered that, I set up a cloudflare tunnel to give ssl without any ssl errors. This solved our access issue.
The 23.3 feed has been set up this way for years, however I never really tested the web server side of things as this feed goes to broadcastify. Since having the issues with the 23.4 feed, I discovered the that 23.3 feed has the same issue.
A couple of forums suggested turning off http/3 (with QUIC) in the cloudflare settings (which I did) and this did not solve our problem. (Ran a live log on the cloudflare tunnels and was getting QUIC connection errors)
To give some perspective, we can go 10 minutes and the feed auto-pause, or we can go as much as 17 hours before the feed auto-pauses. Both internet connections are using enterprise routers with gig internet connections, so upload is not an issue.
Anyone have any ideas on what could be causing these feeds to just stop?
(At the time of posting this, the 23.4 feed had stopped twice today at less than an hour and is currently at 2 hours and 45 minutes. The 23.3 feed has stopped once and is also around 2 hours and 45 minutes.)
(We have also tried using the Listen Live link to get a stream.m3u file and use media player, and will lose the stream just the same.)
I've been talking to Bob over at Proscan and he suggests seeing if anyone else is having this issue.
I have 2 different instances of Proscan on 2 different PCs with different licenses, both at different locations and different internet; you get the point.
The issue I am having is that both feeds are auto-pausing the playback at sporadic times and I cannot seem to narrow down the issue. One location is running the latest version, 23.4, while the other is still on 23.3.
The 23.4 feed used to be accessed via the IP and port directly, however, in the last month, we started having timeouts. We could not access the page unless we stopped the web server, changed the port, and then updated the port on the router. This would work for a day or two. I did later discover that using a self signed certificate and forcing an ssl warning page helped get past the endless loading page that was blank. Since I discovered that, I set up a cloudflare tunnel to give ssl without any ssl errors. This solved our access issue.
The 23.3 feed has been set up this way for years, however I never really tested the web server side of things as this feed goes to broadcastify. Since having the issues with the 23.4 feed, I discovered the that 23.3 feed has the same issue.
A couple of forums suggested turning off http/3 (with QUIC) in the cloudflare settings (which I did) and this did not solve our problem. (Ran a live log on the cloudflare tunnels and was getting QUIC connection errors)
To give some perspective, we can go 10 minutes and the feed auto-pause, or we can go as much as 17 hours before the feed auto-pauses. Both internet connections are using enterprise routers with gig internet connections, so upload is not an issue.
Anyone have any ideas on what could be causing these feeds to just stop?
(At the time of posting this, the 23.4 feed had stopped twice today at less than an hour and is currently at 2 hours and 45 minutes. The 23.3 feed has stopped once and is also around 2 hours and 45 minutes.)
(We have also tried using the Listen Live link to get a stream.m3u file and use media player, and will lose the stream just the same.)
