You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
DigitalOcean
I want to change ssh port of the newly created droplet from the account and node template. We have two main methods to do it.
#cloud-config
#cloud-config
rancher:
ssh:
port: 6969
This method working fine on the web browser while manually creating a droplet. I was failed to supply it in NodeTemplate, please guide me if possible.
/bin/sh cmd
#!/bin/sh
ros config set rancher.ssh.port 6969
The second method does change the port from Nodetemplate and web browser but manually restarts required. There were some similar issues in the past but I think this new.
/bin/sh cmd
#!/bin/sh
ros config set rancher.ssh.port 6969 sudo reboot
adding reboot screw up everthing.
please help me find some solution. I have created almost 50 droplets to test all different scenarios. 😵
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
RancherOS Version: (ros os version)
Operating System: RancherOS v1.5.6
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
DigitalOcean
I want to change ssh port of the newly created droplet from the account and node template. We have two main methods to do it.
This method working fine on the web browser while manually creating a droplet. I was failed to supply it in NodeTemplate, please guide me if possible.
The second method does change the port from Nodetemplate and web browser but manually restarts required. There were some similar issues in the past but I think this new.
please help me find some solution. I have created almost 50 droplets to test all different scenarios. 😵
The text was updated successfully, but these errors were encountered: