I have a droplet which is a secondary server that my main server calls out to.
For security reasons I would like this droplet to be not accessible via it’s public IP. Though I realized I still might need to allow it, since I still want to be able to SSH into it.
It would also be nice if there was some way I could still access it publicly for testing on a local machine, but it would be secured against attacks (like maybe I can somehow use ssh for my http request? or something?)
Let me know any ideas.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
I would recommend not closing all outbound access since you might end up locking yourself from the droplet.
As already mentioned you can close all ports, and only allow the traffic to port 22 from your personal IP address.
One option would be to use a firewall like
csfto close down all ports except port 22.
Alternatively, you could also use a managed Cloud Firewall instead:
You can close all ports, and only allow the traffic to port 22 from your personal IP address.
Hope that this helps!