Cant claim server trying to install on container manager for synology NAS

Plex Media Server
1

Server Version#:
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I’m trying to install plex in a container on my synology NAS :

I’m using a macvlan to have a different IP on myy NAS for Plex & a compose.yaml file to create the server.

services:
plex:
image: lscr.io/linuxserver/plex:latest
container_name: plex
hostname: plex_server
mem_limit: 4g
cpu_shares: 1024
security_opt:
- no-new-privileges:true
#healthcheck:
# test: wget --no-verbose --tries=1 --spider http://20.142.10.71:32400/web
networks:
somenet:
ipv4_address: 20.142.10.71
environment:
- PUID=1026
- PGID=100
- TZ=Europe/Paris
- VERSION=docker
- PLEX_CLAIM=claim-x63LyZHxxGdXFQZcRYpa
volumes:
- /volume1/docker/plex/config:/config
- /volume1/plex_media:/media:rw
- /volume1/plex_media/shows:/media/shows:rw
- /volume1/plex_media/movies:/media/movies:rw
- /volume1/plex_media/music:/media/music:rw
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
- /dev/dri/card0:/dev/dri/card0
ports:
- 32400:32400/tcp
- 3005:3005/tcp
- 8324:8324/tcp
- 32469:32469/tcp
- 1900:1900/udp
- 32410:32410/udp
- 32412:32412/udp
- 32413:32413/udp
- 32414:32414/udp
restart: unless-stopped

The server seems to be created fine on my account :

server
server1009×397 57.9 KB

When I go to the IP, I’m faced with

server
server950×610 50 KB

I tried to :

  • edit preference.xml.
  • add PlexOnlineHome to 1 in the xml and the value is forced at 0 anyway.

Any clue on how to proceed ? I’m stuck there.

2

Your IP address 20.142.10.71 is not RFC 1918 compliant. Which means plex sees it as a public access. You cannot claim a server via its public IP as that is a security risk. You can try GitHub - ChuckPa/UserCredentialReset: User Credential Reset utility for Plex from within the docker container or you can use a RFC private IP address for LAN access. Private network - Wikipedia

3

Thx for the answer.
I have been going through networking as an hobby since half a year with opnsense, vlan, routing stuff , docker & VMs.
I haven’t touched about VPN & public IP yet too much.
I will try to make all my current network RFC 1918 compliant tomorrrow & will try again with plex.

4

@atavus1

To share the importance of RFC-1918 for our servers.

The numbers you have conflict with Amazon’s servers.

RFC-1918 addresses are a subset of the total address block where all equipment knows to separate into LAN & WAN sides. This is the foundation for our LAN addresses. RFC-1918 addresses are not routable through the internet.

I can tell you my server is at 192.168.0.20 and it’s perfectly safe because the general internet will forward that address outside your own modem/router.

[chuck@lizum ~.2001]$ whois 20.142.10.71

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2024, American Registry for Internet Numbers, Ltd.
#


NetRange:       20.142.0.0 - 20.142.255.255
CIDR:           20.142.0.0/16
NetName:        AMAZO-4
NetHandle:      NET-20-142-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Amazon.com, Inc. (AMAZO-4)
RegDate:        2022-07-11
Updated:        2022-07-11
Ref:            https://rdap.arin.net/registry/ip/20.142.0.0



OrgName:        Amazon.com, Inc.
OrgId:          AMAZO-4
Address:        Amazon Web Services, Inc.
Address:        P.O. Box 81226
City:           Seattle
StateProv:      WA
PostalCode:     98108-1226
Country:        US
RegDate:        2005-09-29
Updated:        2022-09-30
Comment:        For details of this service please see
Comment:        http://ec2.amazonaws.com
Ref:            https://rdap.arin.net/registry/entity/AMAZO-4
5

redone all my IP in RFC 1918 compliant and It worked.
Thank you very much and have great holydays !