Maybe I am doing something wrong, but I wasn't able to figure it out. I am trying to use my repository with my SSH key, but always get the response 'Connection refused'.
I set up my local repository with
url = teahub@teahub.io:madhatter/GoService.git
changing it from the https url which worked well but asked me too often for my credentials. ;)
Can't reach teahub with SSH keys #10
Have you added your public ssh key to your identity in the settings/profile/ssh-keys menu?
One note: to protect against DDOS attacks, IPs with repeatedly failing connection attempts get temporarily blocked. We still need to adjust the enforced timeout limit, so please provide feedback if the settings are too restrictive/too lazy.
To find out whether this filter caught you, please try to connect from a different IP for testing and let us know whether it works.
TeaHub is now Codeberg.org. The fail2ban config is similar. Please follow-up and re-open this issue if similar problems occur.
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?