• 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

Search results

  1. E

    Issue Plesk 18, Git & Bitbucket Server

    I had a similar issue with Plesk Obsidian and Github and I manage to resolve it with the help of a support agent from Plesk (through teamviewer). You basically have to delete or rename the id_rsa, id_rsa.pub and known_hosts files from the .ssh folder and recopy any ssh keys to your github...
  2. E

    Issue Github integration errors. Unable to pull updates from the remote repository.

    Anyway, issue is solved by deleting id_rsa, id_rsa.pub and known_hosts file from the .ssh folder. You will have to re-copy the ssh key and clone the repo again.
  3. E

    Issue Github integration errors. Unable to pull updates from the remote repository.

    So, with SSH port 22 and the same settings on a Plesk Onyx server this is working no problem. It might be an issue with Plesk Obsidian and the Git extension.
  4. E

    Issue Github integration errors. Unable to pull updates from the remote repository.

    I am using this method mentioned here: Is it possible to connect to private Github repositories using Plesk Git extension?, but I am unable to connect. I always get the following error: Public key for the server at 'github.com' is already known in...
Back
Top