-
-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCS kex_exchange_identification #8890
Comments
Most likely firewall or networking issue, see https://stackoverflow.com/a/69398009/225718 |
I thought the same and temporarily disabled the firewall with no positive results. I couldn't find any similar issues in the issue section of the weblate repo. So I thought I would open a new one. As you said, the issue is more likely to arise from outside of weblate. But I didn't know for sure. I'll post an update here if I find any solution. |
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
Is it possible to let weblate use port 443 instead of 22 for ssh to github? Adding this section to the config file of ssh on my debian host solves the issue for system users, but for weblate in docker the issue still exists:
I've temporarily disabled iptables. Nothing really helps. I don't see any other solution. |
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
You can customize the SSH client for Weblate in |
Thank you very much! That worked like a charm. I still don't know why this is happening. But the issue is resolved. :) |
Describe the issue
Image of the error in weblate: https://imgur.com/RIuuSE3
Also, when going to https://yourdomain.com/manage/ssh/ and try to add a host key. In this example github.com. I get an error saying this:
Failed to get host key:
. A host key for github.com already exists from when it worked. Not sure if this is related.This issue is also present if I create a new project and component.
I already tried
Steps to reproduce the behavior
I'm not sure how to reproduce this. I'm just hoping somebody else knows more.
Expected behavior
Weblate being able to fetch upstream changes.
Screenshots
https://imgur.com/RIuuSE3
Exception traceback
How do you run Weblate?
Docker container
Weblate versions
Weblate deploy checks
Additional context
No response
The text was updated successfully, but these errors were encountered: