> ## Documentation Index
> Fetch the complete documentation index at: https://docs.preprod.world/llms.txt
> Use this file to discover all available pages before exploring further.

# 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

<AccordionGroup>
  <Accordion title="Protected IP assignment">
    No. Gcore assigns a protected IP from the Anycast pool automatically.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="Editing proxy settings">
    Yes. **Server name**, **Origin address**, applications, ports, and **Proxy protocol** can be changed from **Edit protection**.
  </Accordion>

  <Accordion title="Supported application types">
    Any TCP or UDP application can be protected with a profile from [Supported applications](/edge-proxy/supported-applications). If the exact profile is not in that set, use **Generic TCP Server** or **General UDP Countermeasure**. An incorrect profile may cause legitimate traffic to be blocked during an attack.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="Setup duration">
    Activation typically takes about 3 minutes after clicking **Deploy**.
  </Accordion>
</AccordionGroup>

## 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

<AccordionGroup>
  <Accordion title="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`)
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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](#contact-gcore-support).
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## Contact Gcore support

If the issue persists, reach [Gcore support](https://support.gcore.com).

<Frame>
  <img src="https://mintcdn.com/gcore-docs/hMSfBjm_bKfPx0TA/images/docs/edge-proxy/faqs-and-troubleshooting/faqs-and-troubleshooting-image1.png?fit=max&auto=format&n=hMSfBjm_bKfPx0TA&q=85&s=4a00128d0f3174e59c785f7785c0f64b" alt="Gcore Help Center with Submit a request button highlighted in the top navigation" width="1024" height="375" data-path="images/docs/edge-proxy/faqs-and-troubleshooting/faqs-and-troubleshooting-image1.png" />
</Frame>

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