Rsync - Connection refused on different port than 22

Jap0 · Jun 9th 2017

Hi everybody.
I've configured 'rsync' task with public key authentication on standard 22 ssh port and everything seems to be fine, I've could transfer files. But when I've changed it to different port i.e. 22445, saved and applied settings I've got this message:

Code

Please wait, syncing <user@myserverip:/var/www/> to </srv/dev-disk-by-label-bpi-bck/www> ...


Identity added: /etc/ssh/openmediavault-ca9886376t-a0987-3eaw2-9j6w-09873h6srfcvxlk (rsa w/o comment)
OpenSSH_6.7p1 Raspbian-5+deb8u3, OpenSSL 1.0.1t 3 May 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to myserverip [myserverip] port 22.
debug1: connect to address myserverip port 22: Connection refused
ssh: connect to host myserverip port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.1]

Display More

I've already checked configuration in '/etc/openmediavault/config.xml' and this particular task shows 22445 port, the cron job in '/var/lib/openmediavault/cron.d' shows same mentioned 22445 port. What's wrong? How to fix that issue?
OMV version: 3.0.77 (Erasmus)

Thanks in advance.

Jap0 · Jun 10th 2017

To be more precise:

subzero79 · Jun 10th 2017

Just to discard. Try to delete the extra options that you have there -e "ssh -v" try again

Jap0 · Jun 10th 2017

No affect. I did that in purpose, it shows me what's wrong.

subzero79 · Jun 10th 2017

There must be a bug somewhere the mkconf script is not passing the port to the scheduled script.
You can inspect the rsync script located At

/var/lib/openmediavault/cron.d/

They start with rsync prefix and long uuid. Check the port is correct.
If is not correct I would try to delete and recreate the task.

Jap0 · Jun 10th 2017

I've been there already. The written port is correct, same as at GUI interface.

subzero79 · Jun 10th 2017

I think I know. Is applying a default option.

Can you post

cat /etc/ssh/ssh_config

Jap0 · Jun 10th 2017

Really, which one? Webserver or OMV?

Jap0 · Jun 10th 2017

I can connect with public key to my webserver without any problems on any port, but I can not do that with OMV and rsync

subzero79 · Jun 10th 2017

Omv. The log is from Omv the first one. Is where the task is initiating, right ?

Jap0 · Jun 10th 2017

In my opinion is useless, but there you go:

Code

Protocol 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
UsePrivilegeSeparation yes
KeyRegenerationInterval 3600
ServerKeyBits 2048
SyslogFacility AUTH
LogLevel INFO
LoginGraceTime 120
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
IgnoreRhosts yes
RhostsRSAAuthentication no
HostbasedAuthentication no
PermitEmptyPasswords no
ChallengeResponseAuthentication no
X11Forwarding no
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
UsePAM yes
#AllowGroups root ssh
AddressFamily any
Port 22445
PermitRootLogin no
AllowTcpForwarding no
Compression yes
PasswordAuthentication no
AuthorizedKeysFile ~/.ssh/authorized_keys ~/.ssh/authorized_keys2 /var/lib/openmediavault/ssh/authorized_keys/%u
PubkeyAuthentication yes

Display More

subzero79 · Jun 10th 2017

That's sshd_config, I wanted to see ssh_config

Jap0 · Jun 10th 2017

Code

# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.


# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.


# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.


Host *
# ForwardAgent no
# ForwardX11 no
# ForwardX11Trusted yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
SendEnv LANG LC_*
HashKnownHosts yes
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no

Display More

Jap0 · Jun 10th 2017

Any thoughts about different port than 22?

subzero79 · Jun 10th 2017

Are you familiar with .ssh/config? Do you use it?

subzero79 · Jun 10th 2017

that's the only way I can think is defaulting to 22 is because you might have an entry there with port defined.

Jap0 · Jun 10th 2017

What do you mean by that ? As far I can see you can not resolve my issue don't you?

Jap0 · Jun 10th 2017

My IP address is allowed to do anything with remote webserver, on any port!

subzero79 · Jun 10th 2017

Why don't you try to delete and recreate the job.

Jap0 · Jun 10th 2017

I did that few times. No effect.

Rsync - Connection refused on different port than 22

Participate now!

Tags