Skip to content
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

Closed
hannes101 opened this issue Jul 27, 2024 · 7 comments · Fixed by #1817
Closed

Issue with new SSH proxy settings overwriting the default port #1815

hannes101 opened this issue Jul 27, 2024 · 7 comments · Fixed by #1817
Assignees

Comments

@hannes101
Copy link

hannes101 commented Jul 27, 2024

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:
image
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.

DEBUG: [common/tools.py:1342 keyringSupported] Found appropriate keyring 'keyring.backends.chainer'
DEBUG: [common/tools.py:1271 keyringSupported] Keyring config file folder: /home/johannes/.config/python_keyring
DEBUG: [common/tools.py:1285 keyringSupported] Available keyring backends:
DEBUG: [common/tools.py:1288 keyringSupported] keyring.backends.fail.Keyring (priority: 0)
DEBUG: [common/tools.py:1288 keyringSupported] keyring.backends.SecretService.Keyring (priority: 5)
DEBUG: [common/tools.py:1288 keyringSupported] keyring.backends.libsecret.Keyring (priority: 4.8)
DEBUG: [common/tools.py:1288 keyringSupported] keyring.backends.chainer.ChainerBackend (priority: 10)
DEBUG: [common/tools.py:1330 keyringSupported] Metaclass keyring.backends.Gnome.Keyring not found: AttributeError("module 'keyring.backends' has no attribute 'Gnome'")
DEBUG: [common/tools.py:1330 keyringSupported] Metaclass keyring.backends.kwallet.Keyring not found: AttributeError("module 'keyring.backends.kwallet' has no attribute 'Keyring'")
DEBUG: [common/tools.py:1330 keyringSupported] Metaclass keyring.backend.SecretServiceKeyring not found: AttributeError("module 'keyring.backend' has no attribute 'SecretServiceKeyring'")
DEBUG: [common/tools.py:1330 keyringSupported] Metaclass keyring.backend.GnomeKeyring not found: AttributeError("module 'keyring.backend' has no attribute 'GnomeKeyring'")
DEBUG: [common/tools.py:1330 keyringSupported] Metaclass keyring.backend.KDEWallet not found: AttributeError("module 'keyring.backend' has no attribute 'KDEWallet'")
DEBUG: [common/tools.py:1339 keyringSupported] Available supported backends: [<class 'keyring.backends.SecretService.Keyring'>, <class 'keyring.backends.kwallet.DBusKeyring'>, <class 'keyring.backends.chainer.ChainerBackend'>]
DEBUG: [common/tools.py:1342 keyringSupported] Found appropriate keyring 'keyring.backends.chainer'
DEBUG: [common/sshtools.py:293 SSH.startSshAgent] ssh-agent already running. Skip starting a new one.
DEBUG: [common/sshtools.py:448 SSH.unlockSshAgent] Private key /home/johannes/.ssh/2019QnapNAS is already unlocked in ssh agent
DEBUG: [common/sshtools.py:725 SSH.checkPingHost] Check ping host "192.168.178.45:22"
DEBUG: [common/sshtools.py:756 SSH.checkPingHost] Ping 192.168.178.45 failed. Host is down or wrong address.

A workaround for that is to enable the proxy settings
image

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

@buhtz
Copy link
Member

buhtz commented Jul 27, 2024

Thank you for testing and reporting. Looks like a candidate for a quick and new release 1.5.1.

@buhtz
Copy link
Member

buhtz commented Jul 27, 2024

backintime-1.5.1-dev.tar.gz

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?

@hannes101
Copy link
Author

Yes, fixed now with 1.5.1-dev.
backintime_logs.txt

@buhtz
Copy link
Member

buhtz commented Jul 27, 2024

Thank you very much for testing.

I am assuming that you will do some further tests with your rpm packaging?
Hope not but you might find something else. ☣️ Because of that I will wait with the next release until you give me green light, OK? 🟢

@hannes101
Copy link
Author

I am just testing it locally for my personal backup, I think there's not much more I can do now.

@hannes101
Copy link
Author

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.

@buhtz
Copy link
Member

buhtz commented Jul 27, 2024

Thank you for this offer, but this violates another Deadline. I need to reach Ubuntus DebianPackageFreeze.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants