You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently im not able to mirror a project from my gitlab instance into redmine.
I always get "URL Permission denied, please try again." I read the realy short documentation and there is the section about private Repositories:
"At this moment only ssh access with redmine user ssh key is supported."
What does this mean? My repos in gitlab are accessible via ssh "git@gitlab" or https. Which key do i need to provide to gitlab?
I tried to clone the repo as redmine user and its ssh key and its working (Pubkey as deploykey in the gitlab project - repository).
How should i specify username and or key in the url?
Thank you in advance,
Thomas
The text was updated successfully, but these errors were encountered:
In my case it starts working when I've put gitlab deploy key (private part) in .ssh folder in home folder for the user from which redmine has started and working. I'm using shared hosting and at first I've get the same error as you, but after a little of debugging I've realized that ruby environment (passanger in my case) started from another user, thus my administrative user's .ssh folder just was the wrong place for gitlab deploy key.
Hi,
currently im not able to mirror a project from my gitlab instance into redmine.
I always get "URL Permission denied, please try again." I read the realy short documentation and there is the section about private Repositories:
"At this moment only ssh access with redmine user ssh key is supported."
What does this mean? My repos in gitlab are accessible via ssh "git@gitlab" or https. Which key do i need to provide to gitlab?
I tried to clone the repo as redmine user and its ssh key and its working (Pubkey as deploykey in the gitlab project - repository).
How should i specify username and or key in the url?
Thank you in advance,
Thomas
The text was updated successfully, but these errors were encountered: