Thanks for the log files. Several things need to be addressed. Start down the list and let me know if you’ve any questions or need additional information.
1. Logging Level
Please disable Verbose logging for Plex Media Server. Debug level, the default, is sufficient. Verbose adds unneeded information to the log files. Go to Settings → Server_Name → General (Show Advanced). Uncheck the box next to Enable Plex Media Server verbose logging and save changes.
2. Confirm time & date settings on EX2 Ultra.
The log files are full of entries like the one below. Based on other threads in the forum, the recommendation is to verify that the time and date are correct on the server.
Jul 29, 2021 02:05:38.218 [0xb1727d48] WARN - Exception caught reading modified time "/mnt/HD/HD_a2/Nas_Prog/plex_conf/Plex Media Server/Cache/PhotoTranscoder/b2/b2328ce730f8360917cf2085dfea4b497fcb082b.ppm" (boost::filesystem::creation_time: Function not implemented: "/mnt/HD/HD_a2/Nas_Prog/plex_conf/Plex Media Server/Cache/PhotoTranscoder/b2/b2328ce730f8360917cf2085dfea4b497fcb082b.ppm")
3. Local network
Your local network appears unstable.
Please describe your home network and how the server, your PC, TV, etc are attached. Do you have multiple routers in your home network?
How is the EX2 Ultra connected to your network - directly to the internet access device via an Ethernet cable, to another device such as a WiFi mesh system, etc?
Reason for asking: Something is wrong with either your home network or the EX2. Plex Media Server receives notices that the Ethernet interface has reset. When this happens, it loses its IP address and does not regain it until restarted.
This could be caused by multiple reasons: defective Ethernet cables, misconfigured devices, devices beginning to fail, or other reasons.
From the Plex Media Server.log files:
Plex Media Server starts:
Jul 27, 2021 00:30:06.555 [0xb5e87e80] DEBUG - BPQ: [Idle] -> [Starting]
Picks up an IP address ~10 seconds later:
Jul 27, 2021 00:30:16.370 [0xb5e87e80] DEBUG - Detected primary interface: 192.168.68.129
Loses IP address after ~1 hr 20min:
Jul 27, 2021 01:49:28.073 [0xb1f37d48] DEBUG - NetworkInterface: Notified of network changed (force=0)
Jul 27, 2021 01:49:28.074 [0xb1f37d48] DEBUG - Detected primary interface: 0.0.0.0
The above two messages repeat ~25 times.
Plex Media Server stays in this condition until restarted over a day later:
Jul 28, 2021 04:19:29.235 [0xb5dd7e80] DEBUG - BPQ: [Idle] -> [Starting]
Jul 28, 2021 04:19:42.625 [0xb5dd7e80] DEBUG - Detected primary interface: 192.168.68.129
3. Remote Access
Whatever is happening in your local network is affecting remote access. That is also why I asked about your network configuration.
Plex is picking up a double NAT configuration, which happens when the Plex server is connected behind two routers.
This is keeping your remote access from working. Note in the log files below, the first line contains, public address is 192.168.0.33. If it were working correctly, it would list your real public IP address, the same as the WhatIsMyIP site.
From Plex Media Server.log:
Jul 29, 2021 02:19:48.253 [0xb1c47d48] DEBUG - NAT: UPnP, public address is 192.168.0.33
Jul 29, 2021 02:19:48.253 [0xb1c47d48] DEBUG - PublicAddressManager: got WAN IP 192.168.0.33 from router
Jul 29, 2021 02:19:48.253 [0xb1c47d48] WARN - PublicAddressManager: WAN IP is a private IP address
...
Jul 29, 2021 02:20:29.710 [0xb24dfd48] ERROR - MyPlex: mapping failed due to potential double NAT configuration
Jul 29, 2021 02:20:29.710 [0xb24dfd48] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published (Double NAT)'.