SSH connection to Gitlab is getting timeout
I've followed the official Gitlab docs (https://docs.gitlab.com/ee/ssh/) to make my keys using the comand:
ssh-keygen -t ed25519 -C "email@example.com"
But I'm getting timeout error as you can see at this image:
All my issues
The first page is the error, the pane below at left is the content of my ~/.ssh/config file, and the last pane is the content of my ~/.ssh directory.
Edit1:
I've tried to connect with telnet with the command telnet gitlab.com 22 and I'm getting telnet: Unable to connect to remote host: Connection timed out.
But I can ping gitlab normally
Ping to Gitlab
Edit2:
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
ssh ssh-keys gitlab
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
add a comment |
I've followed the official Gitlab docs (https://docs.gitlab.com/ee/ssh/) to make my keys using the comand:
ssh-keygen -t ed25519 -C "email@example.com"
But I'm getting timeout error as you can see at this image:
All my issues
The first page is the error, the pane below at left is the content of my ~/.ssh/config file, and the last pane is the content of my ~/.ssh directory.
Edit1:
I've tried to connect with telnet with the command telnet gitlab.com 22 and I'm getting telnet: Unable to connect to remote host: Connection timed out.
But I can ping gitlab normally
Ping to Gitlab
Edit2:
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
ssh ssh-keys gitlab
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
1
This sounds like a (possibly transient) network problem and not an ssh / authentication problem. What happens if you typetelnet gitlab.com 22? If it clears the screen and gives you some kind of banner, hit Enter to get back to your shell prompt and try thesshagain. If thetelnetfails, then you simply have a problem connecting to gitlab.com. Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 26 '18 at 4:41
gitlab.com is not listening on port 22, I've tested it from France, UK and USA
– user1330614
Dec 26 '18 at 22:45
And how can I workaround of it?
– Ziggoto
Dec 26 '18 at 23:11
add a comment |
I've followed the official Gitlab docs (https://docs.gitlab.com/ee/ssh/) to make my keys using the comand:
ssh-keygen -t ed25519 -C "email@example.com"
But I'm getting timeout error as you can see at this image:
All my issues
The first page is the error, the pane below at left is the content of my ~/.ssh/config file, and the last pane is the content of my ~/.ssh directory.
Edit1:
I've tried to connect with telnet with the command telnet gitlab.com 22 and I'm getting telnet: Unable to connect to remote host: Connection timed out.
But I can ping gitlab normally
Ping to Gitlab
Edit2:
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
ssh ssh-keys gitlab
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
I've followed the official Gitlab docs (https://docs.gitlab.com/ee/ssh/) to make my keys using the comand:
ssh-keygen -t ed25519 -C "email@example.com"
But I'm getting timeout error as you can see at this image:
All my issues
The first page is the error, the pane below at left is the content of my ~/.ssh/config file, and the last pane is the content of my ~/.ssh directory.
Edit1:
I've tried to connect with telnet with the command telnet gitlab.com 22 and I'm getting telnet: Unable to connect to remote host: Connection timed out.
But I can ping gitlab normally
Ping to Gitlab
Edit2:
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
ssh ssh-keys gitlab
ssh ssh-keys gitlab
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
edited Dec 26 '18 at 23:18
Ziggoto
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
asked Dec 26 '18 at 4:27
ZiggotoZiggoto
11
11
1
This sounds like a (possibly transient) network problem and not an ssh / authentication problem. What happens if you typetelnet gitlab.com 22? If it clears the screen and gives you some kind of banner, hit Enter to get back to your shell prompt and try thesshagain. If thetelnetfails, then you simply have a problem connecting to gitlab.com. Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 26 '18 at 4:41
gitlab.com is not listening on port 22, I've tested it from France, UK and USA
– user1330614
Dec 26 '18 at 22:45
And how can I workaround of it?
– Ziggoto
Dec 26 '18 at 23:11
add a comment |
1
This sounds like a (possibly transient) network problem and not an ssh / authentication problem. What happens if you typetelnet gitlab.com 22? If it clears the screen and gives you some kind of banner, hit Enter to get back to your shell prompt and try thesshagain. If thetelnetfails, then you simply have a problem connecting to gitlab.com. Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Dec 26 '18 at 4:41
gitlab.com is not listening on port 22, I've tested it from France, UK and USA
– user1330614
Dec 26 '18 at 22:45
And how can I workaround of it?
– Ziggoto
Dec 26 '18 at 23:11
1
1
This sounds like a (possibly transient) network problem and not an ssh / authentication problem. What happens if you type
telnet gitlab.com 22? If it clears the screen and gives you some kind of banner, hit Enter to get back to your shell prompt and try the ssh again. If the telnet fails, then you simply have a problem connecting to gitlab.com. Please do not respond in comments; edit your question to make it clearer and more complete.– Scott
Dec 26 '18 at 4:41
This sounds like a (possibly transient) network problem and not an ssh / authentication problem. What happens if you type
telnet gitlab.com 22? If it clears the screen and gives you some kind of banner, hit Enter to get back to your shell prompt and try the ssh again. If the telnet fails, then you simply have a problem connecting to gitlab.com. Please do not respond in comments; edit your question to make it clearer and more complete.– Scott
Dec 26 '18 at 4:41
gitlab.com is not listening on port 22, I've tested it from France, UK and USA
– user1330614
Dec 26 '18 at 22:45
gitlab.com is not listening on port 22, I've tested it from France, UK and USA
– user1330614
Dec 26 '18 at 22:45
And how can I workaround of it?
– Ziggoto
Dec 26 '18 at 23:11
And how can I workaround of it?
– Ziggoto
Dec 26 '18 at 23:11
add a comment |
1 Answer
1
active
oldest
votes
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1387716%2fssh-connection-to-gitlab-is-getting-timeout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
add a comment |
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
add a comment |
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
I've got it. I have to change my ~/.ssh/config and put these lines:
Host gitlab.com
Hostname altssh.gitlab.com
User git
Port 443
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_ed25519
I've followed this tutorial: here
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
answered Dec 26 '18 at 23:18
ZiggotoZiggoto
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1387716%2fssh-connection-to-gitlab-is-getting-timeout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This sounds like a (possibly transient) network problem and not an ssh / authentication problem. What happens if you type
telnet gitlab.com 22? If it clears the screen and gives you some kind of banner, hit Enter to get back to your shell prompt and try thesshagain. If thetelnetfails, then you simply have a problem connecting to gitlab.com. Please do not respond in comments; edit your question to make it clearer and more complete.– Scott
Dec 26 '18 at 4:41
gitlab.com is not listening on port 22, I've tested it from France, UK and USA
– user1330614
Dec 26 '18 at 22:45
And how can I workaround of it?
– Ziggoto
Dec 26 '18 at 23:11