Skip to main content
This guide provides the answers to common questions and solutions to typical issues when using Edge Proxy.

​
General questions

​
What is Edge Proxy?

Edge Proxy is a DDoS protection service that runs on the Gcore CDN edge network. It filters incoming traffic before forwarding it to your origin server.

​
What types of applications can I protect?

You can protect any TCP or UDP application, including:
  • Game servers (for example, Counter-Strike, Minecraft, FiveM)
  • Web servers and APIs
  • DNS servers
  • Voice servers (for example, TeamSpeak)
  • Custom TCP or UDP applications

​
How long does setup take?

The setup process typically takes less than five minutes. After you click Start Protecting, the proxy is provisioned in about 20 seconds.

​
Does Edge Proxy add latency?

Edge Proxy is designed to add minimal latency. Traffic is routed to the nearest Point of Presence (PoP), which may improve routing efficiency in some cases.

​
Can I protect multiple applications?

Yes. You can create multiple proxy rules. Several rules can share the same protected IP address.

​
Do I need my own IP range or AS?

No. Gcore assigns a protected Anycast IP address automatically.

​
Setup and configuration

​
Can I choose the protected IP address?

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

​
Can I reuse the same origin IP?

Yes. You can create multiple proxy rules that use the same origin IP with different ports, protocols, or application types.

​
What happens if I select the wrong application type?

Incorrect configuration may cause legitimate traffic to be blocked during an attack. To resolve this:
  • Delete the proxy
  • Create a new one with the correct application type

​
What if my application is not listed?

If your application is not available in the list:
  • Select a matching engine or protocol (for example, Unity, Unreal, RakNet)
  • Use TCP protection for TCP-based applications
  • Contact support if you are unsure

​
Can I edit an existing proxy?

No. To change the configuration, delete the proxy and create a new one. A new protected IP may be assigned.

​
DNS and connectivity

​
Do I need to update DNS?

Yes, if your application uses a domain name.
  • Update your A or AAAA record to the protected IP
  • If using direct IP connections, share the new IP:PORT with users

​
How long does DNS propagation take?

Propagation depends on your DNS TTL and can take from a few minutes to 48 hours. To reduce downtime:
  • Lower the TTL before making changes
  • Update the record
  • Increase the TTL after propagation completes

​
What happens to existing connections?

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

​
Troubleshooting

​
Clients cannot connect to the protected IP

Symptoms: Users cannot connect to your application using the protected IP and port. Steps to resolve:
  1. Verify the protected IP and port
    • Check the values in the Customer Portal
    • Ensure you use the full IP:PORT pair
  2. Check your origin server
    • Confirm the application is running
    • Verify it listens on the correct port and protocol
  3. Verify protocol configuration
    • Ensure TCP or UDP matches your application
  4. Check firewall rules
    • Allow traffic from Gcore edge IPs
    • Do not restrict access to old client IPs only
  5. Check DNS propagation
    • Verify DNS resolution using tools like dig or nslookup

​
High latency through the proxy

Symptoms: Users experience increased latency or lag. Steps to resolve:
  1. Compare latency
    • Test direct connection vs protected IP
  2. Check origin location
    • Ensure your origin is close to Gcore PoPs
  3. Verify application type
    • Incorrect settings may cause retransmissions

​
Legitimate traffic is blocked during an attack

Symptoms: Real users cannot connect or are disconnected during an attack. Steps to resolve:
  1. Verify application type
    • Use the correct countermeasure for your application
  2. Contact Gcore support

​
Proxy is active but no traffic flows

Symptoms: The proxy shows as active, but no traffic reaches your application. Steps to resolve:
  1. Verify client configuration
    • Ensure clients use the protected IP:PORT
  2. Check the port
    • Confirm clients connect to the correct protected port
  3. Test from another network
    • Avoid testing from the same network as the origin

​
Contact Gcore support

If the issue persists, contact Gcore support via the support portal. Use the Submit a request form to create a support ticket, and provide:
  • Account ID
  • Proxy name and protected IP
  • Description of the issue
  • Steps already taken
  • Screenshots or logs, if available