• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Docker via SSL

ollibraun

New Pleskian
Hi,

I have a docker container with software that should be reachable via SSL.

It can be reached via http on port 8080 and via https on port 8081 (Container config).

However, I cannot reach it via the domain. A reverse proxy "443 to 8081" is created.

See: Using Docker

However, the configuration files then contain the following:

Code:
#extension docker begin
    location ~ ^/w.* {
        proxy_pass http://0.0.0.0:8091;
        proxy_set_header Host              $host;
        proxy_set_header X-Real-IP         $remote_addr;
        proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
    location ~ ^/.* {
        proxy_pass http://0.0.0.0:8091;
        proxy_set_header Host              $host;
        proxy_set_header X-Real-IP         $remote_addr;
        proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    #extension docker end

Is that a mistake on Plesk's part? I can't reach the web server in the Docker container.

I get the message that I am sending an http request to an SSLO port. I think the configuration should be like this:

proxy_pass https://0.0.0.0:8091;

But I am not sure...

Regards
Oliver
 
Back
Top