Hello, I am a new user. Hello very warmly and I am weak in English 😛
I am writing this post and also it is related to the topic
I am in favor of implementing an internal terminal on the customer panel because of:
- The ability to restrict to SSH via IP address (dedicated IP or VPN) via port 22 from outside via Firewall, so that there is no attack from outside and only for administrator.
- Clients can access the internal terminal from the container at the panel level and not interfere with other container and system environment.
- It can be set to manually enable a given client to access the internal terminal by request to support.
There is one server panel that are based applications on advanced containers. The team has introduced an internal terminal that can only access a given container through the panel and it works without a problem and we don't have to have external port 22 open all the time for SSH.
I am the type of administrator that I want to have limited access to SSH via external port 22 for me or those authorized via VPN or through a private network (Host Bastion). This way I had it implemented on servers with an external firewall and no attack and I had login added by key and without password for more security.
I plan to test a Teleport or similar system to make things easier with server management.
I am a new user of your panel and I am very happy with how it works. I am currently in the process of testing, so there are many things I don't know yet how it works.
I have a question, is it possible to connect between clusters to the main panel through a private network? Because I want to completely restrict SSH access from outside port 22. Or introduce the option to automatically enter the server addresses that are used by a person to all the servers of his own in the Firewall function, which is scheduled for March 2024. Seemingly a very strange solution, but this at the same time increases the security of the server.