On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Is it possible to connect to private Github repositories using Plesk Git extension?

Follow

Comments

5 comments

  • Avatar
    Marek Kaczanowicz

    Hi, the connection is successful, but the auto-deployment seems to be not working from bitbucket...

     

    When I press the PULL UPDATES button - all OK, however, if I Commit to bitbucket, waiting few minutes and the repository is not populated automatically.

     

    What can be the reason of this?

    0
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hello, @Marek Kaczanowicz!

    In order to automate this process, web hooks should be used, see the following page for the details:

    https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/git-support/using-remote-git-hosting.75848/#o76296 

    0
    Comment actions Permalink
  • Avatar
    Evangelos Sapountzis

    I am using this method mentioned here, but I am unable to connect. I always get the following error:

     

    Public key for the server at 'github.com' is already known in '/var/www/vhosts/new.domain.com/.ssh/git_known_hosts'.
    ssh: connect to host github.com port 49153: Connection timed out
    fatal: Could not read from remote repository.
    Please make sure you have the correct access rights
    and the repository exists.

     

    Even if I try changing the SSH port to the default 22, I keep getting similar errors.

     

    Any suggestions?

    0
    Comment actions Permalink
  • Avatar
    Denis Bykov

    @Evangelos Sapountzis

    The cause of this behavior is not clear, but I can see that you have resolved it by deleting id_rsa, id_rsa.pub and known_hosts file from the .ssh folder, according to https://talk.plesk.com/threads/github-integration-errors-unable-to-pull-updates-from-the-remote-repository.354967/

    0
    Comment actions Permalink
  • Avatar
    Evangelos Sapountzis

    @... Yes, indeed. I managed to resolve it with the help of a Plesk support agent. And the solution is the one found on the link you posted. 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request