-
Notifications
You must be signed in to change notification settings - Fork 199
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
Issue with new SSH proxy settings overwriting the default port #1815
Comments
Thank you for testing and reporting. Looks like a candidate for a quick and new release 1.5.1. |
Should be fixed. I checked it on a VM and my productive machine. Would you like to give it a try with that tarball before I prepare a new release? |
Yes, fixed now with 1.5.1-dev. |
Thank you very much for testing. I am assuming that you will do some further tests with your rpm packaging? |
I am just testing it locally for my personal backup, I think there's not much more I can do now. |
In fedora the package will be in updates-testing for, normally 7 days, I can extend that a bit and we see if things come up. |
Thank you for this offer, but this violates another Deadline. I need to reach Ubuntus DebianPackageFreeze. |
I am testing backintime 1.5.0 for an update in fedora. I noticed that I couldn't ping my local NAS. Checking the logs I found out why.
Please see the settings here:
As you can see, actually it should connect using port 21212, however, when checking the logs, it is using port 22, which is set by the proxy settings.
A workaround for that is to enable the proxy settings
and then it connects with the desired port 21212. Please see the attached log file.
backintime_logs.txt
My guess is that it's caused by #1688
The text was updated successfully, but these errors were encountered: