我是一个中国大陆用户,现在遇到这么一个问题。
在下班的路上,使用流量通过IPV6访问家中的NAS上部署的plex,当使用ios的plex的时候,可以很快的打开,并且音乐媒体库可以立刻刷新出来,非常好的体验;
但此时使用plexamp打开,媒体库则展示出来得非常缓慢,经常刷新好多次才能加载出来,不知道是不是plexamp打开的时候卡在认证还是什么原因,
请优化一下吧,plexamp的界面远远好看于plex的音乐界面。如果有可能,建议优化一下我们中国大陆用户的网络连接,再次感谢。
I’m a user in mainland China and I’m experiencing this problem.
On the way out of work, I use traffic to access the plex deployed on my NAS at home via IPV6, and when I use the ios plex, it can be opened very quickly, and the music media library can be refreshed immediately, a very good experience;
However, when using plexamp to open, the media library is displayed very slowly, often refreshing many times to load out, I don’t know if it is stuck in the authentication when plexamp opens or what is the reason.
Please optimize it, plexamp’s interface is far better than plex’s music interface. If possible, please optimize the internet connection for our mainland China users, thanks again.
Hi, and welcome! ![]()
Please post Plexamp logs, and we can see why it is taking too long to load.
Plexamp-Logs-2025-02-24-2.zip (366.0 KB)
Thanks for replying to my feedback, I have uploaded two images, when accessing the home NAS Plex server on a 5G network via IPV6 bound Synology’s own domain name, and switching to another tab and then cutting back, this page gets stuck and the loading icon doesn’t move, in the logging software, please check.
The IOS plexamp interface is great, but once inside it loads the data significantly less quickly than the IOS plex loads (or to put it another way connecting to the server doesn’t load as fast as the plex does), so hopefully this experience can be optimized.
There’s a networking issue with your server, and Plexamp can only reach it via the relay, which is very slow.
These are the URLs it’s trying:
Feb 24, 2025 23:38:57.614 [Javascript] WARNING - DEVICE: Server connection https://192-168-31-83.f829041662e746c0a99dc4d7bf000ac1.plex.direct:32400 didn't work for zdl: HTTP status -28
Feb 24, 2025 23:38:57.617 [Javascript] WARNING - DEVICE: Server connection https://192-168-191-199.f829041662e746c0a99dc4d7bf000ac1.plex.direct:32400 didn't work for zdl: HTTP status -28
Feb 24, 2025 23:38:57.617 [Javascript] WARNING - DEVICE: Server connection https://27-187-119-92.f829041662e746c0a99dc4d7bf000ac1.plex.direct:24468 didn't work for zdl: HTTP status -28
I suspect your server isn’t properly accessible remotely, and it may have something to do with IPv4/v6 as it only seems to be attempting IPv4 connections.
ok,Thanks a lot, I’ll try setting it up in synology nas.
After comparing plex and plexamp , when I log into plex using 5G, IPV6 and download a song album, it is full speed. When I log in to plexamp to download the same album, the speed is only a few tens of K/s. So, I can be sure that there is no problem with the plex server on my synology and the nas device, and I can be sure that there is a connection problem with plexamp, which is probably still going through a proxy, and has not been converted to an ipv6 connection method.
Here are two logs, one for opening plex and one for opening plexamp on ios 5G IPV6.
please check,ty
Plexamp-Logs-2025-03-07-1.zip (290.5 KB)
PlexDebugInfo-me-8.45-9684 (2025-03-07 16.22.21 +0800).zip (1.4 MB)
Thanks for posting the logs, it doesn’t appear Plexamp is requesting IPv6 connections to test with.
Is there any chance you can share your server with me (username elan) temporarily so I can debug the code and make sure it works with IPv6?
Just now I switched from downloading plexamp from the US appstore to downloading plexamp from mainland China, and it feels almost the same in terms of experience, I’m able to share my server with you, how do I do it? send my (username&password) message to you?
Yes, the ios side of plexamp logs in(5G IPV6 ), and when it first starts to download, it goes fast, but doesn’t last more than a couple dozen seconds before it maintains its speed at a couple dozen K/S. It’s so weird. If you ever need additional information, I’d be happy to provide it.
We worked privately, and with the kind help of @ChaoDL we were able to make sure IPv6 worked to his server; the fix should be in the next release of Plexamp.
That’s great, thank you very much for your hard work in finding the problem, I hope the plex gets better and better!
Hi boss, when is the next update?
When it’s ready, we’re getting close ![]()
Good job, I can’t wait to experience plexamp in a more perfect way! ![]()
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.


