Skip to main content
Edge Proxy routes incoming traffic through Gcore’s DDoS mitigation infrastructure and assigns a protected IP address that clients connect to instead of the origin server. In the Gcore Customer Portal, navigate to Security → Edge Proxy → Protected servers and click Add server to open the four-step wizard.
Protected servers list showing existing servers and the Add server button
1

Enter server details

Enter a Server name and the Origin address — IPv4 or a domain name.
Step 1 showing Server name and Origin address fields
Click Continue.
2

Select applications

Each card is a DDoS filtering profile for a specific application type — Minecraft Protection, Counter-Strike variants, FiveM, Generic TCP Server, General UDP Countermeasure, and others.Use Type to search to filter the list. Select every profile that matches traffic on this server.The plan usage counter in the wizard header tracks how many ports are consumed across all servers against the plan limit.
Step 2 showing application cards and search
Click Continue.
3

Set ports

For each selected application, enter the listening port (1–65535) and select TCP or UDP. Click Add port to add more ports.Click Advanced to set Proxy protocol on each port.Proxy protocol prepends a header so the origin sees the original client IP instead of the Edge Proxy address. It is available in two versions: V1 supports TCP connections and V2 supports both TCP and UDP and can carry additional connection metadata, so the origin application must support the selected version — otherwise, leave the setting Off.
Step 3 showing port, protocol, and Proxy protocol settings
Click Continue.
4

Review and deploy

Click Deploy. Activation takes about 3 minutes, after which the server appears in the Protected servers list with Online status and an assigned proxy IP.
Step 4 showing a summary of the configuration before deployment
Copy the proxy IP and update the client to connect to it instead of the origin server address. If clients use a domain name, update its A record to point to the proxy IP.
If the application is unreachable after activation, most activation issues trace back to firewall rules blocking Gcore edge IPs, incomplete DNS propagation, or a protocol mismatch.