I just created a CentOS 6.3 VM and followed these instructions for the gitlab install: http://howto.basjes.nl/linux/installing-gitlab-on-centos-6
I've tried this installation with both gitlab v3.01 and v2.91.
Here is what is working for me:
I can complete the gitlab install without problem
From the command-line, I can use passwordless authentication from the the gitlab service account to the gitolite service account
From the command-line, I can clone the gitolite-admin repo, make changes, and pushes the changes back to the remote repo
I can start the rails web app
I can login the web management site
I can create new accounts and login with the new accounts
Here's what I can't do:
I can't create projects (Repos)
I can't add ssh keys
I always get the same error:
GitLab was unable to access your Gitolite system.
In the githost.log log file, I get a less than useful error:
ERROR -> Timeout::Error execution expired
I've double checked permissions
Reviewed the gitlab.yml config file
Ran through the four suggested troubleshooting tips from the web page
Tried different versions of gitlab, but no matter what I do, I keep getting the same error.
I'm stuck because the logs don't tell me anything and I am able to access the gitolite repositories with the gitlab service account without issue. Anybody have any success with the most recent versions of CentOS/Gitlab/Gitolite? Any help would be much appreciated, thanks!
I know this is kind of late - but for completeness.
I've run into the same problem doing installation on recent Debian version.
It is, or was for me, caused by an old version of redis-server.
Related
I am currently trying to connect a GitHub Repo to Ionic App Flow.
Therefore, I have set up everything as proposed.
Install ionic CLI as suggested by npm install -g #ionic/cli
Created local App
Created App in App Flow dashboard
Set up SSH Key to GitHub
Additionally, I am admin in the GitHub Repo, yet I am not the owner of it.
If i want to connect the App Flow App to my GitHub Repo i do the following as instructed:
I link the ionic app by ionic link XXXXX
Following the instructions
Which git host would you like to use? >> GitHub.
Does the repository exist on GitHub? (Y/n) >> Y.
This is when the trouble kicks in. I am asked to auth to Github and get
back a list of all Repos I have access too. However, the one I am admin at
and want to connect the Repo to is not listed.
Same case in the dashboard under AppName > Settings > Git
All my personal repos and to I am Collaborater at are shown, but not the
one I am looking for. Can someone help and tell my why this is the case
and how to resolve this issue?
Constructive help appreciated.
Thanks in advance!
I just ran into this myself. Go to the Github organization's settings page, and on the Third-party access tab - turn off the application access restrictions. Then on the Ionic dashboard your organization should appear in the dropdown.
I have managed to finally add my devops account in sourcetree using the https://orgname.visualstudio.com path
Now I am having issues cloning the repository
I am using the path that devops gives me
https://orgname#dev.azure.com/orgname/MyProject/_git/MyRepo
but I get an error saying
This is not a valid source
The details reveal authentication issues... Yet it authenticated fine when adding the account.
What is going on? Does the azure account have to be the default account?
I managed to fix this by changing from the sourcetree embedded git to my system git Tools>Options>Git>Git Version>Select System. Afterwards when trying again it prompted me to login on my organization domain with 2 factor as if logging in on the devops web app directly.
My system Git is using manager-core for the credential management which is probably not the same system which the embedded version used.
I tried the above solutions (and more) but for me what in the end solved the problem was that the git-password I first wrongly entered when I tried to access the repo had been saved in Keychain (MacOS) and when I tried again this password was used without giving me the option to type it in again. I deleted the password to the Azure DevOps project in Keychain and then got prompted to enter the password again whereafter I pasted the Personal Access Token (!!) generated in Azure Devops and it finally worked!
It could happen when you entered wrong credentials and you don't get asked again, try this:
Go to : Sourtree->Preferences->Advance (tab)
Under: "Default usernames for URLs which do not include one:" delete your wrong credentials.
Try accessing your repo again with right credentials.
This is not the issue which caused by Azure devops. No matter https://xxx.visualstudio.com, or the URL which like dev.azure.com, they should all available git source.
For me, I just try with multi different git URLs, and found the few of URLs are failed with same error with you. But it prompt This is a git repository after I exit the SourceTree and re-configure the clone with same URL which encountered the error previously.
This seems be the most common Sourcetree problem which encountered by many users, not just the URL of azure devops that you occurred.
Check this thread, and try with its recommend way:
Open source tree, Tools -> Options -> Click on Git Tab -> Update
Embedded Git.
Or, consider the method I used: exit the Sourcetree, and re-configure the clone with same URL. (Not recommend since this can not permanently solve this issue)
Really confused by all this.
A few days ago I set up a windows azure vm.
I installed the build agent from azure devops
Followed the instructions for installation
and all was working!
Today - for some reason - it is complaining about not being able to read my git password:
Git fetch failed with exit code: 128
Nothing has changed.
No new PAT
No expired PAT
I figured I would remove the agent from the machine and reinstall and configure the agent - which I was kind of hoping wouldnt have worked because I then wouldnt be able to trust it in the future.
Sure enough it didnt work
Does anyone know what might be up?
A bonus question too - does anyone know if there is "just a build image I can use"? Liek the ones Azure uses? I see the repo on github and it has a load of scripts but not sure how you run them. Individually? Is there a master script I just cant see?
Thanks all!
This is the answer to my problem. I have read a lot of only helpful posts and they all point to different issues to the same error message.
It turns out that my ~/.gitconfig had the contents of my known_hosts file.
:|
I dont know how it happened, but it did. I deleted it and the git clone is working!
Thanks Lance and all!
Does anyone know what might be up?
When cloning azure devops repos using cmd.exe in local machine, we can use simple command like git clone URL. The URL comes from Azure Devops Repos=>Clone:
If it's one private azure devops repos, normally in local machine it will display a popup window for authentication. But now since we're running that command in pipeline job, we can't sign in with that popup window.
For this, there're two available choices:
1.git clone https://UserName:Password#dev.azure.com/OrgName/ProjectName/_git/RepoName
Replace username and password with those values after clicking the button. Replace those OrgName,ProjectName,RepoName with your actual ones.
2.Check this, you can also use PAT in that command like: git clone https://anything:{yourPAT}#dev.azure.com/OrgName/ProjectName/_git/RepoName
Replace {yourPAT} with your PAT. Replace those OrgName,ProjectName,RepoName with your actual ones.
I am getting this error message from GitKraken whenever I try to clone/fetch/push/push to any of my Github repositories:
failed to get server certificate: The handle is in the wrong state for the requested operation
I have no idea why this is happening, everything was working fine with my current setup until yesterday and I have checked that GitKraken is properly authorized to connect to my Github account and my repositories.
What I have tried:
Remove and add my credentials, reauthorize GitKraken.
Check my Git installation - can correctly push/pull and clone Github repos.
Tested on another machine, I can reproduce the issue.
Reinstalled GitKraken.
Run as administrator.
Removed the .gitkraken folder under %AppData% and reconnected from scratch.
Installed the kb3140245 update as suggested in the GitKraken Slack channel to someone else with a similar issue.
Generated and added SSH keys via the GitKraken UI to connect to Github.
Technical Information:
GitKraken version: 3.3.4
OS: Windows 7 Ultimate (x64)
Anyone else have a similar problem or know how to deal with this?
PS: I am not entirely sure what other technical information might be of use to troubleshoot the issue, so feel free to ask me in the comments below to update my question with any relevant information.
This is because Github removed weak cryptophic standard support (TLSv1 and TLSv1.1) - source
All you have to do on Windows devices (mostly on Windows 7) is set default TLS version to 1.2 - link
Step-by-step fix
Download the kb3140245 update from Microsoft, which is necessary to enable TLS 1.1 and TLS 1.2.
Download the easy fix utility from Microsoft and run it.
Restart your system. Everything should work fine. There might be issues with some websites etc, just rebooting your router should resolve any issues that might arise.
This broke me for a long time.
In gitkraken, go to the left window where "origin" is on your respective repos, click the three dots over flow and click "edit origin", make sure your pull & push urls are ssh or http NOT https.
UPDATE:
I found the answer. You can't use a pass phrase when you generate the key. (It's an easy mistake to make, since the GitHub instructions strongly suggest that you do use a pass phrase. Presumably the case of deploy keys is an exception).
Have been trying to setup a Jenkins server on Ubuntu 14.04. Have installed Jenkins no problems, but am unable to connect to the secure repository URL. I'm getting permission denied (public key). I have tried a lot of solutions that I researched on the web, but still no success.
Here are the details:
Jenkins installed no problems and running as user jenkins
GitHub plugin is installed
Have followed the github instructions on keygen. I tried this as my own user (kim) on the ubuntu machine, and have also done it as the jenkins user
Am loading the public key as a deploy key against the github repo
Am loading the private key directly in the credentials in jenkins
Have tried numerous different usernames in the Jenkins credentials setup (including git, git#github.com, and my git hub user name)
The authentication test (ssh -T git#github.com) works no bother
I have tried this solution, Authenticate Jenkins CI for Github private repository. Again, the ssh test works fine (against the alias), but Jenkins still fails
I'm running out of ideas?