• 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.

Issue Plesk suggests enabling SSH access for git when it has already been enabled

websavers

Regular Pleskian
We have a subscription where a git repo was set up within Plesk to be pushed from a local repo on their remote computer. This is a Customer user, not an Admin.

In the settings for the repository, Plesk suggests this: "To make the repository available over SSH, enable SSH access for the system user here (Link to Web Hosting Access page)."

This is generally a helpful message, however in this instance the customer has already enabled SSH access which is chrooted AND there is no option for a full shell (as they are not an admin). My questions are:
  1. If chrooted SSH is acceptable for git, then why does it still show that message?
  2. If a chrooted or nologin shell are the only options and git requires a complete shell for the system user, then why does the git extension suggest SSH connectivity at all? (ie: that message should never appear unless a full shell is available to the user).
Thanks to anyone who can help answer these questions
 
Back
Top