#77 push to port 22 fails with "Network unreacheable"

Closed
opened 4 months ago by ldesousa · 6 comments

Pushing a project to Codeberg for the first time. Created an account and registered a SSH key. Then added the new remote and tried to push:

$ git remote add codeberg git@codeberg.org:ldesousa/projections-compare.git
$ git push -u codeberg master
ssh: connect to host codeberg.org port 22: Network is unreachable
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

What is wrong?

Pushing a project to Codeberg for the first time. Created an account and registered a SSH key. Then added the new remote and tried to push: ``` $ git remote add codeberg git@codeberg.org:ldesousa/projections-compare.git $ git push -u codeberg master ssh: connect to host codeberg.org port 22: Network is unreachable fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` What is wrong?
ashimokawa commented 4 months ago
Owner

@ldesousa If you had too much failed authorization attempts It could be that your IP is blocked for while.

it should work the way you tried it.

@ldesousa If you had too much failed authorization attempts It could be that your IP is blocked for while. it should work the way you tried it.
hw commented 4 months ago
Owner

Yeah, fail2ban will trigger to block DDOS attacks, but release the block automatically after a while. I am sure you have checked out https://codeberg.org/Codeberg/Documentation/wiki/SSH-key-for-Codeberg?

Yeah, fail2ban will trigger to block DDOS attacks, but release the block automatically after a while. I am sure you have checked out https://codeberg.org/Codeberg/Documentation/wiki/SSH-key-for-Codeberg?
ldesousa commented 4 months ago
Poster

This is not due to failed authentication attempts, I am getting this from the very first time I tried. It looks like port 22 is simply closed:

$ ssh -T git@codeberg.org
ssh: connect to host codeberg.org port 22: Network is unreachable

$ ping codeberg.org
PING codeberg.org (159.69.0.178) 56(84) bytes of data.
64 bytes from codeberg.org (159.69.0.178): icmp_seq=1 ttl=52 time=13.7 ms
64 bytes from codeberg.org (159.69.0.178): icmp_seq=2 ttl=52 time=13.5 ms
64 bytes from codeberg.org (159.69.0.178): icmp_seq=3 ttl=52 time=13.5 ms
^C
--- codeberg.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 13.528/13.600/13.712/0.156 ms

$ telnet codeberg.org 22
Trying 159.69.0.178...
Trying 2a01:4f8:1c0c:4943::1...
telnet: Unable to connect to remote host: Network is unreachable
This is not due to failed authentication attempts, I am getting this from the very first time I tried. It looks like port 22 is simply closed: ``` $ ssh -T git@codeberg.org ssh: connect to host codeberg.org port 22: Network is unreachable $ ping codeberg.org PING codeberg.org (159.69.0.178) 56(84) bytes of data. 64 bytes from codeberg.org (159.69.0.178): icmp_seq=1 ttl=52 time=13.7 ms 64 bytes from codeberg.org (159.69.0.178): icmp_seq=2 ttl=52 time=13.5 ms 64 bytes from codeberg.org (159.69.0.178): icmp_seq=3 ttl=52 time=13.5 ms ^C --- codeberg.org ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 13.528/13.600/13.712/0.156 ms $ telnet codeberg.org 22 Trying 159.69.0.178... Trying 2a01:4f8:1c0c:4943::1... telnet: Unable to connect to remote host: Network is unreachable ```
ashimokawa commented 4 months ago
Owner

@ldesousa

Port 22 is definitely open. If you want you can send your IP to contact@codeberg.org, so we can manually unblock you.

@ldesousa Port 22 is definitely open. If you want you can send your IP to contact@codeberg.org, so we can manually unblock you.
ldesousa commented 4 months ago
Poster

I am connecting from a large network in a University domain (9 000 users) that was blocked from Codeberg (possibly by the action of someone else). It is now unblocked.

I am connecting from a large network in a University domain (9 000 users) that was blocked from Codeberg (possibly by the action of someone else). It is now unblocked.
hw commented 4 months ago
Owner

Thank you for confirming. We have relaxed the fail2ban rules in order to minimize the risk of similar issues in the future.

Thank you for confirming. We have relaxed the fail2ban rules in order to minimize the risk of similar issues in the future.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.