• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

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