Hi,

On 25/06/2021 13:52, Patrik Dufresne wrote:
> Hello Adam,
> 
> When using the SSH proxy command this following message "Fatal Error:
> Truncated header string (problem probably originated remotely)" is
> generated by SSH. Usually this gets printed when the box doesn't allow ssh
> tunnel.
> 
> On the bastion server, You should review your /etc/ssh/sshd_config and make
> sure you have "AllowTcpForwarding yes".
> 
> After that, you may create a file in ~/.ssh/config
> 
> Host <hostname-behind-bastion>
>   ProxyCommand ssh -q -A -x <bastion-hostname> -W <ip-behind-bastion>:22
> 
> I invite you to test the configuration by calling ssh manually first, to
> make sure the ssh configuration is working, before trying to test it with
> rdiff-backup.

Adding to what Patrik wrote, if you can:

1. call `ssh -C hostname-behind-bastion rdiff-backup --server',
2. then type `q1234567` + Enter (only the 'q' and the length is important)
3. and the only output you get is `oquittingq.` (might look slightly
different with rdiff-backup 1.x)
4. and the command line comes back,
then you're probably good to go.

KR, Eric

> 
> 
> 
> On Fri, Jun 25, 2021 at 7:36 AM Frank Crawford <fr...@crawford.emu.id.au>
> wrote:
> 
>> Adam,
>>
>> This should work with any issue, but can you share the actual
>> ProxyCommand you are using.
>>
>> Also, what do you get if you log in yourself directly?
>>
>> And you may want to up the verbosity of rdiff-backup output (e.g. -v5)
>> to see what is being returned.
>>
>> Regards
>> Frank
>>
>> On Thu, 2021-06-24 at 17:59 +0100, Adam Weremczuk wrote:
>>> Hi all,
>>>
>>> I run old rdiff-backup 1.2.8 on a remote server and one local behind
>>> an
>>> ssh bastion.
>>>
>>> Direct backup over ssh work fine but I struggle hopping over
>>> intermediary box. All 3 run Debian.
>>>
>>> I've tried ProxyCommand with and without netcat but each time I'm
>>> getting:
>>>
>>> ---------------------------------------------------------------------
>>> ----------------------------------
>>>
>>> Fatal Error: Truncated header string (problem probably originated
>>> remotely)
>>>
>>> Couldn't start up the remote connection by executing
>>>
>>>      ssh -C backup rdiff-backup --server
>>>
>>> Remember that, under the default settings, rdiff-backup must be
>>> installed in the PATH on the remote system.  See the man page for
>>> more
>>> information on this.  This message may also be displayed if the
>>> remote
>>> version of rdiff-backup is quite different from the local version
>>> (1.2.8).
>>>
>>> ---------------------------------------------------------------------
>>> ----------------------------------
>>>
>>> I haven't been able to find any recipes online and I'm assuming it's
>>> feasible.
>>>
>>> Could anyone help?
>>>
>>> Regards,
>>> Adam
>>>
>>>
>>
> 
> 


Reply via email to