Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
Console Access only - No incoming connections
I am planning on creating some servers which don’t require incoming connections.
They are simply worker servers. They will connect to other systems themselves, download work, perform it and upload the result. So nothing needs to connect to that server to make it work.
As such I want to firewall the server so that incoming connections are entirely blocked. My original plan was to leave SSH 22 open on the private network so I could connect to the server for updates, and maintenance, etc.
However would Console Access be more appropriate than leaving the SSH port open?
The downside to Console Access is having to use a password versus using an SSH key, but surely using Console Access is more secure, in that access is only via my control panel, and not exposed to any network access?
What would be the best strategy? Console Access only or leave SSH on private network?
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.×