local connections using fqdn not seen as local

[inverimus]

I have jellyfin version 10.10.6 and use an nginx reverse proxy to connect to it. I can connect to the server fine using the local IP and FQDN, but when I use the FQDN while on my home network it is treated as a remote connection. I run my own DNS server so requests to my domain locally use the local IP, but jellyfin still treats this as a remote connection and refuses it if remote connections are not allowed. It used to work, but after some update in the last few months it stopped working, but I don't know exactly when and I made no changes to nginx or jellyfin configs during that time.

[TheDreadPirate]

In your DNS server, I'm assuming you resolve your FQDN to your LAN IP? From a client on your network, can you verify that this is actually the case?

Code:

nslookup jellyfin.domain.tld

"nslookup" should work for all OSes, AFAIK.

[inverimus]

In your DNS server, I'm assuming you resolve your FQDN to your LAN IP?  From a client on your network, can you verify that this is actually the case?

Code:

nslookup jellyfin.domain.tld

"nslookup" should work for all OSes, AFAIK.

Address: 192.168.1.130

[TheDreadPirate]

Are your clients on the same subnet as your server? Did add your own CIDRs in Dashboard > Networking > LAN networks?

[inverimus]

Are your clients on the same subnet as your server?  Did add your own CIDRs in Dashboard > Networking > LAN networks?

There is only one local subnet and everything is on that subnet. It worked before without anything in LAN networks, but I did try adding the network there while troubleshooting and it made no difference. I can go to 192.168.1.130:8096 and everything works as expected, but when I use the fqdn from my local network it behaves as if I am remotely accessing it when it didn't used to.