Server Version#: v1.14.1.5488-cc260c476
Player Version#:
Getting this error from the logs:
Feb 03, 2019 12:35:35.594 [6244] DEBUG - HttpServer: Listening on port 32400 with queue of 2147483647 connections.
Feb 03, 2019 12:35:35.595 [6244] ERROR - HttpServer: Error binding acceptor: An attempt was made to access a socket in a way forbidden by its access permissions
Feb 03, 2019 12:35:35.595 [6244] ERROR - Error: Unable to set up server: listen: An attempt was made to access a socket in a way forbidden by its access permissions (class boost::exception_detail::clone_impl<struct boost::exception_detail::error_info_injector >)
Ran netstat -ano, nothing on port 32400.
Backstory:
-
Had this installed on Server 2016. Working fine.
-
C:\ had installation to default, SSD RAID1.
-
Saved appdata to D:\Plex. SSD 1TB.
-
E:\ is a drivepool with StableBit, saved content there, movies and TV.
-
Worked great for few months. No issues. Had Ombi, Sonarr, Radarr, Tautulli, Jackett all working beautifully. Set all those apps as a system service using NSSMx64. Tested working.
-
Time to set plex as a service. Tried to install Plex Media Service by cjmurph. Didn’t work right, couldn’t get PMS to be reachable.
-
Uninstalled PMSService completely. Ran PMS, no start.
-
Repair installed PMS, no start, error log showing this above error now.
-
Google the hell out of it.
-
Ran netstat -ano, nothing on 32400.
-
Uninstalled PMS completely. Reinstalled. Same error.
-
Chased down some DCOM errors, enabled local activation, resolved some event log errors. Retried to run PMS, same error.
-
Run as administrator. Same error.
-
Backup database. Delete database. No change.
-
Delete D:\ appdata. No change.
-
Verified registry entry pointed to correct locations, done. No change.
-
Disabled all Plex related services, all additional apps, (Radarr, Ombi etc…) No change.
-
Uninstalled everything. No change.
-
Bang head against wall. Ef it, I wanted Server 2019 anyways right?
-
Nuke boot drive. Install Server 2019.
-
Configure.
-
C:\ RAID1, done.
-
D:\ SSD 1TB, done. Old plex appdata still readable.
-
E:\ DrivePool, done. All files accessible and working correctly.
-
Install PMS. Login, configure, use same D:\ for app data, transcodes, and backup db, dont add libraries yet, verify reachable locally, verify reachable on network. Good.
-
Restore database. Relaunch PMS. Seems ok.
-
Add libraries, same locations as previous installations pointed to, Just hangs. Doesn’t add the folders and start loading media and fetching metadata, just hangs. Wait for quite some time. Shut it down.
-
Relaunch Plex, database corrupt. Go through process to repair database for some time. Efff it. I have a backup. Nuke database.
-
Relaunch Plex, media database corrupt. Sonnuva… I have backup. Nuke all D:\app data.
-
Reluanch Plex. Works fine hooray. No libraries, but configured correctly, everything reachable. I add movies folder. It finds all movies, starts downloading metadata, etc… Wait. Wait. Wait.
-
Go about the server, have to reboot. Plex still scanning media, meh, shut it down. Reboot server.
-
Launch PMS, SAME DAMN ERROR AS PREVIOUS WINDOWS INSTALLATION AND LISTED ABOVE.
-
Pound beer(s), walk away, woosah many times.
-
Create this post, welcome to now. FML.
Will keep banging away. Can post netstat output if youd like, and whatever server logs you’d need.
UPDATE:
- Decided I didn’t have enough. Uninstalled PMS. Reinstalled to new directory, now default without the Plex directory part. Launched. Started fine. Settings saved.
- Will raise eyebrow and begin the slow march to testing.
- Possible windows firewall somehow automagically turned itself on for private networks.
Appreciate the help in advance.
