--- title: " Troubleshooting" date: "2025-10-03T08:09:54+00:00" summary: "Troubleshoot Error 400 in Acquia Edge Standard: Fix client-side issues, provisioning errors, and rule creation problems." image: type: "page" url: "/acquia-cloud-platform/add-ons/edge-standard/troubleshooting" id: "e5e87ca8-a850-4e2a-b736-dc59bfd9e182" --- Use this guide to identify and resolve common issues with Acquia Edge Standard, including access, domains, DNS, WAF rules, and metrics. Access and onboarding --------------------- ### Unable to access Edge Standard after purchase If you cannot access the Edge Standard console after your organization has purchased the product: 1. Verify that your Acquia Edge Standard entitlement is active on your subscription. You can check this in Acquia Cloud under your subscription details. 2. Confirm that your account type is compatible with Edge Standard. The following account types are not supported: * Acquia Cloud Site Factory (ACSF) * Acquia Cloud Platform (ACP) legacy * Source subscriptions * Multi-subscription or multi-organization accounts * Node.js subscriptions * FedRAMP-required subscriptions * Subscriptions with more than 10 custom domains or more than 3 applications 3. If your entitlement is active and your account type is compatible, contact Acquia Support for assistance. ### Edge Standard not visible in Acquia Cloud Platform UI If you have been invited to use Edge Standard but cannot see it in the Cloud Platform interface: 1. Verify that you accepted the invitation using the correct email address associated with your Acquia account. 2. Confirm that your account is linked to the correct subscription. 3. Check that your account type is compatible with Edge Standard. For the list of unsupported account types, visit the Unable to access Edge Standard after purchase section. 4. If the issue persists after verifying the above, contact Acquia Support with your account and subscription details. ### Permissions or access not working as expected Edge Standard uses a single administrator role (Org Admin) with full access to all Edge Standard features. Granular or custom role delegation is not currently available. If you believe your access is incorrectly restricted: 1. Verify that your account has the Org Admin role assigned. 2. Confirm that you are logged in with the correct Acquia ID. 3. If your role is correctly assigned and you still cannot access expected features, contact Acquia Support with your account and organization details. Domains and DNS --------------- ### Bare domains are not supported Edge Standard does not support bare domains, such as [example.com](http://example.com/). Only subdomains, such as [www.example.com](http://www.example.com/), are supported because Edge Standard provides a single hostname endpoint that requires a DNS CNAME record. If you need to use a bare domain, point it directly at your Acquia Cloud Platform balancer IP address and configure a redirect to your Edge Standard-protected subdomain in your application's .htaccess file. For more information, visit [Domain management](/acquia-cloud-platform/add-ons/edge-standard/domain-management "Domain management"). ### Domain status stuck on "Not Configured" If you have configured a domain in the Edge Standard console but the status shows "Not Configured": 1. Verify the CNAME record provided in the Edge Standard console. 2. Check the Status column in the Domains tab. The status must show Ready for DNS repointing before you update your DNS. 3. After you update your DNS, allow time for propagation. Use an external tool, such as dig or an online DNS checker, to confirm your CNAME record points to the correct Edge Standard endpoint. 4. After successful propagation, the status changes to Configured. ### Domain status stuck on "Ownership validation pending" If your domain status does not progress from "Ownership validation pending" to "Ready for DNS repointing": 1. Confirm you have created a DNS CNAME record in the following format: \_acme-challenge.www.example.com → www.example.com.prod.sites.acquia-horizon.co 2. Replace [www.example.com](http://www.example.com/) with your actual domain. 3. Allow up to 2 hours for the SSL certificate to be generated and the status to update. 4. If the status has not changed after 2 hours, contact Acquia Support. ### Domain and bandwidth limits If you have reached your domain or bandwidth entitlement limit: * A warning banner appears at the top of the console: "We have detected X domains beyond your current entitlements." * The Domain usage widget displays "Limit reached" with the overage count. * You can add new domains on your Cloud UI Domains page, but they will not be protected by Edge Standard until you purchase additional entitlements. * Traffic to existing protected domains is not affected. Contact your Account Manager to purchase additional domain entitlements or a higher bandwidth tier. ### Unable to remove a domain from Edge Standard Self-service domain deprovisioning is not currently available. If you need to remove a domain from Edge Standard, contact Acquia Support with the domain details and your request. WAF and security ---------------- ### WAF rules not working as expected If a custom security rule, such as an IP block or country block, is not having the intended effect: 1. Confirm the rule is enabled and saved. 2. Verify you are using the correct attribute and value. For example, use a two-letter country code like "US" for the United States. 3. Check the rule's priority. If another rule has higher priority, it may take precedence. 4. Review the Security Metrics dashboard to see if the rule is being triggered. 5. If the issue persists, contact Acquia Support. ### WAF false positives Edge Standard security controls inspect all traffic to your site, including authenticated editorial requests. In some cases, legitimate actions can trigger a security false positive. For example, saving content on a Drupal node edit page can trigger a false positive. Symptom: * Authenticated editors receive a 403 Bad Request - Denied error when saving or editing content. * Public site delivery is not affected. Cause: * Edge Standard WAF inspection flags the content of an editorial request as potentially malicious. * This is a false positive. The editor is submitting valid content, such as HTML, embedded code, or certain text patterns, that resembles patterns the WAF associates with attacks, such as cross-site scripting (XSS). Resolution: 1. Ask the affected editor to visit a public IP lookup service, such as [whatismyip.com](http://whatismyip.com/), from the same network they use to access the site, and note their public IP address. 2. Sign in to the Edge Standard console. 3. Navigate to Security > IP Access Control. 4. Add the editor's public IP address as a trusted IP. If the editor connects through a corporate network, add the network's public IP address or CIDR block instead. 5. Click Save. 6. Ask the editor to retry the action that was blocked. Note Some networks route traffic through different public IP addresses depending on the type of request. If the block persists after you add the initial IP address, ask the editor to verify their IP address using a different lookup service, then add the correct address to the trusted IP list. For more information, visit [IP access control](/acquia-cloud-platform/add-ons/edge-standard/ip-access-control "IP access control"). Escalation: If the issue persists after adding the trusted IP, contact Acquia Support with the following information: * Source IP address of the affected editor * Requested URL path. For example, /node/12345/edit. * Timestamp of the failed request in UTC * The specific action the editor attempted. For example, the editor saved a node edit page and received a 403 Bad Request error. * Relevant HTTP response headers, if available ### Planned vulnerability or security scans Before running a planned vulnerability or security scan against your Edge Standard-protected site, create an IP Access Control rule and add your scan IP addresses as trusted IPs. For instructions, visit [IP access control](/acquia-cloud-platform/add-ons/edge-standard/ip-access-control "IP access control"). Metrics ------- ### Metrics not updating or missing If the Performance Metrics or Security Metrics dashboards show no data or stale data: 1. Confirm that the date range selected in the filter dropdown matches the period you expect to see. 2. Allow up to 15 minutes for data processing. Check again after waiting. 3. If the issue persists for more than an hour, contact Acquia Support. Note Some variance between Edge Standard metrics and third-party analytics tools, such as Google Analytics, is expected due to differences in measurement points, bot filtering, CDN caching, and data aggregation timing. Related resources * [Domain management](/acquia-cloud-platform/add-ons/edge-standard/domain-management "Domain management") * [IP access control](/acquia-cloud-platform/add-ons/edge-standard/ip-access-control "IP access control") * [Edge Standard](/acquia-cloud-platform/add-ons/edge-standard/getting-started "Getting started") * [Acquia Support](/service-offerings/support "Support") * [Support User's Guide](/service-offerings/support-users-guide "Support Users Guide")