Skip to content
This repository was archived by the owner on Apr 12, 2025. It is now read-only.

Aborting connection test for <plex-server-name> at http://<hostname>:32400/media/providers due to mixed content prevention #171

Open
sgtsquiggs opened this issue Jan 1, 2025 · 1 comment

Comments

@sgtsquiggs
Copy link

sgtsquiggs commented Jan 1, 2025

Any idea what would be causing this error?

[Connections] Aborting connection test for <plex-server-name> at http://<hostname>:32400/media/providers due to mixed content prevention

If I visit http://<hostname>:32400 directly it is working.

I am visiting app.plex.tv, so simulate external clients connecting to my server.

My HTTP setup:

Docker:

587e03262214   ghcr.io/hotio/plex       "/init"                  2 hours ago     Up 2 hours      0.0.0.0:32400->32400/tcp                        plex
20f394195ec9   ghcr.io/lostb1t/replex   "/app/replex"            2 weeks ago     Up 12 hours     0.0.0.0:3001->80/tcp                            replex

Router -> port forwarding 32400 to dockerhost:3001


I also have the following HTTPS access set up, but I have similar issues when I configure my plex server to advertise my HTTPS address:

Docker:

587e03262214   ghcr.io/hotio/plex       "/init"                  2 hours ago     Up 2 hours      0.0.0.0:32400->32400/tcp                        plex
20f394195ec9   ghcr.io/lostb1t/replex   "/app/replex"            2 weeks ago     Up 12 hours     0.0.0.0:3001->80/tcp                            replex
24327450496b   caddy                    "caddy run --config …"   18 months ago   Up 18 minutes   0.0.0.0:10080->80/tcp, 0.0.0.0:10443->443/tcp   caddy

Caddyfile:

hostname {
        reverse_proxy /library/parts http://plex:32400
        reverse_proxy /video/:/transcode/universal/session http://plex:32400
        reverse_proxy http://replex:80
}

Router -> port forwarding 443 to dockerhost:10443

caddy-security, replex, and plex are all on the same docker network.

Visiting https://<hostname> works fine 🤷‍♂️

@sgtsquiggs
Copy link
Author

sgtsquiggs commented Jan 1, 2025

Removing the insecure URL from Plex->Settings->Custom server access URLs and defining the https address as https://<hostname>:443/ seems to have resolved access via app.plex.tv... I needed the :443 for some reason.

I have the :32400 port routed directly to plex instead of through replex - now Plex->Settings->Remote Access is staying solidly ✅ .

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant