Laptop ip
191.117.0.208
Synology
191.117.0.213
No domain name
Thatâs your problem.
You are not RFC-1918 compliant.
Do you realize youâre using a public WAN address block and all traffic destined for you is being sent to there?
[chuck@lizum ~.2000]$ whois 191.117.0.208
% Joint Whois - whois.lacnic.net
% This server accepts single ASN, IPv4 or IPv6 queries
% LACNIC resource: whois.lacnic.net
% Copyright LACNIC lacnic.net
% The data below is provided for information purposes
% and to assist persons in obtaining information about or
% related to AS and IP numbers registrations
% By submitting a whois query, you agree to use this data
% only for lawful purposes.
% 2022-02-25 17:40:18 (-03 -03:00)
inetnum: 191.116.0.0/14
status: allocated
aut-num: N/A
owner: CLARO CHILE S.A.
ownerid: CL-CCSA39-LACNIC
responsible: Claro Chile Movil S.A.
address: Avda El Salto, 5450, Huechuraba
address: - - Santiago - RM
country: CL
phone: +56 258125104 [0000]
owner-c: CCM66
tech-c: CCM66
abuse-c: CCM66
created: 20131010
changed: 20210528
nic-hdl: CCM66
person: Claro Chile Movil
e-mail: netadmin.mobile@ip.telmexchile.cl
address: Avda El Salto, huechuraba, 5450,
address: - Santiago - Santiago
country: CL
phone: +56 2258125104
created: 20210528
changed: 20220119
% whois.lacnic.net accepts only direct match queries.
% Types of queries are: POCs, ownerid, CIDR blocks, IP
% and AS numbers.
[chuck@lizum ~.2001]$
192.168.x.x
10.x.x.x
-or-
172.16.x.x â 172.31.x.x
(Per the IETF spec RFC-1918 for Private Networks)
1 Like
I was not aware of that. So changing the ip back to one of these 192.168.x.x 10.x.x.x 172.16.x.x-172.31.x.x
Should solve the issues?
Yes it will .
PMS distinguishes between LAN addresses and WAN addresses.
When it knows itâs being accessed from a LAN IP, you can do a lot more (which is what you need when youâre the admin and trying to configure it).
When it sees a WAN address, itâs very strict about whatâs allowed.
1 Like
That is very interesting. I had no idea. I just thought I was being different
The reason modem/routers work as they do is because of those rules.
The address in the RFC-1918 specification are defined as Local-only and arenât routed (propagated) by the internet routers. They stop right at your modem/router and are translated to NAT (network address translation) transactions. This is how multiple devices share the WAN address given to you by your ISP.
The message goes out (the router translating and keeping track of it).
When the reply comes back, it translates it back to your LAN address and forwards.
Public IP addresses from your home LAN are simply sent out on an as-is basis.
No reply is ever seen because when Plex.tv replies to that address, the internet does its job and sends it back to the that IP (whoever the rightful owner is).
1 Like
Well Iâm happy to say that it fixed the issue! I can now log in to the server side!
Thank you so much!
2 Likes
Youâre very welcome!
2 Likes
newest update does not fix the re-loading of Plex on update. I have to still reboot entire NAS. Synology 1019+
Package Center should honor the run state.
If Plex is running when you start the update,
â Stops Plex
â Installs update
â Starts Plex
If Plex is not running when you start the update,
â Install update
Is this how itâs working for you?
There are times (which happens to me every once in a while)
- Save the DSM configuration
- Reset DSM
- Reload DSM (which does not erase any media files)
- Reinstall DSM
- Reinstall packages
From there, I pick up where I left off.
Seems excessive just to fix plex not auto loading after update.
My update process was as follows:
Plex running
Install update
Attempt to re-run after update
Fails every time, says manually stopped.
Reboot unit to fix issue.
Next update Iâll try your process but Iâm not interested in resetting the whole DSM.
1 Like
Very cumbersome
DSM 7 changed EVERYTHING.
On DSM 7, the package internally only has access to username âPlexMediaServerâ
They removed ALL ârootâ (administrator) privileges.
As such, please observe
- Signed in as root:
- Switch to the PlexMediaServer user (which is what I see internal in the package scripting)
- Check the status of the package
- Start the package
- Check the status again.
You can see how Package Center rejects any request by the package username to start the package (itâs NOT an administrator).
bash-4.4# su -s /bin/bash PlexMediaServer
bash-4.4$ whoami
PlexMediaServer
bash-4.4$ synopkg status PlexMediaServer
PlexMediaServer package is stopped
Status: [263]
bash-4.4$ synopkg start PlexMediaServer
{"action":"prepare","error":{"code":0},"stage":"prepare","success":true}
bash-4.4$ synopkg status PlexMediaServer
PlexMediaServer package is stopped
Status: [263]
bash-4.4$
This is 100% a Synology problem.
- Package Center knows the run/stop status prior to installation
- Package Center stops if needed
- Package Center does the installation.
- Package Center should resume RUN status after installation.
I think itâs an internal corruption. To have âerrorâ and âsuccessâ in the same return code is not logical.
This is why I reinstall DSM and itâs magically fixed. 
I invite you all to test (repeat) what Iâve done above
1 Like
Very much regret installing DSM7, downgrading doesnât really work well.
Are yâall gonna fix this without us having to monkey around or you canât really fix bc of what they did
1 Like
I am trying to figure out a workaround to DSM but thatâs like an ant moving a mountain.
I am doing what I can. I will report if I make progress.
1 Like
TO ALL FOLLOWING HERE:
I may have found a solution.
I am making some package coding changes now and will have a test package
asap.
EDIT: Nope. Not it. Still searching.
1 Like
Investigating here.
How are the updates being installed ?
Automated script or via Package Center ?
1 Like
iâve always stopped plex before updating and never had the issue described above.
plex server updates. When I know theyâre available I just do a manual update. DSM stops, updates and then restarts plex. Has worked every time so far
Have a DS416
Updated to the latest plex version.
but the quickconnect to 32400 doesnt load
also10.0.1.7:32400/web also does not work.
get this error on firefox: Unable to connect
any thoughts. been trying to fix it for a couple hours now, working on the port forwarding, firewall (which is off) turning off quickconnect, and whatever else I have read on this thread.
