Your browser does not support the video tag.
  • Home
  • Blog
  • Talk

© 2025 YIKZERO

Record of Installing Plex Server on R4S

Develop· March 18, 2023
This article was translated from Chinese byGemini 2.5 Pro. If there are any discrepancies, please refer to the Chinese version.

Environment Configuration

  • Model: FriendlyElec NanoPi R4S
  • Firmware Version: OpenWrt R22.3.13 (2022-06-22)
  • Architecture: ARMv8 Processor x 6
  • Environment: Google Direct

Preparations

  1. Prepare a network that can access Google.
  2. Install an OpenWrt system with Docker.
  3. Expand the memory card for Docker.

Troubleshooting Records

Architecture Issue

Most of the tutorials on setting up Plex with Docker are based on the X86 architecture. If you set it up according to the docker image of plexinc/pms-docker, you will encounter an error in the docker container logs: stderr: exec /init: exec format error

This is because the Docker container you installed has a different architecture from your system.

Therefore, find and install the ARM architecture PLEX from linuxserver/plex:

docker run \
-d \
--name plex \
-p 32400:32400/tcp \
-p 3005:3005/tcp \
-p 8324:8324/tcp \
-p 32469:32469/tcp \
-p 1901:1900/udp \
-p 32410:32410/udp \
-p 32412:32412/udp \
-p 32413:32413/udp \
-p 32414:32414/udp \
-e TZ=Asia/Shanghai \
-e PLEX_CLAIM=claim-xfczZtmEH5QPvZQc1HsF \
-e ADVERTISE_IP="http://192.168.31.1:32400/" \
-h Zero-R4s \
-v /myplex/plex/database:/config \
-v /myplex/transcode/temp:/transcode \
-v /mnt/sda/Media:/data \
--restart unless-stopped \
lscr.io/linuxserver/plex:latest

A detailed operation tutorial can also be found at linuxserver/plex. Adjust it according to your own situation.

PLEX No Initialization Page

This means that when you first enter the Plex application interface, you may encounter a "server not found" issue due to remote access not being enabled. You can use the following two methods to solve this problem:

1. SSH Port Forwarding

You need to open the PowerShell tool on your local computer and run the above command to forward the Plex port (default 32400) of the remote server to the port of the local computer (for example, 8888). After the port is successfully forwarded, you can access localhost:8888/web in the browser of your local computer to open the Plex application interface.

2. Direct Connection

If the remote server has allowed remote access, you can try to directly access the IP address and Plex port of the remote server (for example, http://13.124.4.66:32400/web) in your browser to open the Plex application interface.

Solution

On macOS, you can use the iTerm application to set up SSH port forwarding. The specific steps are as follows:

1. Connect to the Remote Server

Enter the following command to connect to the remote server, where username is the username on the remote server, and remote_server_ip is the IP address of the remote server:

ssh -L 8888:localhost:32400 username@remote_server_ip

This will forward the 32400 port of Plex on the remote server to the 8888 port on the local computer.

2. Enter and Verify the Password on the Remote Server

Now, you can open the browser on your local computer and enter http://localhost:8888/web to access the Plex interface on the remote server.

Error Again

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:OC9qmnB9nQtFN/OiPH7jGEoKb/zbX4NghGv/glu5dwQ.
Please contact your system administrator.
Add correct host key in /Users/yikzero/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /Users/yikzero/.ssh/known_hosts:1
Host key for 192.168.31.1 has changed and you have requested strict checking.
Host key verification failed.

This error message indicates that the key of the remote server you previously connected to has changed, which may be because the server has been updated or the administrator has changed the server's key. To protect information security, the SSH client will check and verify the key of the remote server. If the key changes, this error message will appear.

Update the remote server key data on your local computer to solve the problem. The operation steps are as follows:

  1. Delete the old key: Execute ssh-keygen -R <remote_server_ip> to delete the old key data on the local computer.

  2. Connect to the remote server: Use ssh username@remote_server_ip to connect.

    • The system will prompt "Are you sure you want to continue connecting (yes/no)?". Enter yes and press Enter.
    • Enter the remote server password to verify.
    • After connecting, re-run the command to set up SSH port forwarding.

After completion, you can access the PLEX server.

HomeLab Configuration
Hugo Tinkering Record: From 0 to 1