How to change the SSH Ports in WD MY Cloud and PR4100 for device to device conectivity

[khsajidali]

HI,
i want to configure a remote backup Job from MY Cloud Single Bay to My Cloud PR4100.
there is some restriction on ISP Side the TCP port is blocked from ISP side

how can i change the ssh connectivity on different port as port 22 is blocked from ISP level.

Regards,

[NAS_user]

There are probably other issues related to the router in your network as well.

You probably need to look into Port Forwarding options on your NAS. Essentially, this will “map” the port 22 on your local device to a different port on your router for communication to the outside world.

This would be the same procedure if you had a second device (say, another NAS) on your network that ALSO wanted port 22.

[khsajidali]

I checked with the ISP they told me that it is blocked at router level.

i did port forwarding on router to access WDPR through SSH over internet and its working fine, but my concern was that how can i tell the other WD My Cloud Device that remote WDPR SSH Port is changed.

whenever i try to configure remote backup on WD my Cloud its gives me error of RSYNC test.

[brannonb]

You need to edit sshd_config which is in /etc/ssh once you change the port you will need to restart the service
sudo service ssh reload

Feb 26 01:49:26 bob-linux systemd[1]: Reloading OpenBSD Secure Shell server.
Feb 26 01:49:26 bob-linux sshd[4693]: Received SIGHUP; restarting.
Feb 26 01:49:26 bob-linux systemd[1]: Reloaded OpenBSD Secure Shell server.
Feb 26 01:49:26 bob-linux sshd[4693]: Server listening on 0.0.0.0 port 224.
Feb 26 01:49:26 bob-linux sshd[4693]: Server listening on :: port 224.
Feb 26 01:49:26 bob-linux sshd[4693]: Server listening on 0.0.0.0 port 12345.
Feb 26 01:49:26 bob-linux sshd[4693]: Server listening on :: port 12345.
Feb 26 01:49:26 bob-linux sshd[4693]: Server listening on 0.0.0.0 port 222.
Feb 26 01:49:26 bob-linux sshd[4693]: Server listening on :: port 222.

[Tfl]

This may be useful.

Remote backup with nonstandard ports (not 873 and 22)

I’ve done some digging… here are the results. Server First you’d want to run the rsync daemon at the source side on a non-default port. You may run this directly rsync --daemon --port=10873 --config=/etc/rsyncd.conf Or use the WD wrappers to save a custom port in the config and then start the daemon rsyncom -e 1 -p somepassword -o 10873 -s rsyncom -x The password gets converted to base64 and is stored in /etc/rsyncd.secrets. The WD wrapper generates a configuration file with rsync module…

@brannonb you can’t sudo service in My Cloud software.
Edit the /etc/ssh/sshd_config and use kill -HUP $(pidof sshd) to reload.

[brannonb]

Wonder whats at line 1530 of main.c? I only have a DX4000 and MyCloudgen 1/ no pr4100

[Tfl]

My bad… linked the wrong post, but it’s all there in that topic.
Rsync bails with that error when it can’t connect over ssh.

[brannonb]

nohup it. problem solved

[prisoner24601]

This is not a permanent solution. If you update the sshd user’s password via the web UI then it will overwrite /etc/ssh/sshd_config and, in doing so, revert to less secure settings such as allowing passwords (over pubkey), allowing empty passwords, and resetting the default port to 22.

[brannonb]

passwd sshd and it saves to sshd_config? /face palm

[texasrebel]

I just ran into a similar problem. When you reboot the sshd_config file also reverts, and authorized_keys disappears. These are getting generated by a script somewhere. I think the whole environment is. Changes don’t persist.