Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For quite some time now Hetzner Storage Box backups had stopped working with the existing SSH config.
The output when performing the backup would simply be:
This is because they seem to have tightened up the allowed commands on the backend, so the
cdcommand fails.As far as I can tell, it isn't necessary to change directory first, as the
--restrict-to-pathshould take care of this.Also, the executable path no longer works with an absolute path, and the executable name has changed format too...
With all that in mind, using "borg-1.2" works for both Hetzner and rsync, so this works perfectly for me and my backups all work with this new config in place.