"Connection Reset" and IPv4 and IPv6 issues with access to subset of Apps

TrueNAS General
1

I have a very strange networking problem accessing my Apps. Everything had been as good as gold until after I restarted one of my un-managed switches, and now Mozilla Firefox on any computer or tablet in the house (but interestingly not always Chrome or Edge on some computers) gives me a Connection Reset error

image
image831×341 13.5 KB

But this only happens when tryingg to access certain apps such as Deluge and Jellyfin, but things like Syncthing, Scrutiny and Crafty all work fine.

So, the following all work fine

https://truenas.local - ie, the main TrueNAS dashboard

http://truenas.local:30064/ - Dozzle

https://truenas.local:8443 - Crafty

The following don’t

http://truenas.local:8112/ - Deluge

http://truenas.local:30013 - Jellyfin

What I’ve found is if I go in via IPv4 - rather than local hostname (ie, 192.168.0.200 in my case as the IP for my TrueNAS Server) - then all the apps can be accessed. But if I go in via IPv6 ([fe80::b499:beff:fe45:ae3b] in my case as the IP for my TrueNAS server) then all apps aside from Deluge and Jellyfin can be accessed. And I get the same “Connection Reset” error just for these two apps.

I’m really confused as how can an IPv4 address work across the board for any app, yet an IPv6 address can’t, but for only two of the apps I’m running.

I’ve restarted everything from scratch, bringing up my internet first, then the switches, then router and mesh network, then Truenas server and still the same issue.

Am really befuddled. Any advice greatly appreciated.

2

Isn’t this evidence of a Firefox bug or configuration issue?

3

At least one problem might be that your network doesn’t configure routeable IPv6 addresses which internet browsers are expecting.

If you’re relying on a link-local address to reach a host on the same subnet then you’d need to specify an additional zone id so the application knows which actual interface to use. The problem is that browsers don’t universally support that.

Since you mentioned IPv4 access works, you could have a DNS issue.

What does it return for ‘truenas.local’? Does it contain an A (IPv4) record? If so, then your browser should be falling back to IPv4 if it can’t reach the host by IPv6.

1 Like
4

Thanks all. I ended up resetting and restarting everything again. Not sure what the key change was. I included resetting the network config in the Apps section of TrueNAS. I also reset my router to IPv4 only and then back to IPv6. It’s now working again.

1 Like