I re-installed the server from scratch (deleting Preferences.xml and everything else), still get the connection problem.
I signed out and re-claimed my server as well.
Here’s the fresh logs: logs.tar.gz (75.2 KB)
Update:
So with my new install same problem happens, I managed to unclaim/reclaim the fresh install and same problem exists, logs are still showing a 403.
From this:
EventSource: Failure in ParseHeader: HTTP/1.1 403 Forbidden
Is there a way to know what was the Header parsing problem? I’m assuming this is a response from your Nginx, so there’s no way I can know unless I start checking all headers one by one from my end, which I don’t really want to do.
Any chances to get a better description of why this connection is getting a 403 even though I have the right access token setup in my server config?
Are you running a proxy in front of PMS? I am looking at your account and I do not see any duplicated servers.
I see the same thing with duplicate servers.
No reverse proxy or some such.
What I see when connected to my feral slot PMS instance
What I see at app.plex.tv
Mimas is another slot that feral setup for me to see if it would work properly with plex. They claim that they have many servers with no problems for plex users. I’m wondering if it’s older versions of plex that don’t have a problem.
Please allow me to be as considerate as I can with this.
I can’t support Feral hosting because of how they have configured their servers.
They have chosen to isolate processes and networks using Linux Namespaces.
PMS is not written for that environment. As such, we cannot support that environment.
If Feral provides traditional containerized / virtualized service where PMS sees no other processes other than those belonging to the virtual host instance then we can continue.
We did find a build problem with the current Plex Pass version.
We’ve identified where the system regressed and corrected it.
Please expect fresh builds in PlexPass shortly.
But Docker is precisely using namespaces to separate container processes and Plex doesn’t seem to have a problem with that. Under that assumption then every user with Docker should be having the same issue.
Not that I want to be pushy or anything, but I don’t think there’s enough of an argument with that to claim that’s THE reason of why it doesn’t work, although I understand you have more experience in Plex, this doesn’t make sense from a general tech approach.
Quick question, what did you mean with Plex Pass? Is it the builds that are available only to paid users or something else?
The reason plex doesn’t work on Feral:
-
ps -ef | grep -i plexwill show multiple Plex Media Server processes - PMS, when it starts, checks for the IPC’s (shared memory partitions).
- Anything found from either above is terminated. (assumed hung)
In Docker, you have ONE PMS server instance per container.
On a VM, or real host, you have ONE PMS server instance per machine.
On other providers, such as Hetzner, PMS does not see other instances because each is fully insulated from the others.
PMS isn’t intended to be multi-instance on a host. Docker provides the containerized insulation required. Feral uses only Namespaces. This is insufficient.
Regarding the other issues of PlexPass beta;
The root cause was discovered last night.
It was a regression in the build (compile) and has been resolved.
You’ll see a new PlexPass build. (might be up now as I write this – too busy, haven’t looked)
If a problem, use public release until it is.
Thanks a lot!
Thanks for the patience as well 
I’ll check the new build and come back.
Not sure what to expect here with regard to the bug found.
We are told PMS won’t work on feral but yet something in a plex pass build was found regressed with the implication being that a fix will fix our problem.
So, I’m confused.
Doubly so because my seedbox PMS is using the latest public release anyway, not plex pass. 
Feral and this regression are not related.
Plex hasn’t worked on Feral for as long as I’ve been here. When first discovered, it took a while. We then discovered that when another PMS starts on the same host as an existing PMS, the first PMS is terminated. We saw the commanded shutdown mid-playback sessions. This was the clue.
Later research revealed they use Linux Namespaces as their sole means of isolating customers. This is insufficient for PMS. It needs, at minimum, containerization (e.g. Docker).
The ‘broken build’ is a problem with RPATH. It’s been corrected. New packages are generating as I write this and about to push to PlexPass Beta
1 Like
So, a few things:
- Problem with double server registration, plex.tv and 403 still exists in version 1.16.6.1592. Should I reinstall Plex to be sure?
- In Feralhosting, Plex processes are no longer seen by other Plex instances. (Last time I checked was around the beginning of the year and I think the reason they changed it is exactly what you say). Users and their processes can only see their own processes.
- This problem is not about Feral, so I’d like to move away from that topic. This is clearly a malformed header / connection problem.
Thanks for updating. I have not had the opportunity / need to see any changes Feral might have made since last evaluation.
Given the previous Plex Pass build was faulty, have you either reverted to Public or tried the new PlexPass build (1592) ?
403 error code is forbidden. Given this doesn’t occur so often as to be a problem (that’s I’m keenly aware of), we can try a few ways to reset the server / plex.tv association if you wish. This will be a bit of ‘try and see’ if you’re interested.
I’m currently using the 1592 build and I’m having all the same issues that I pointed in the first post.
At this point I’m willing to try anything that may solve it, so go ahead
I am having the same issues as well. Duplicate server in the list and the inability to access the server via app.plex.tv with “403 Forbidden” errors in the logs. When I add ?secure=0 to the URL, the server becomes visible. The server is also visible on the iOS and AndroidTV app, the issue is only with the webapp.
The same issue is also being reported here by multiple users: Cannot access server from plex.tv
I’m using the 1.16.6.1592 (Plex Pass) build by the way.
so @ChuckPa, what should I try?
I have been seeing several 403 errors reported. Those I’ve seen have been associated with Feral. Is this seedbox running on Feral?
If so, I will try one more time to help with Feral and determine how to setup PMS for them.
At the moment one of my servers is with them and I have another one setup in a home-lab environment with a similar config.
Right now both have the same problem. The logs I sent are from Feral though.
