-
Notifications
You must be signed in to change notification settings - Fork 204
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
Improve error message about unsupported commands on SSH destination (was: SSH backup to Hetzner Storage Box: "test" command not available) #1745
Comments
Reminds me of #1674. Maybe this is a similar problem? EDIT: Sorry, I realized that the linked issue is written in German. The issue was about a Synology NAS device. To my understanding the difference was between using |
I tried a different approach by mounting the Storage Box sub-account via
|
Hello Phillip, We have to wait for a response from my teammate "aryoda". He is deeper into that topic. Hetzner itself refused to provide us with a test account in the past. They also won't be helpful. Don't hesitate to warm up the Issue if you don't get any response in some weeks. Christian |
Did you checked #1674 ? Did this help you? Is your Issue a duplicate of it? |
I didn't investigate further because I switched to restic with resticprofile. |
Thank you for reporting back. |
I am facing the same issue, with a Hetzner account:
Trimming down the ssh command to just
|
The list of available commands is just:
I'm afraid this may be a bit too restricted to get BIT working :-/ |
For my own and because Hetzner once reject my requests, I am not much motivated investing resources into this. But I am also open for suggestions how to solve, RPs and test scenarios. The "test -e" command just tests if the folder does exist. Maybe "stat" could be used for this instead. But I am unable to test this because Hetzner won't provide us an account. They provide rsync, restic, borg on their servers. If they wont to support Back In Time they do have enough man power doing so. We are open for PRs. |
Hetzner has confirmed that support for BackInTime is on their roadmap, but can't say when it will be available... |
Great to here that Hetzner will jump in. Let's see if they suggest the use of another command then |
Can you please do me a favour and test this command (replace login credentials):
I replaced Can you please also provide the output of |
Unfortunately their shell is _really_ restricted.
The suggested command doesn't work:
/home > d=0;[ -e "./" ] || d=1
Command not found. Use 'help' to get a list of available commands.
Even a simple a simple assignment fails:
… /home > d=0
Command not found. Use 'help' to get a list of available commands.
On 26-08-2024 13:33, buhtz wrote:
Can you please do me a favour and test this command (replace login
credentials):
|ssh -o ServerAliveInterval=240 -o LogLevel=Error -o
IdentityFile=/home/robert/.ssh/id_rsa -p 23
***@***.*** d=0;[ -e "./" ] || d=1 |
I replaced |test -e| with |[ -e ]|.
—
Reply to this email directly, view it on GitHub
<#1745 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEY2JRDZZEYQCKPHXLQ2EM3ZTMHBRAVCNFSM6AAAAABIURJVIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBZHE4DQMJRHA>.
You are receiving this because you commented.Web Bug from
https://github.com/notifications/beacon/AEY2JRFEXXIX557ELUJRF7LZTMHBRA5CNFSM6AAAAABIURJVIWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUJV6PRM.gifMessage ID: ***@***.***>
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage",
"potentialAction": { ***@***.***": "ViewAction", "target":
"#1745 (comment)", "url": "#1745 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
|
OK, lets try
This should work. But the question is if we should use |
Hello Robert, |
It will not work as already the variable assignment 'd=0' is not supported. |
Mhm... It worked on my bash. So this is another Hetzer-restriction? Do you have any other ideas? Or can we just say Hetzer is not supported and improving the error message. |
Suggested approachDo not support restricted systems like Hetzer is using. Improve the error message to make it more clear to the user what is going on. Maybe do a previous check if commands are available or not. Also add a FAQ entry about known error messages in context of Hetzner boxes. |
I am trying to set up a backup profile for my Hetzner Storage Box under a sub-account. The sub-account is accessible from outside the Hetzner network and SSH access is enabled. I have also installed the public SSH key on this sub-account so that I can use SSH without entering my password.
The problem I'm running into is that backintime tells me that it
Couldn't create remote path.: /home
. In the config tab I setPath
to/home
.I think it's due to the structure of a Hetzner Storage Box sub-account, because when I SSH into that sub-account, the starting directory is the
/home
folder of that sub-account. When you create a sub-account for your Hetzner Storage Box you define a base directory and this base directory will be the/home
folder. Outside this/home
folder (under/
) a subaccount has no permissions to do anything.Running Back in Time 1.4.3 under Pop!_OS 22.04 LTS (Linux-6.8.0-76060800daily20240311-generic-x86_64-with-glibc2.35).
The text was updated successfully, but these errors were encountered: