#Plex media server connection refused how to#

Thanks in advance for help with diagnosis and resolving. A better solution would be to do the above to your media folders and then symlink those media folders from a Shared directory where plex can scan, without breaking permissions for the whole home for everyone. That is, if file corruption is indeed the issue. installed docker image on a centos 7 host (VirtualBox vm), with 5 other active containers (all from linuxserver, all working well and accessible from other computers on the lan), container starts, logs looks good, but web UI says connection refused and no preferences.xml file generated and no real application logs run. It is now exhibiting the same behavior, so I'm wondering if it came on after one off/on of the breaker, and then shut down abnormally on the next off/on, corrupting the SD card in a manner similar to the corruption on the main RPi. Then, not so cleverly, I had the backup RPi plugged in (but powered down) on the same strip as the functioning RPi. where do I look in the logs to figure out what is going on?Īs a final note, I cleverly set up a (almost) clone of my functioning LMS on another SD card installed in another RPi. If I click max2play's button 'Open Squeezebox Server Webadministration' I get the same 'refused to connect' message as when I go manually to LMSip:9000 (no surprise there). On the other hand, the max2play web interface indicates that LMS is running, and if I login via Putty I see that the squeezeboxserver process is running, with the same pid that max2play reports. Try checking the connection checking the proxy and firewall.

If I point my browser to :9000 I get the message: Since then LMS appears to start, but none of my SBs can see it and iPeng can't see it. Two days ago it had an abrupt shutdown when an electrician in the house started flipping circuit breakers randomly until he found the one he wanted. I've been running LMS 8.0.0 - one of the nightlies from 1-2 months ago - just fine on a Raspberry Pi under Max2play. What I have been doing to get it back up and running is a couple of reboots, sometimes it works at first try others I have to give it a few reboots to get it back.I feel dumb about this because several years ago when I hung out a lot in these forums I could help other people resolve such matters.

#Plex media server connection refused how to#

How to force a quit and make it restart properly? So it’s still running, despite the stop command it seems. the only fix (when this happens) is to log into the WD admin. client is roku at 192.168.60.100 but plex running on 192.168.0.1:32400 refuses to connect (sometimes), even when using the media>configure admin interface of the wireless pro. T16:55:54+01:00 systemd: : Main process exited, code=exited, status=1/FAILURE While online, I authorized the entire subnet of 192.168.60.0/24 for that particular plex server. T16:55:54+01:00 exmediaserver: Plex Media Server is already running. So I tried “sudo snap stop plexmediaserver” witch seems to work and gives no error or entry in log.īut when i try to do a “sudo snap start plexmediaserver” witch seems to work, but in the log it gives a few errors: T16:55:54+01:00 exmediaserver: ERROR: ld.so: object '/usr/local/lib/libprocesshider.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. I’ve tried restarting plex with “sudo snap restart plexmediaserver” and it seems to work and gives no errors, but the server is still unavailable. Verify you have a network connection and that the server is online, or see our tips for further assistance.” But when trying to access Plex via browser I get a error: “PLEXSERVER is currently unavailable So I have this recurring problem that comes once in a while but not every time…Īfter a power failure or a reboot of my server, the Plex snap starts and seems to be working.