• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Plesk + Ubuntu 16.04 + Docker + GitLab

UweP

Regular Pleskian
Hi! I installed the Docker container for GitLab-ce on my server with plesk onyx. Now I wonder, how can I have gitlab reachable over https at https://gitlab.mydomain.tld? Also I want a Let's Encrypt Certificate. Is that possible?

I'm new to Docker etc..

If I set static ports (not changing ports) and select on subdomain gitlab.nextgamers.eu the docker proxy rules for gitlab-ce port 443, it says nginx bad gateway. The http forward works though.

What I exactly wanna do now is:
1. Get :443 to forward to the https port of the installation without error.
2. Get Let's Encrypt working.

Ok what I found out - Let's Encrypt can't of course do the challenge response because everythings forwarded to the docker container, and there plesk or let's encrypt doesnt have access. But how do I get the https forward work in general? Ive removed the http forward 80 to portOfnginxInDocker80 but the https still doesnt work. It says 502 Bad Gateway. Nginx.

Some time later ... I can't find any solution. Right now the error I get, when redirecting both, 80 and 443 to the container ports:
This page isn’t working
gitlab.nextgamers.eu redirected you too many times.

I've cleared my cookies, still the same.

In the nginx log inside the container it says:
2017/07/12 15:19:34 [warn] 405#0: conflicting server name "gitlab.nextgamers.eu" on 0.0.0.0:443, ignored
2017/07/12 17:27:15 [warn] 424#0: conflicting server name "gitlab.nextgamers.eu" on 0.0.0.0:443, ignored

But only everytime i restart the container I think. I'm not sure though when this happens. Not when I load the page though.








Thank you! :)
 
Last edited:
Back
Top