Repository navigation
Plex App API config assumes exposure of TCP 32400 #740
jehanalvani
started this conversation in
App issues
Replies: 4 comments 8 replies
|
Can work around this by simply explicitly providing 443 port in the URL. e.g. |
1 reply
|
My solution was in my original Issue note:
HTH |
2 replies
|
After replacing my Plex.php with the link from Dallas-J, still not working for me. API communication successful but no info on the dashboard. I have other Heimdall icons with working API's. I am running Plex v4.87.2, Heimdall 2.5.4, http://ip:32400, no proxy. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
When configuring the enhanced Plex app, Heimdall assumes that TCP 32400 is exposed to communicate with a Plex server. In many cases, folks will deploy a server, and expose it on 80/443 via a reverse proxy, so 32400 is never exposed to the internet. As the API is REST, there's no reason that we should assume 32400.
Example is visible below in my own config. I had to expose 32400 without proxying via my reverse-proxy, then configure a custom URL specifying
httpand:32400to successfully connect to the PMS API.All reactions