Clients losing connection to Server

#1

At Home.
Clients losing connection to Server.
I have been having this problem lately.
On Firestick 4K, Onn 4k Android TV box, iPhone.
I am on the current stable release 2023.01.23.1746.
The Guide comes up empty or it says server not found or some such.
I say connect to server, then Try Again, nothing works.
It goes to the At Home selection, I select that and enter the Server IP addrs.
It says Server not found at that address.
I try to use my iPhone to go to the Web UI to uncheck, Re-check Bonjour, but iPnone also cannot get to Server.
Other Clients are getting to the Server.
I finally go to my Win 11 laptop, go to the web UI, uncheck Bonjour, recheck Bonjour.
Now all is OK.
What is going on???
Not good, wife getting pissed.
Thanks for any suggestions.
LOG

2023/03/27 21:22:18 [Recovery] 2023/03/27 - 21:22:18 panic recovered:
write tcp 192.168.0.217:8089->192.168.0.197:56752: wsasend: An established connection was aborted by the software in your host machine.
github.com/gin-gonic/[email protected]/render/json.go:58 (0x636e5e)
github.com/gin-gonic/[email protected]/context.go:899 (0x63c8b7)
github.com/gin-gonic/[email protected]/context.go:942 (0x121edc5)
github.com/fancybits/channels-server/http_device.go:369 (0x121ed79)
github.com/gin-gonic/[email protected]/context.go:169 (0x121ed0d)
github.com/fancybits/channels-server/http_device.go:360 (0x121ec47)
github.com/gin-gonic/[email protected]/context.go:169 (0x121be81)
github.com/fancybits/channels-server/http_device.go:87 (0x121bdac)
github.com/gin-gonic/[email protected]/context.go:169 (0x1213c03)
github.com/fancybits/channels-server/http.go:273 (0x12138f7)
github.com/gin-gonic/[email protected]/context.go:169 (0x121386a)
github.com/fancybits/channels-server/http.go:250 (0x121384f)
github.com/gin-gonic/[email protected]/context.go:169 (0x1213727)
github.com/fancybits/channels-server/http.go:242 (0x121309a)
github.com/gin-gonic/[email protected]/context.go:169 (0x6457c1)
github.com/gin-gonic/[email protected]/recovery.go:107 (0x6457ac)
github.com/gin-gonic/[email protected]/context.go:169 (0x644906)
github.com/gin-gonic/[email protected]/logger.go:240 (0x6448e9)
github.com/gin-gonic/[email protected]/context.go:169 (0xd630b9)
github.com/gin-contrib/[email protected]/sessions.go:65 (0xd630a5)
github.com/gin-gonic/[email protected]/context.go:169 (0xd5d2c1)
github.com/gin-contrib/[email protected]/gzip.go:47 (0xd5d299)
github.com/gin-gonic/[email protected]/context.go:169 (0x12144a5)
github.com/fancybits/channels-server/http.go:363 (0x1214491)
github.com/gin-gonic/[email protected]/context.go:169 (0x643a10)
github.com/gin-gonic/[email protected]/gin.go:598 (0x643678)
github.com/gin-gonic/[email protected]/gin.go:554 (0x6431b1)
net/http/server.go:2947 (0x33968b)
net/http/server.go:1991 (0x334966)
runtime/asm_amd64.s:1594 (0x7ef20)

2023/03/27 21:22:35.411193 [TVE] stream timestamps: cnni: start_at=2023-03-27T21:12:27-05:00 end_at=2023-03-27T21:22:20-05:00 live_delay=8.5581934s
2023/03/27 21:22:35.411193 [TNR] Opened connection to TVE-Cox for ch6032 CNNI
2023/03/27 21:22:35.449489 [HLS] Starting live stream for channel 6032 from 127.0.0.1 (bitrate=4549)
2023/03/27 21:22:36.823905 [HLS] Probed live stream in 1.3692305s: h264 1280x720 progressive 1891370bps
2023/03/27 21:22:43.105196 [HLS] Stopping transcoder session ch6032-dANY-ip127.0.0.1 (out: 0s, finished: false)
2023/03/27 21:22:43.114165 [TNR] Closed connection to TVE-Cox for ch6032 CNNI
2023/03/27 21:22:43.130349 [SNR] Buffer statistics for ch6032 CNNI: buf=0% drop=0%
#2

Is your server IP changing? Maybe need static dhcp reservation

#3

It never changed for the first year I had Channels,
Then It changed about a month or two ago (not sure how long), and hasn't changed since.
I have wondered if somehow the old IP addrs is still lurking somewhere within Channels and gets pulled up.
Is that possible and if so, how would I clear it.

#4

Seems like some issue with your router

#5

Here is the only thing going on that "may" be the culprit... But I don't see how.
If the devs or anyone in the community can shed some light please educate me.
.
About 8 months ago, on the Firestick, (where I most recently had the Channels Server not found issue)
I had changed the Silk Browser Settings to use a Secure DNS to block ads.
h t t p s://dns.adguard.com/dns-query
I had no problems with the browser, Channels or Laptop IP addrs, but I changed about a month ago to this:
h t t p s://dns.adguard-dns.com/dns-query
The url only changed by adding -dns after adguard
.
I believe when I changed this about a month ago from the one above to this new url is "maybe" when my Laptop IP addrs changed, and I changed all Channels devices to the new Laptop IP addrs.
.
And it seems to me, this is when I started having the Channels server not found, sporadically,
perhaps after using the Internet Silk Browser on the Firestick and thus this adguard stuff,
NOTE: the Laptop IP addrs is not changing, it only changed that one time.
I don't know much about DNS, DHCP etc but I don't see how this could be the culprit.
It just seems like the Firestick, Android TV devices etc loose the connection
and even if I re-enter it manually on the At Home screen it still says Server not found at that address.
Only un-checking and re-checking Bonjour seems to allow finding the Server again.
I thought the Clients were supposed to automatically find the Server if it lost connection.

#6

When it stops working on your TV, can you access this link http://192.168.0.217:8089 from phone browser? If not, then either the router or the PC is not allowing connections

#7

No, the iPhone cannot get to that Settings page ui when the Server not found issue arises.
I have to go to the Laptop (which is hard wired to router) to do the Bonjour thing.
Good thing that woks !!

#8

Try updating to prerelease, and submit diagnostics from the DVR when it happens next time.

1 Like
#9

Hmmm, I knew you'd say that.
I follow those pre-releases and subsequent comments closely,
and have decided to avoid them and wait for Stable releases.
"If it ain't broke don't fix it"
is my standard , and Channels hasn't given me trouble for quite a while.
But if it gets worse I'll try that, at least I have the Bonjour thing.
Is there a way for Bonjour to automatically run when a Client reports a Server Not Found??
Thanks for the replies.
You guys are the best.

#10

If it's enabled on the DVR web UI, it should always be running.

And besides, how would the server know when a client couldn't connect to it?
The server advertises itself with Bonjour and the Clients listen for the advertisements.

DVR: Bonjour World. I'm here and available
Client: Bonjour Channels DVR Server

#11

Yes it IS always running.
BUT when my Client loses connection and it DOES NOT see the "advertisements"
I have to stop and restart Bonjour (check/uncheck) manually.
And yes I suspect the Server might not know if a Client has lost connection.
Unless someone (Developers) can tell me that Bonjour only sends out the "advertisements" every 30 minutes or something
then I must stop/restart Bonjour manually..
And if that is the case, advertise only every ___ minutes
Then maybe we can have a time frame for advertising, every ___ minutes.
And I suspect that would not be a great idea, Bonjour might then flood the network with advertising

#12

The issue is not related to bonjour.

It sounds to me like some other device on your network is trying to use the same IP as your DVR.

When you toggle bonjour, it sends an ARP packet that reassociates your PC with the IP address.

I would recommend picking a new IP and setting that as a static DHCP reservation on your router with the MAC addr of the PC.

2 Likes
#13

Thanks for reply.
I looked into that DHCP reservation a little, I will do a little more before I mess it up worse.
.
One more question, when I do At Home and enter the Server IP manually (which it does not find)
Do I need to have the :8089 at the end??
I do not put that because it never shows that on Settings page.

#14

No you don't need the :8089 or http, just the IP

#15

Mine started doing something like this today. I discovered my Windows server switched the Wi-Fi connection to a "Public Network" somehow. I'm not sure why--I did have an update to my Unifi Dream Machine router today that perhaps caused the Windows laptop to detect the Wifi network as a different network, thus switching it to public? In any case, I switched the Wifi network back to private, and Channels started working again. Try checking that out.

#16

My IP4 address starts with 192.168 so I am Private, but thanks for the reply.
I am just going to watch it,
I'd love to KNOW what is causing the disconnect so I can reproduce,
before I start putting in "possible" fixes.
But with Tech/computers, sometimes you will never KNOW, too many variables and combinations.
.
" How do I know if my network address is public or private?
The way to tell is to reference a standard used by TCP/IP:

  1. An IPv4 address beginning with any of the following is a private address: 172.16., 172.17., 172.18, etc up to 172.30. and 172.31. 192.168.
  2. Otherwise it's a public IPv4 address
#17

127.127.127.127 or 10.10.10.10 are private

1 Like
#18

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.