Pandora FMS community forums
Docker Reverse Proxy Mixed Content - Printable Version

+- Pandora FMS community forums (http://pandorafms.org/forum)
+-- Forum: Pandora FMS (http://pandorafms.org/forum/forum-3.html)
+--- Forum: Community support (English) (http://pandorafms.org/forum/forum-7.html)
+--- Thread: Docker Reverse Proxy Mixed Content (/thread-13903.html)



Docker Reverse Proxy Mixed Content - austin1123 - 08-29-2019

I am attempting to setup the docker container of Pandora FMS.

Below is my docker-compose.yml
Code:
version: "3.6"
services:
 pandora:
   image: pandorafms/pandorafms:7
   container_name: pandora
   restart: unless-stopped
   volumes:
     - /etc/localtime:/etc/localtime:ro
   labels:
   # Service Name of the container
     - "traefik.backend=pandora"
   # Enable this proxy route
     - "traefik.enable=true"
   # Network that is shared with the Proxy
     - "traefik.docker.network=proxy_backend"
   # Fronend Rule
     - "traefik.frontend.rule=Host:pandora.domain.com"
   # Port & Protocol the service is listening for
     - "traefik.port=80"
     - "traefik.default.protocol=http"
   networks:
     - proxy_backend


networks:
 proxy_backend:
   external: true

I am using Treafik as my reverse proxy and it works for everything else I have setup.

The issue I am experiencing is that, while I can load the page in my browser with HTTPS, the page attempts to load resources using a hard coded port 80.
The Pandora container is listening on 80, but should not hard code that port into the URLs on the site.

Chrome console
GET https://pandora.domain.com:80/pandora_console/include/styles/common.css net::ERR_SSL_PROTOCOL_ERROR

So, how can I prevent the site from adding the :80 to every link or resource?


RE: Docker Reverse Proxy Mixed Content - jamal - 09-05-2019

Good morning

This is caused by the http GET request method in which the data is readable in the URI. With the POST method the data does not travel in the URI and cannot be seen.

Regards


RE: Docker Reverse Proxy Mixed Content - jamal - 09-05-2019

Check the configuration files of the reverse proxy and compare it with that of the Docker because it seems that the configurations are conflicting.

Best regards