• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Plesk Obsidian 18 + Docker + Gitlab - SSL and SSH issues

pau.iranzo

New Pleskian
Hi everyone,

We have installed the Docker extension in our Plesk Obsidian 18 server. After that we have installed the gitlab-ce container and associated it with a custom subdomain. To make it work we had to:
  • Add the correct volume mapping (so we don't loose data when we restart the container)
  • Add an extra environment variable (GITLAB_OMNIBUS_CONFIG indicating the external_url: external_url 'http://git.xxxx.com/'; gitlab_rails['lfs_enabled'] = true;)
  • Add the port mapping in the custom subdomain
1582601357145.png
1582601566171.png

What works:
What I would like to 'improve':
  • Configure the external_url with https instead of http. Letsencrypt works at a subdomain level (when there isn't any docker), but docker won't start if I change the external url to use https. Basically, when I try to set the external_url with https, the container is not able to start (when with http it works fine). I would like to do this to have the proper url in my repos (the screenshot below shows the error when the container tries to start but throws the letsencrypt error):

1582602800584.png
  • On the other hand, the most important thing: I would like to clone my repo using "git clone [email protected]:magento/regalosconfoto-magento2.git" instead of using the 'git clone ssh://[email protected]:32773/magento/regalosconfoto-magento2.git' expression. When I try to clone it with the 'short' expression, it asks me for password (because there isn't any actual port mapping that tells the server that when cloning, port 22 should point to port 32773). I've tried to set a different port mapping at a subdomain/subfolder level, but it doesn't work either (it still do not connect with the docker machine port 22):
1582603195804.png

How can I solve these 2 issues? I tried to explain as better as possible... but it isn't easy :S

Thank you for your help
 

Attachments

  • 1582601894084.png
    1582601894084.png
    43.8 KB · Views: 100
  • 1582603153292.png
    1582603153292.png
    17.7 KB · Views: 150
Hi all,

Thanks to this other post:

I've been able to solve the issue related to https. Basically, I had to specify the nginx listen port on GITLAB_OMNIBUS_CONFIG as follows:
GITLAB_OMNIBUS_CONFIG = external_url 'https://gitlab.brildor.com'; nginx['listen_port']=80; nginx['listen_https']=false;

I still cannot clone the respository without using ssh://.
 
Back
Top