Localhost refused to connect

Plex Media Server Desktops & Laptops
1

Hello,

I have an Atomic Pi and I installed the x86 version of Raspberry Pi OS. I installed PMS and everything seemed fine. However, whenever I try to start PMS, I get the following error on the web screen: “localhost refused to connect.”

When I try to check status, I get the following:

plexmediaserver.service - Plex Media Server
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor
Active: failed (Result: exit-code) since Fri 2020-05-29 13:34:39 PDT; 4min 38
Process: 4330 ExecStartPre=/bin/sh -c /usr/bin/test -d "{PLEX_MEDIA_SERVER_AP Process: 4332 ExecStart=/bin/sh -c export PLEX_MEDIA_SERVER_INFO_VENDOR="(gr
Main PID: 4332 (code=exited, status=127)

May 29 13:34:39 raspberry systemd[1]: plexmediaserver.service: Service RestartSe
May 29 13:34:39 raspberry systemd[1]: plexmediaserver.service: Scheduled restart
May 29 13:34:39 raspberry systemd[1]: Stopped Plex Media Server.
May 29 13:34:39 raspberry systemd[1]: plexmediaserver.service: Start request rep
May 29 13:34:39 raspberry systemd[1]: plexmediaserver.service: Failed with resul
May 29 13:34:39 raspberry systemd[1]: Failed to start Plex Media Server.

I am unsure what’s wrong. I installed PMS on RPI 4 B and had no issues so I’m not sure what I did wrong. FYI - the PMS will be accessing hard drives connected to my router. I was able to map and mount those drives, but I’m just stuck being unable to actually reach the server. Any help is greatly appreciated!!!

Thank you.

2

craft a quick shell script which:

  1. Sets up the environment variables just as the service file does
  2. Launches /usr/lib/plexmediaserver/Plex Media Server
  3. Whatever is wrong and causing the error will be printed in that terminal window
3

Hi ChuckPa

Thank you for the response. I should let you know my proficiency with Linux is pretty limited, and consists of following guides and making sure I type everything correctly. I should provide an update however. I became frustrated and uninstalled PMS (the original installation was done via terminal). I figured maybe I should try to download the package from Plex web site, and I picked the 32-bit version by accident. Voila, everything worked. Then I read only the 64-bit version supports hardware transcoding so I uninstalled the 32-bit and then installed the 64-bit version, the exact same problem came back. Am I mistaken in believing that Atomic Pi supports 64-bit PMS? Maybe that was my error all along?

Just out of curiosity, would you recommend that I try Debian? If yes, which version (I unfortunately prefer graphical interface if possible - which I feel slightly pathetic about as I grew up using MS-DOS…) do you think would work best?

Thank you.

4

First, whatever processor you’re using, whether it be 32 bit or 64 bit, you should always install a bit-width matching OS on it. This allows you to use the full capabilities of the CPU. (install a 64 bit OS on a 64 bit CPU)

Install the same (matching) Plex package for that CPU/OS pair.

If you have the 64 bit package installed, you’ll have access to HW on those CPUs which support it (key discerning point here)

Regarding which OS to install, Ubuntu is Debian based. It’s been tailored / augmented to help those who aren’t as Linux savvy as the typical Debian user.

From all I’ve helped here, I’ve found most who are new to Linux have the best success with Ubuntu.

Derivatives of Ubuntu (Mint, etc) have more troubles than can be counted.

Given your Linux skills aren’t the best yet and apriori knowledge and competency of Linux is implied by using it, based on all I’ve helped:

  1. Create a VM somewhere on Windows or Mac
  2. In that VM, practice the How-To’s I have in Linux Tips
  3. Try to understand what’s happening rather than just memorizing .
  4. When you can setup a ‘test’ server
    a. through the VM
    b. accessing media files (only need 1 or 2) which are in the VM
    c. accessing your main media files wherever stored
  5. Then you’re ready to load onto the native host.

Linux has built-in documentation, with how-to-use, for every command. You can access it by typing man <command-name> in a terminal window.

5

Thanks for being so helpful and informative. Given my different experiences trying to install the operating systems, I decided to a fresh re-install of Raspberry Pi OS and then install the 64-bit version of PMS to see what happens. Lo and behold everything worked and the hardware transcoding tab is now present. I don’t know why different installs result in different results, but it works now so I can’t complain. Thanks for everything!

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.