Currently, Plesk allows configuring reverse proxies through the "Apache & Nginx" tab under "Additional nginx directives." While functional, this approach can be tedious and less intuitive, especially for users managing multiple servers or specific use cases. Adding a dedicated "Reverse Proxy" option during domain or subdomain setup would greatly enhance usability and streamline the process.

For instance, when creating a subdomain, users could choose "Reverse Proxy" as a hosting type, alongside options like "Web Hosting" or "Mail Hosting." This feature could include an intuitive configuration interface with settings such as:

Specifying the target server (e.g., local machine or external server).
Configuring the port (e.g., for game servers or web services).
Selecting the proxy type (e.g., game server reverse proxy, web reverse proxy).

Practical Benefits:

Simplifying Multi-Server Management:

For setups with multiple local servers running behind a single public IP, this feature would make it much easier to route subdomains to specific servers. For example, api.example.com could point to one server while files.example.com points to another, all configured seamlessly through the Plesk interface.

Game Server Support:

In scenarios where multiple game servers use the same port (e.g., 25565 for Minecraft), the reverse proxy feature could allow assigning subdomains to differentiate servers (e.g., server1.example.com and server2.example.com), making it easier to manage and configure them without complex manual setups.

Improved Efficiency and Usability:

By reducing the need to manually input directives and manage configuration files, this feature would save time and lower the barrier for less technically skilled users. It would also ensure a more consistent setup process, reducing errors and improving troubleshooting.

This addition would significantly enhance Plesk's usability, making it more practical for advanced server setups and modern hosting environments.