ProScan Web Server Playback Pausing Itself

[shanelynn321]

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.)

 

[ProScan]

On the far side, is the pausing issue happening on the same computer and/or router?

I would set up a test Web Server ProScan instance w/ version 23.4. Try one thing at a time and let it run for several days. Something like this:

1 - Use a non-secured http web server and at the far side, use the Listen Live link which will run your default media player.
2 - Use a secured https web server and at the far side, use the Listen Live link.
3 - Use a secured https web server with cloudflare and at the far side, use the Listen Live link.
4 - Try 1 to 3 with the internal media player.

 

[buddrousa]

If Changing Ports fixes the problem then my 1st thought is ISP Blocking Ports or Firewall Antivirus Blocking Ports.
Who is the Internet Provider?
What are you using for Computer Security?
Who Manages the Network you are on?

 

[shanelynn321]

On the far side, is the pausing issue happening on the same computer and/or router?

I would set up a test Web Server ProScan instance w/ version 23.4. Try one thing at a time and let it run for several days. Something like this:

1 - Use a non-secured http web server and at the far side, use the Listen Live link which will run your default media player.
2 - Use a secured https web server and at the far side, use the Listen Live link.
3 - Use a secured https web server with cloudflare and at the far side, use the Listen Live link.
4 - Try 1 to 3 with the internal media player.

1 - This was the original setup.
2 - We tested this for a week and had the same results. Inconsistent disconnects.
3 - Current setup that has been going for about 10 days. Inconsistent disconnects.

The above is in reference to the server running 23.4. We do not have the ability of running a 2nd instance of proscan within the same PC.

 

[shanelynn321]

If Changing Ports fixes the problem then my 1st thought is ISP Blocking Ports or Firewall Antivirus Blocking Ports.
Who is the Internet Provider?
What are you using for Computer Security?
Who Manages the Network you are on?

I thought the same thing, however we are only changing the internal ports, not the external port. The ISP at the 23.4 location is Astound Business and runs fine aside from the listen live or on page player pausing itself, they have no issues there. The ISP at the 23.3 location is Astound Residential and runs over a hundred other servers and services without issue aside from the page pausing itself. I have been troubleshooting this since the middle of December when the ability to listen become near impossible without sitting there watching the screen. As for the network security and management, I have no control of the network at the 23.4 location since it is a business that I am helping out with this feed issue that has been running for years without issue until lately. At the 23.3 location, I manage the network and its security and have verified no changes with firewall settings or antivirus settings.

 

[shanelynn321]

I planned on reporting the runtime for both feeds this morning, however this pc decided to restart for updates without warning. When I left last night, they were both at almost 6 hours with no issue.

EDIT: Which has happened before. I've gotten just under 18 hours on both feeds one day but then less than an hour multiple times after.

 

[shanelynn321]

I planned on reporting the runtime for both feeds this morning, however this pc decided to restart for updates without warning. When I left last night, they were both at almost 6 hours with no issue.

EDIT: Which has happened before. I've gotten just under 18 hours on both feeds one day but then less than an hour multiple times after.

UPDATE: Started both feeds within seconds of each other. 23.4 ran for 2:52:09 while 23.3 ran for 2:45:24. Checked the connections logs to 23.3 and no high latency or disconnections anywhere within the network.

EDIT: 23.4 has already paused at 19:40 while 23.3 is still going at 26:40 currently.

 

[shanelynn321]

UPDATE: Started both feeds within seconds of each other. 23.4 ran for 2:52:09 while 23.3 ran for 2:45:24. Checked the connections logs to 23.3 and no high latency or disconnections anywhere within the network.

EDIT: 23.4 has already paused at 19:40 while 23.3 is still going at 26:40 currently.

23.4 Already paused again at 7:53. EDIT: Feed went offline in this case.
23.3 is at 36:55 and still going.

No more updates. This was to iterate how inconsistent this problem is.

 

[shanelynn321]

23.4 Already paused again at 7:53. EDIT: Feed went offline in this case.
23.3 is at 36:55 and still going.

No more updates. This was to iterate how inconsistent this problem is.

23.4 Had restarted for updates and then ran without issue for 5 1/2 hours.
23.3 ran for just shy of 7 hours.

 

[shanelynn321]

@ProScan Does the web server audio player use websockets or is it just the scanner display that uses them? I occasionally will get websocket errors in the web browser console and since I'm not at the PC and the console doesn't have timestamps, it is hard to tell at what point these pop up.

 

[ProScan]

@ProScan Does the web server audio player use websockets

No

or is it just the scanner display that uses them?

The web page uses a WebSocket if the Push option is selected on the web page.

You probably know this already but just in case. The audio doesn't run through the web page. The media player is a separate stream to the server. Perhaps close the browser when streaming audio to see if that makes a difference.

It's kind of confusing when you are talking about 2 streams and 2 versions of ProScan. I would make a test case like I posted in #2. Maybe step 1 is doing the same thing now. Just change one thing at a time and let it run until it timeouts.

 

[shanelynn321]

You probably know this already but just in case. The audio doesn't run through the web page. The media player is a separate stream to the server. Perhaps close the browser when streaming audio to see if that makes a difference.

We've been using the player built into the web page, not the listen live link. I'll try that on the 23.3 feed since it is the one that I maintain. Only 1 person uses the listen live link on the 23.4 feed.

It's kind of confusing when you are talking about 2 streams and 2 versions of ProScan. I would make a test case like I posted in #2. Maybe step 1 is doing the same thing now. Just change one thing at a time and let it run until it timeouts.

Unfortunately these are 2 different feeds providing 2 different system configurations for different individuals. The 23.3, only I use and have access to. The 23.4 is a non profit that has volunteers from outside the area log in and can listen in. Only reason I know about the issue with 23.3 is because of 23.4. I'll have to start referring to them as Feed 1 (23.4) and Feed 2 (23.3).

I'll let you know what my findings on Feed 2 are since I can do testing on it as the source client is unaffected.