• 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 Permission for Plesk ssh User

IfCondition

New Pleskian
Hello because I get no answer at gitlab I ask here if someone knows more.
I have switched from Docker Gitlab to Gitlab directly on debian and use it in combination with Plesk now I have the connection to Gitlab with a subdomain managed but as soon as I make Gitlab reconfigure all folder permissions are changed again and then I get a permanent 502 error because my domain user does not come to the folders, I also gave my user test white root permissions and the git groups but even then not as soon as I set chmod 775 /var/opt/gitlab recursive I get limited access to gitlab.

These are my nginx settings pointing to a conf:

location ~ / {
# serve static files from defined root folder;.
# @gitlab is a named location for the upstream fallback, see below
# for manual installation
# root /home/git/gitlab/public;
# for omnibus installation
# root /opt/gitlab/embedded/service/gitlab-rails/public;
try_files $uri $uri/index.html $uri.html @gitlab;
}

# if a file, which is not found in the root folder is requested,
# then the proxy pass the request to the upsteam (gitlab unicorn)
location @gitlab {
proxy_read_timeout 300; # https://github.com/gitlabhq/gitlabhq/issues/694
proxy_connect_timeout 300; # https://github.com/gitlabhq/gitlabhq/issues/694
proxy_redirect off;

proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header host $http_host;
proxy_set_header X-Real-IP $remote_addr;

proxy_pass http://gitlab;

}

This is my config
upstream gitlab {
# for manual installation
# server unix:/home/git/gitlab/tmp/sockets/gitlab.socket;
# for omnibus installation
server unix:/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket;
}

Hope for a solution
 
Might want to look at some support posts on stackoverflow for some help such as installing GitLab on VPS running Parallels Plesk or google around for additional help articles like Install GitLab 11 on Ubuntu 16.04 LTS with Plesk 17 Onyx and HTTPS / SSL - Christian Kauppert

Basically you're introducing something that isn't 100% normal in the Plesk world. Personally, if it's something that requires installing additional services that does not utilize Docker or Node (or at least make it easy to do straight in Plesk), I would use a different server for it to keep things separated. Like I said, this is just me. It is still possible to do all on the same server but you can run into issues and dependency issues if not careful.

But, in either case, like I said, check out those two links above and see if any of them helps you get it working.
 
Back
Top