Troubleshooting Gitlab: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Clone on Windows: Could not resolve hostname == | === Clone on Windows: Could not resolve hostname === | ||
__FORCETOC__ | |||
If you clone a project using SSH, Windows may answer: | If you clone a project using SSH, Windows may answer: | ||
| Line 11: | Line 12: | ||
# Try adding a <code>/</code> after the colon, i.e: <code>...forge:etsi.org:/_username_...</code> | # Try adding a <code>/</code> after the colon, i.e: <code>...forge:etsi.org:/_username_...</code> | ||
# Try using HTTPS instead of SSH | # Try using HTTPS instead of SSH | ||
=== "Authentication Failed" when pushing on master === | |||
If you receive a "Authentication error" while pushing your changes to the ''master'' branch, you most probably have a role "Developer" in the project, which does not allow you to push onto the master branch. | |||
You will want to push to another branch (an existing one or a newly created), by issuing the following git command (or similar operation using a visual tool): | |||
git push origin <local-branch>:<remote-branch> | |||
For example, if you developed a new feature you would like to contribute in a new branch called "new-feature", you will want to issue the command: | |||
git push origin new-feature:new-feature | |||
== Authorization issues (e.g. 403) == | |||
Check the following: | |||
=== 1. Check logging into Gitlab with your EOL === | |||
Are you able to sign in at https://forge.etsi.org/gitlab/users/sign_in with your EOL account? | |||
=== 2. Check group membership and permissions === | |||
Once logged in, visit <nowiki>https://forge.etsi.org/gitlab/mec</nowiki> . In case you have “Request group access” below the group name please click on it. | |||
=== 3. Check your SSH setup === | |||
Once set up your SSH keys, to verify they are working you need to issue: | |||
ssh [[Mailto:git@forge.etsi.org|git@forge.etsi.org]] | |||
And verify that you see the following: | |||
'' PTY allocation request failed on channel 0 | |||
Welcome to GitLab, <YOUR_EOL_USER>! | |||
Connection to forge.etsi.org closed.'' | |||
'' '' | |||
=== 4. Verify that remote URL is correct === | |||
The URL for the ''origin'' remote should be in the following format (where 'group' and 'project' are replaced by your group and project names): | |||
* '''git@forge.etsi.org:<group>/<project>.git''' for SSH access, | |||
* '''https://forge.etsi.org/rep/<group>/<project>.git''' for SSH access, | |||
To change the remote URL, use: | |||
$ git remote set-url origin <CORRECT-URL> | |||
Latest revision as of 14:22, 24 July 2019
Clone on Windows: Could not resolve hostname[edit | edit source]
If you clone a project using SSH, Windows may answer:
ssh: Could not resolve hostname forge:etsi.org:_username_: Name or service not known.
How to fix:
- Check that there are not mispellings in the URL
- Try adding a
/after the colon, i.e:...forge:etsi.org:/_username_... - Try using HTTPS instead of SSH
"Authentication Failed" when pushing on master[edit | edit source]
If you receive a "Authentication error" while pushing your changes to the master branch, you most probably have a role "Developer" in the project, which does not allow you to push onto the master branch.
You will want to push to another branch (an existing one or a newly created), by issuing the following git command (or similar operation using a visual tool):
git push origin <local-branch>:<remote-branch>
For example, if you developed a new feature you would like to contribute in a new branch called "new-feature", you will want to issue the command:
git push origin new-feature:new-feature
Authorization issues (e.g. 403)[edit | edit source]
Check the following:
1. Check logging into Gitlab with your EOL[edit | edit source]
Are you able to sign in at https://forge.etsi.org/gitlab/users/sign_in with your EOL account?
2. Check group membership and permissions[edit | edit source]
Once logged in, visit https://forge.etsi.org/gitlab/mec . In case you have “Request group access” below the group name please click on it.
3. Check your SSH setup[edit | edit source]
Once set up your SSH keys, to verify they are working you need to issue:
ssh [[1]]
And verify that you see the following: PTY allocation request failed on channel 0
Welcome to GitLab, <YOUR_EOL_USER>! Connection to forge.etsi.org closed.
4. Verify that remote URL is correct[edit | edit source]
The URL for the origin remote should be in the following format (where 'group' and 'project' are replaced by your group and project names):
- git@forge.etsi.org:<group>/<project>.git for SSH access,
- https://forge.etsi.org/rep/<group>/<project>.git for SSH access,
To change the remote URL, use:
$ git remote set-url origin <CORRECT-URL>