Plexamp Remote Connect Not Working - iOS16 / Win10 Localhost

I am running Plexamp on my Win10 media server, and cannot remote connect to it from iPhone 14Pro. Anytime I try to remote connect (on my local network), the iOS app shows a red “Cannot connect to remote player” strip and connect window becomes unresponsive until the app is killed and restarted.

Weirdly enough, remote connecting from the server to Plexamp on my phone works just fine. Connecting from Plexamp on another PC to the server also works.

iOS 16.5
Plexamp 4.7.4
Plex Server 1.32.4.7195

Has anyone had this issue? Logs are attached
Plexamp-Logs-2023-06-24-1 2.zip (200.9 KB)

I see a failed player selection message:

DEVICE: Player connection http://192.168.1.88:32500 didn't work for PlexAmp
...
DEVICE: Player connection http://10.204.112.68:62786 didn't work for iPhone

Almost certainly a networking issue, probably double NAT.

Thanks Elan. I have run tracert on the server and the second private IP (pls see below screenshot) is ISP gateway, which (according to them) does not have a NAT. I have only one router.

image

Wouldn’t double NAT impact all the devices (not only iPhone)? Remote connect works for any Win PC running Plexamp - both on local network and externally (I’ve just tested using a 5g modem).

Any tips on how I can further investigate? Thanks again

With double NAT things might work only in one direction.

What are the IP addresses of your iPhone and Win 10 machine?

I have 2 Win 10 machines - a server (iNUC) and a home PC - 192.168.1.88 and 192.168.1.87 respectively.

iPhone had a dynamic IP before, but I just tried reserving iPhone’s address on my router to 192.168.1.86 and it did not help.

To be clear, I can remote connect both ‘to’ and ‘from’ Plexamp on my Win 10 server via another Win 10 home PC running Plexamp. For iPhone though it only works in one direction:

Win 10 PC => Win 10 server - OK
Win 10 server => Win 10 PC - OK
Win 10 server => iPhone - OK
iPhone => Win 10 server - Doesn’t work.

See if you can hit the Win10 server from your iPhone in the browser, e.g.

http://192.168.1.88:32500

I am having a similar issue.

Jun 26, 2023 16:32:51.015 [0x6c09f000] DEBUG - Networking: Completed request 236: (GET http://192.168.1.152:59287/resources) with code -28 (have 0 bytes) in 15007 ms.

Trying to control my Win10 Plexamp App with my Iphone.

Then I’d ask the same thing, try hitting it from a browser on the iPhone. Maybe some sort of Windows firewall/permissons issue?

1 Like

Allowed public access on Windows Firewall Rule for Plexamp after deleting rules and things are WORKING.

So, I have played with the firewall (which did not help), then reinstalled Plexamp on both Server and Win10 PC machines, played with the settings … and got it working for the iPhone => Win10 PC! No idea what I’ve done though…

Basically now the situation is:
Win 10 PC => Win 10 server - OK
Win 10 server => Win 10 PC - OK
Win 10 server => iPhone - OK
iPhone => Win 10 PC- OK
iPhone => Win 10 server - Doesn’t work

Hitting the ip:port from the iPhone for both the server (for 192.168.88:32500) produces ‘server stopped responding’ message. But so does the ip:port for the PC (for 192.168.87:32500), despite it working in Plexamp app now.

Firewall settings (open for all domains) on both server and PC are identical. Switching off the server’s firewall altogether doesn’t help either.

The only possible hint is that the phone seems to ‘see’ the server as a ‘phone’ rather than the PC (called ‘Studio’ here):

InkedIMG_3837

in the Plexamp app on your server, what ip:port is shown under Settings > Advanced > Remote Control … Allow player to be controlled at … ?

It is 192.168.1.88:32500

image

Played with it a bit more. Can’t put my finger on what the difference between my two Windows PCs is (my iNUC server and regular PC). My iPhone can connect to one, but not the other.

Through no fault of my own, everything suddenly works now.

I suspect my router firmware got updated, which resolved the issue. I got TP-link Deco x20 router - not old, but also not new, so not sure what was wrong before.

Thanks everyone who tried to help and thanks Elan for a great product!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.