I’ve recently updated to the current update for FreeBSD/FreeNas.
I did a fresh install because no posters, banners, backgrounds are being fetched when updating.
Current OS is FreeNas, with plex installed through pkg. Version 1.1.3.2700 is what’s on there now. I had this same issue on the previous release as well.
I have not tried rolling back to a install before those 2. I wanted to see if anyone else is having this same issue, and if you are, is it solved and how did you solve it.
This is apparently a problem for any FreeBSD user running Plex in a jail. Jails don’t have loopback addresses. There is a simple fix: go to Settings, Server, Network, hit Advanced. In “List of IP addresses and networks that are allowed without auth” box put the IP address of the server/jail.
I hope future versions of Plex automatically handle this.
@feld said:
This is apparently a problem for any FreeBSD user running Plex in a jail. Jails don’t have loopback addresses. There is a simple fix: go to Settings, Server, Network, hit Advanced. In “List of IP addresses and networks that are allowed without auth” box put the IP address of the server/jail.
I hope future versions of Plex automatically handle this.
Thnx this fixed it.
Anyway it work perfectly before, curious why this is now needed. The issue started one releases before.
@feld said:
This is apparently a problem for any FreeBSD user running Plex in a jail. Jails don’t have loopback addresses. There is a simple fix: go to Settings, Server, Network, hit Advanced. In “List of IP addresses and networks that are allowed without auth” box put the IP address of the server/jail.
I hope future versions of Plex automatically handle this.
Thanks, this got me fixed right up! Guess updates don’t fix things anymore
@feld said:
This is apparently a problem for any FreeBSD user running Plex in a jail. Jails don’t have loopback addresses. There is a simple fix: go to Settings, Server, Network, hit Advanced. In “List of IP addresses and networks that are allowed without auth” box put the IP address of the server/jail.
I hope future versions of Plex automatically handle this.
Thnx this fixed it.
Anyway it work perfectly before, curious why this is now needed. The issue started one releases before.
I’m guessing they added some security controls. This makes sense, but running in a jail has a few unusual quirks the devs were probably not aware about. Eg, when you try to access 127.0.0.1 you’re actually accessing the main IP of your server, not a real loopback. This will make the source address of the connection look like an external address and so they blocked it by default as they never considered the address of the server itself would be used.
I must have already set this up years ago because I had no issues. I wouldn’t have come up with it on my own at that time, so it must’ve been recommended in a guide/instructions somewhere even then.
@feld said:
This is apparently a problem for any FreeBSD user running Plex in a jail. Jails don’t have loopback addresses. There is a simple fix: go to Settings, Server, Network, hit Advanced. In “List of IP addresses and networks that are allowed without auth” box put the IP address of the server/jail.
I hope future versions of Plex automatically handle this.
@feld said:
This is apparently a problem for any FreeBSD user running Plex in a jail. Jails don’t have loopback addresses. There is a simple fix: go to Settings, Server, Network, hit Advanced. In “List of IP addresses and networks that are allowed without auth” box put the IP address of the server/jail.
I hope future versions of Plex automatically handle this.
Thx tons for this! Works fine now! This was driving me ■■■■ & balls!
@feld said:
This is apparently a problem for any FreeBSD user running Plex in a jail. Jails don’t have loopback addresses. There is a simple fix: go to Settings, Server, Network, hit Advanced. In “List of IP addresses and networks that are allowed without auth” box put the IP address of the server/jail.
I hope future versions of Plex automatically handle this.
This does it indeed also after upgrading to version 1.2.7.2987, before it worked without any issue