Connecting to *.plex.direct problem

Server Version#: Docker 1.42.2.10156
Player Version#: Android 10.26.0.2578

Loading metadata and other data is extremely slow.
Video playback takes a long time to establish the connection, but once connected, playback seems to work fine.

When accessing my IP address via a web browser, the server does not appear slow.
Additionally, connection attempts within a LAN environment are fast.

I confirmed in the app logs that a timeout occurs when connecting to 123-123-123-123.3c51430e8cf41c8ad15bd48a.plex.direct.

I apologize for the awkward English, as it is machine translation.

<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

12-10 12:14:37.817 i: Fetching [method:GET] https://sonos.plex.tv/resources?X-Plex-Token=...fWRz&X-Plex-Client-Identifier=4a62047516-com-plexapp-android&X-Plex-Language=ko-kr
12-10 12:14:37.852 e: [AppsFlyerInitializer] Error getting conversion data: Launch status code: 403
12-10 12:14:37.918 e: [PlexServerWebSocket] (ID: 208430 | Server: omv) Connection failed.
12-10 12:14:37.918 e: An exception occurred: java.net.SocketTimeoutException: failed to connect to 123-123-123-123.3c51430e8cf41c8ad15bd48a.plex.direct/123.123.123.123 (port 32400) from /172.30.1.65 (port 45556) after 5000ms
12-10 12:14:37.919 e: Stacktrace: java.net.SocketTimeoutException: failed to connect to 123-123-123-123.3c51430e8cf41c8ad15bd48a.plex.direct/123.123.123.123 (port 32400) from /172.30.1.65 (port 45556) after 5000ms

android mobile app 2025.30.0

same problem.

12-10 12:49:15.886 d: 12/10/2025 12:49:05:873 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://192-168-1-2.57a2d8c53c0e8cf41c8ad15bd48a.plex.direct:32400/media/providers 10007ms
12-10 12:49:15.886 d: 12/10/2025 12:49:05:885 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://10-0-3-1.57a2d8c53c51430e8cfad15bd48a.plex.direct:32400/media/providers 10017ms
12-10 12:49:15.887 d: 12/10/2025 12:49:05:890 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://172-20-0-1.57a2d8c53ce8cf41c8ad15bd48a.plex.direct:32400/media/providers 10020ms
12-10 12:49:15.887 d: 12/10/2025 12:49:05:895 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://172-17-0-1.57a2d8c430e8cf41c8ad15bd48a.plex.direct:32400/media/providers 10024ms
12-10 12:49:15.887 d: 12/10/2025 12:49:05:899 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://172-19-0-1.57a2d8c53c51430e8cf4d15bd48a.plex.direct:32400/media/providers 10026ms
12-10 12:49:15.887 d: 12/10/2025 12:49:05:904 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://172-18-0-1.57a2d8c53c51430ead15bd48a.plex.direct:32400/media/providers 10029ms
12-10 12:49:15.887 d: 12/10/2025 12:49:05:907 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://172-21-0-1.57a2d8c53c51430e8cf15bd48a.plex.direct:32400/media/providers 10031ms
12-10 12:49:15.887 d: 12/10/2025 12:49:05:909 [myid4a62040ed6247516-com-plexapp-android] [Connections] Fetch timeout GET https://123.123.123.123.57a2d8c53c514c8ad15bd48a.plex.direct:32400/media/providers 10031ms
12-10 12:49:15.887 d: 12/10/2025 12:49:05:912 [myid4a62040ed6247516-com-plexapp-android] [Connections] Testing connection for omv at https://139-162-87-197.57a2d8c53c51430e8cf41c8ad18a.plex.direct:8443
12-10 12:49:15.887 d: 12/10/2025 12:49:11:533 [myid4a62040ed6247516-com-plexapp-android] [Connections] GET 200 https://139-162-87-197.57a2d8c53c51430e8cf41c8ad15a.plex.direct:8443/media/providers 5620ms
12-10 12:49:15.887 d: 12/10/2025 12:49:11:534 [myid4a62040ed6247516-com-plexapp-android] [Connections] Current best connection to omv is https://139-162-87-197.57a2d8c53c51430e8cf41c8ad48a.plex.direct:8443 is relay

123.123.123.123 was originally my public IP address, but I have altered it.
Whens accessing https://123.123.123.123.57a2d8c53c514c8ad15bd48a.plex.direct:32400 via web browser. fast

The issue has been resolved.
Since I didn’t do anything, I have no idea why it was resolved.