FAQs and troubleshooting

Edge Proxy assignments are automated and require no IP management. Most issues appear during initial DNS migration or when the application type is misconfigured.

Frequently asked questions

Protected IP assignment

No. Gcore assigns a protected IP from the Anycast pool automatically.

Changing the origin address

Yes. Click Edit protection and update Origin address. The field accepts an IPv4 address or a domain name. The assigned proxy IP does not change.

Editing proxy settings

Yes. Server name, Origin address, applications, ports, and Proxy protocol can be changed from Edit protection.

Supported application types

Any TCP or UDP application can be protected. If the exact profile is not listed, select the closest matching engine or protocol, or use Generic TCP Server / General UDP Countermeasure. An incorrect application type may cause legitimate traffic to be blocked during an attack.

Multiple proxies and applications

Yes. Multiple proxies can use the same origin address with different ports or protocols, and several proxies can share the same protected IP address.

Setup duration

Activation typically takes about 3 minutes after clicking Deploy.

DNS migration

If clients connect using a domain name, update its A or AAAA record to point to the protected IP. Propagation depends on the DNS TTL and can take from a few minutes to 48 hours — lowering the TTL before the switch reduces downtime.

Existing connections to the origin continue until clients reconnect. New connections automatically use the protected IP.

Troubleshooting

Clients cannot connect

Verify that:

• clients connect to the protected IP:PORT, not the origin address
• the origin server is running and listening on the configured port
• the proxy protocol matches the application (TCP or UDP)
• firewall rules allow Gcore edge IPs
• DNS resolves to the protected IP (check with dig or nslookup)

High latency through the proxy

Compare latency on a direct connection vs the protected IP to isolate the source. If the origin server is far from Gcore PoPs, round-trip time increases. An incorrect application type can also cause retransmissions that appear as latency.

Legitimate traffic blocked during an attack

The most common cause is an incorrect application type — the countermeasure profile is not tuned for the application and flags legitimate packets as malicious. Reconfigure the proxy with the correct application type. If the issue persists, contact support.

Proxy active but no traffic reaches the application

Confirm clients are connecting to the protected IP:PORT and not the origin address directly. Test from a network other than the origin server’s, as local routing may bypass the proxy.

Contact Gcore support

If the issue persists, reach Gcore support.

Use the Submit a request form and provide:

• Account ID
• Proxy name and protected IP
• Description of the issue
• Steps already taken
• Screenshots or logs, if available