Unable to listen for events on SERVERNAME

General Discussions
1

I have recently been messing around with getting my whole web-facing setup on my nas a bit more secure (forced SSL and using reverse proxy to reduce exposed ports).

The issue is if I access plex over the reverse proxied URL EG: plex.hostname.synology.me I get a constant spam of the message “Unable to listen for events on SERVERNAME”. Everything else appears to work correctly despite this.

This only occurs when accessing over the internet, on the local network it connects properly.

However, there are some other parts that make it seem even stranger and seems to depend on browser.

If I have no port forwarded for plex specifically (the way i’d like it). Plex says it’s not accessible, despite being perfectly accessible via plex.hostname.synology.me, both Chrome and Samsung internet will display the listening error.

If I then forward a port for Plex (specified under remote access) Samsung Internet will connect properly, whilst Chrome will still display the errors. If I connect via the external ip + port rather than plex.hostname.synology.me, both browsers work correctly with no errors.

Any thoughts?

2

Additional testing has shown that the browser doesnt appear to matter, it will just randomly work or not while on the reverse proxied url, but will work 100% on hostname.synology.me:forwardedport

As both methods route to localhost:32400 I’m not sure why one works and the other doesn’t.

3

I have just done the same thing.
Desktop with PMS running NGINX reverse proxy. Works fine without the SSL redirect but when you introduce the SSL redirect everything works fine except I get this recurring message.

I have not however had much chance to investigate as yet.