After deploying this server using the Standalone AMI, you will get a fully functional HTTP/SOCKS5 Proxy Server with a single IP address used for both the Endpoint and Outbound traffic.
br> If you want to run the Proxy Server with separate IP addresses for the Endpoint and the Outbound connection - where the Endpoint IP is used by clients to connect to the Proxy Server, and the Outbound IP is the address under which client traffic appears on the internet - you can deploy this server using a CloudFormation template. This configuration allows you, for example, to change or rotate the outbound IP address later simply by replacing the second Elastic IP, without needing to update the client configuration and without restarting the server.
Usage instructions:
1. Launch the server.
2. If the Elastic IP was assigned to a running instance, the instance must be restarted.
Linux username: admin
After launching the server, it is immediately ready to work; no additional settings are required.
At the first launch of the server, a user named "testuser" with a randomly generated password is created in the user database.
User management Web Panel:
https://[Public IP address]
(use "administrator" as username and your instance ID as password)
When accessing the Control Panel using HTTPS, your web browser may display a warning about potential risks due to the use of IP address in the URL. In this case, you should proceed and accept the risks, as our goal is to encrypt traffic, and there is no reason to worry about using IP address in a web browser.
Use the following settings on a client side:
ADDITIONAL INFO
phpMyAdmin (database management):
https://[Public IP address]/phpmyadmin/
Default username for phpMyAdmin: "administrator", initial password is your instance ID. By default, access to phpMyAdmin is restricted in "/usr/share/phpmyadmin/.htaccess"
Access to the Database via Port 3306:
By default, for security reasons, access to the server through port 3306 is closed. However, the database includes a user named "remote," who has read and write access to the database if this port is opened. This can be useful for managing users remotely via MySQL queries.
Username: "remote", password is your instance ID, database: "radius", tables: "radcheck" - list of users, "radusergroup" - access status for users (Enabled/Disabled).
