Use this guide if your site is not loading during or shortly after initial Pressidium EDGE setup.

This article focuses on issues that appear during or shortly after initial EDGE setup, such as DNS records not resolving, SSL still provisioning, the WordPress integration not being connected, or setup steps being incomplete.

If the site was already working through EDGE and became unavailable later, visit Site Not Accessible.

Quick diagnosis

Before detailed troubleshooting, check these common causes:

  1. DNS has not propagated yet: Recent DNS changes can take time to update across DNS resolvers and caches.
  2. DNS records are incorrect: The domain may still point to the previous host or to the wrong record value.
  3. SSL is not active yet: SSL may still be provisioning, especially if DNS was changed recently.
  4. The WordPress integration is not connected: The Pressidium Performance Plugin may not be installed, active, or connected to EDGE.
  5. Setup is incomplete: The site, domain, origin, SSL, or DNS configuration may need review in the Pressidium Dashboard.

Common symptoms

Site is completely unreachable

What you see:

  • Browser shows “This site can’t be reached”
  • Browser shows DNS_PROBE_FINISHED_NXDOMAIN
  • Browser shows a connection timeout
  • The domain does not resolve

Likely causes:

  • DNS records are missing
  • DNS records are incorrect
  • DNS changes have not propagated yet
  • The domain is pointing to the wrong destination

Site loads but shows errors

What you see:

  • Site partially loads
  • Browser shows SSL warnings
  • Browser shows mixed content warnings
  • Images, CSS, JavaScript, or fonts do not load
  • Some pages work and others do not

Likely causes:

  • SSL is not active yet
  • SSL does not cover the exact hostname
  • Mixed content exists in WordPress content or theme files
  • Cache or optimization settings need review
  • EDGE setup is incomplete

Site redirects or shows wrong content

What you see:

  • Site redirects unexpectedly
  • The wrong domain appears in the browser
  • Old content appears
  • Content from the previous host appears
  • The root domain works but www does not, or the other way around

Likely causes:

  • DNS still points to the old host
  • Only one hostname is configured correctly
  • Redirect settings are incorrect
  • Cache is serving old content
  • WordPress Address or Site Address is incorrect

Step-by-step troubleshooting

Step 1: Verify DNS configuration

Start by confirming that DNS points to the values shown in the Pressidium Dashboard.

Check DNS records

  1. Open your DNS provider.
  2. Find the DNS zone for the affected domain.
  3. Check the records for the root domain and www version, if both are used.
  4. Confirm that each record type and value matches the DNS values shown in Pressidium EDGE.
  5. Remove old or conflicting records for the same hostname unless the Dashboard specifically instructs you to keep them.

Use only the DNS values shown in the Pressidium Dashboard as the source of truth for your setup.

Test DNS resolution

For an A record, run:

dig example.com A

Or:

nslookup -type=A example.com

For a CNAME record, run:

dig www.example.com CNAME

The result should match the expected EDGE value shown in the Pressidium Dashboard.

Check DNS propagation

If DNS was changed recently, compare results from multiple resolvers or locations.

You can use:

  • dig
  • nslookup
  • Online DNS propagation checkers
  • Public resolvers such as 1.1.1.1 or 8.8.8.8

If some locations show the new value and others show the old value, propagation may still be in progress.

See DNS Propagation Delays for more details.

Common DNS issues

  • Wrong DNS records: Records still point to the old hosting provider.
  • Incomplete DNS setup: Only the root domain or only www is configured.
  • Conflicting records: More than one record type exists for the same hostname.
  • Wrong DNS provider: Records were edited somewhere other than the active DNS provider.
  • High TTL: Old values may remain cached longer than expected.

See DNS Configuration Problems for detailed DNS troubleshooting.

Step 2: Check SSL certificate status

After DNS points to EDGE, check whether SSL is active for the affected hostname.

Verify SSL is active

  1. Open the site in the Pressidium Dashboard.
  2. Check the domain or SSL status for the affected hostname.
  3. Confirm whether SSL is active, pending, or showing an error.
  4. Open the site using https://.
  5. Check whether the browser shows an SSL warning.

If SSL is pending, confirm that DNS points to EDGE and that enough time has passed for DNS propagation.

If SSL shows an error, review the domain, DNS records, and SSL configuration.

See SSL Certificate Not Activating if SSL remains pending or fails to activate.

See SSL Troubleshooting for browser warnings, certificate mismatch errors, mixed content, and HTTPS issues.

Step 3: Verify the WordPress integration

The Pressidium Performance Plugin connects your WordPress site to Pressidium EDGE and enables integration features such as cache management and sync.

Check plugin status

  1. Log in to WordPress admin.
  2. Go to Plugins.
  3. Confirm that Pressidium Performance is installed and active.
  4. Check for plugin errors or update notices.
  5. Open the Performance menu in the WordPress admin sidebar.
  6. Confirm that the plugin is connected to EDGE, if the site uses the WordPress integration.

Reconnect the plugin if needed

If the plugin is not connected:

  1. Open the site setup or WordPress integration area in the Pressidium Dashboard.
  2. Copy the Client ID and Client Secret shown for the site.
  3. Open the Performance plugin settings in WordPress.
  4. Paste the Client ID and Client Secret into the plugin settings.
  5. Save the plugin settings.
  6. Return to the Pressidium Dashboard and finish or recheck the setup.

If the Client Secret was lost or exposed, re-issue the Client Secret in the Pressidium Dashboard and update the plugin settings with the new value.

See Connect the Performance Plugin to EDGE for connection steps.

See WordPress integration not connected if the integration remains disconnected.

Step 4: Check site status in the Dashboard

Open the site in the Pressidium Dashboard and review the setup state.

Check:

  • The site exists in the correct EDGE account.
  • The primary domain is correct.
  • The affected hostname is attached to the correct site.
  • Domain verification is complete or pending for a clear reason.
  • DNS setup does not show unresolved issues.
  • SSL is active or provisioning as expected.
  • The origin hostname or IP address is correct.
  • Redirect behavior is correct.
  • Any warnings or errors in the Dashboard have been reviewed.

A successful setup should show that the domain is verified or connected, the site loads over HTTPS, public pages load correctly, and the WordPress integration is connected if you completed that step.

See Verify Your Setup for the full post-setup checklist.

Step 5: Test site functionality

After DNS, SSL, Dashboard configuration, and WordPress integration have been checked, test the site from the browser.

Basic tests

  1. Homepage loads: Visit the domain and confirm the homepage loads without errors.
  2. HTTPS works: Visit the site using https:// and confirm there are no SSL warnings.
  3. Resources load: Check that images, CSS, JavaScript, fonts, and embedded resources load correctly.
  4. Important pages work: Test login, checkout, forms, account pages, membership pages, LMS pages, or other dynamic pages.
  5. WordPress admin works: Confirm that wp-admin remains accessible.
  6. Requests reach EDGE: Check response headers, EDGE traffic data, cache information, or site analytics to confirm requests are reaching the EDGE service.

You can also run:

curl -I https://example.com

Use the response headers and HTTP status code to confirm whether the site returns a valid response.

Specific error messages

“This site can’t be reached”

Possible causes:

  • DNS is missing
  • DNS has not propagated
  • Domain points to the wrong destination
  • Site is not configured for the domain

What to do:

  • Verify DNS configuration.
  • Check active nameservers.
  • Confirm the record value matches the Dashboard.
  • Check DNS propagation.
  • Review DNS Configuration Problems.

DNS_PROBE_FINISHED_NXDOMAIN

Possible causes:

  • The domain does not resolve
  • The hostname is incorrect
  • DNS records are missing
  • DNS records were added at the wrong DNS provider

What to do:

  • Confirm the domain name is typed correctly.
  • Confirm the DNS record exists.
  • Confirm you edited records at the active DNS provider.
  • Check nameservers.
  • Contact your DNS provider if records are not being served.

ERR_CONNECTION_REFUSED

Possible causes:

  • DNS points to the wrong destination
  • The origin is refusing connections
  • EDGE is not configured for the domain
  • A firewall or network rule is blocking the connection

What to do:

  • Verify DNS points to EDGE.
  • Confirm the site is added in the Pressidium Dashboard.
  • Review origin configuration.
  • Test from another network.
  • Contact Support if the issue persists.

SSL certificate warnings

Possible causes:

  • SSL is not active yet
  • Certificate does not cover the exact hostname
  • DNS still points to the wrong destination
  • Browser cache shows old certificate data
  • Custom certificate data is incorrect

What to do:

  • Check SSL status in the Dashboard.
  • Confirm DNS points to EDGE.
  • Confirm the certificate covers the exact hostname.
  • Test in a private browser window.
  • Review SSL Troubleshooting.

Mixed content warnings

Possible causes:

  • HTTPS pages load resources over http://
  • WordPress Address or Site Address still uses HTTP
  • Theme, plugin, or content includes hardcoded HTTP URLs
  • Cached pages or assets include old URLs

What to do:

  • Check browser developer tools for mixed content warnings.
  • Update WordPress Address and Site Address to HTTPS if the site should run fully over HTTPS.
  • Replace hardcoded HTTP URLs with HTTPS where appropriate.
  • Clear page, plugin, browser, and EDGE cache.
  • Retest the affected pages.

EDGE does not guarantee that all hardcoded HTTP URLs in WordPress content, themes, or plugins will be automatically rewritten. Fix mixed content at the WordPress content, theme, plugin, or database level where needed.

Troubleshooting by scenario

Site worked before adding EDGE

If the site worked before you added EDGE:

  1. Check DNS changes: Confirm the DNS records were changed correctly.
  2. Remove old conflicting records: Remove old A, AAAA, or CNAME records for the same hostname unless the Dashboard specifically instructs otherwise.
  3. Check propagation: DNS changes can take time to update across resolvers.
  4. Check SSL status: SSL may still be provisioning if DNS was updated recently.
  5. Review setup steps: Confirm the site, origin, domain, DNS, SSL, and WordPress integration steps are complete.
  6. Check redirects: Confirm the site is not redirecting to an old or unconfigured hostname.

New site setup

If this is a new EDGE setup:

  1. Confirm the site has been added to the Pressidium Dashboard.
  2. Confirm the domain is correct.
  3. Confirm the origin hostname or IP address is correct.
  4. Complete domain verification.
  5. Add the DNS records shown in the Dashboard.
  6. Wait for DNS propagation if changes were recent.
  7. Confirm SSL is active or provisioning.
  8. Install, activate, and connect the Pressidium Performance Plugin if required.
  9. Run the setup verification checklist.

See Adding a WordPress Site to EDGE for the full setup flow.

Site loads but is slow

If the site loads but performance is poor:

  1. Check cache behavior: Cache may not be warm immediately after setup.
  2. Test key pages: Test the homepage, important landing pages, checkout, login, account, LMS, or membership pages.
  3. Check whether requests reach EDGE: Review response headers, cache information, traffic data, or analytics.
  4. Review origin performance: Slow uncached requests may still depend on the origin.
  5. Review plugin settings: Check whether optimization settings were enabled and whether they affected layout or functionality.

See Site Loading Slowly for performance troubleshooting.

See Cache Not Working if cache behavior does not look correct.

Quick fixes

Clear browser and local DNS cache

  1. Clear browser cache and cookies.
  2. Test in a private or incognito window.
  3. Test in another browser.
  4. Clear local DNS cache if your device may be using stale DNS.

On Windows, open Command Prompt as Administrator and run:

ipconfig /flushdns

On macOS, open Terminal and run:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

On Linux systems using systemd-resolved, run:

sudo systemd-resolve --flush-caches

Or, on newer systems:

resolvectl flush-caches

Clearing local DNS cache only affects your device. It does not speed up global DNS propagation.

Purge EDGE cache

If the site loads but shows old content or old assets:

  1. Open the site in the Pressidium Dashboard.
  2. Go to the site cache or performance controls.
  3. Use the available cache purge action for the site.
  4. Retest the affected page in a private browser window.
  5. Confirm that the expected content is served.

Also clear any WordPress page cache, plugin cache, browser cache, or origin cache that may be involved.

Reconnect the WordPress integration

If cache changes are not syncing or the plugin shows as disconnected:

  1. Confirm the Pressidium Performance Plugin is installed and active.
  2. Open the plugin settings from the Performance menu in WordPress.
  3. Confirm the Client ID and Client Secret are saved correctly.
  4. Re-issue the Client Secret in the Pressidium Dashboard if needed.
  5. Save the new credentials in the plugin settings.
  6. Confirm the plugin shows as connected.

Verify DNS again

If the site is still not loading:

  1. Check DNS records at the active DNS provider.
  2. Confirm the record type is correct.
  3. Confirm the record value matches the Dashboard.
  4. Confirm there are no duplicate or conflicting records.
  5. Check DNS from multiple resolvers.
  6. Wait for propagation if the records were changed recently.

Diagnostic information to collect

Before contacting Support, collect:

Site information

  • Domain name
  • Affected hostname, such as root domain or www
  • Site status in the Dashboard
  • Any Dashboard warnings or errors

DNS information

  • DNS provider
  • Active nameservers
  • DNS record types and values
  • Approximate time DNS changes were made
  • DNS lookup results
  • DNS propagation results, if available

SSL information

  • SSL status in the Dashboard
  • Browser SSL warning, if shown
  • Certificate hostname
  • Certificate expiration date, if relevant
  • Whether the issue affects HTTP, HTTPS, or both

WordPress integration information

  • WordPress version
  • Pressidium Performance Plugin version
  • Whether the plugin is installed and active
  • Whether the plugin shows as connected
  • Any plugin errors

Browser and network information

  • Browser and version
  • Error messages shown
  • Screenshots of errors
  • Whether the issue occurs in a private window
  • Whether the issue occurs from another network or device
  • Whether the issue is intermittent or constant

Troubleshooting steps

  • What you already checked
  • Changes you made
  • Test results
  • When the issue started
  • Whether the site worked before setup

Prevention tips

Before setup

  • Take a backup before making major changes.
  • Record the current DNS records before editing them.
  • Confirm which DNS provider is active.
  • Plan DNS changes for a low-traffic period when possible.
  • Lower TTL in advance if your DNS provider allows it.

During setup

  • Follow the setup steps in order.
  • Use the exact DNS values shown in the Pressidium Dashboard.
  • Do not add multiple DNS options for the same hostname unless instructed.
  • Complete domain verification before routing live traffic when possible.
  • Keep the Client Secret secure if you connect the WordPress integration.

After setup

  • Monitor the site during the first 24 to 48 hours.
  • Test the root domain and www version.
  • Test HTTP and HTTPS.
  • Test WordPress admin and important dynamic pages.
  • Check SSL status after DNS has propagated.
  • Keep a record of DNS, SSL, origin, and plugin configuration.

Troubleshooting checklist

  • Confirmed the site exists in the correct EDGE account
  • Confirmed the primary domain is correct
  • Confirmed the origin hostname or IP address is correct
  • Confirmed DNS records match the Dashboard
  • Checked active nameservers
  • Removed old or conflicting DNS records
  • Checked DNS propagation
  • Checked SSL status
  • Tested HTTPS
  • Checked for mixed content warnings
  • Confirmed the Pressidium Performance Plugin is installed and active
  • Confirmed the WordPress integration is connected, if required
  • Tested the site in a private browser window
  • Tested from another browser, device, or network
  • Tested important pages and WordPress admin
  • Cleared browser, DNS, plugin, and EDGE cache where relevant
  • Collected diagnostic information for Support if the issue persists

When to contact Support

Contact Pressidium Support if:

  • The site still does not load after DNS has propagated
  • DNS and SSL appear correct but the site is not working
  • SSL remains pending or shows an error
  • Domain verification remains pending after the DNS record is correct
  • The origin cannot be reached
  • The Pressidium Performance Plugin cannot connect to EDGE
  • The Dashboard shows setup errors you cannot resolve
  • The issue is urgent or affects a live production site

When contacting Support, include:

  • Domain name
  • Affected hostname
  • Site status from the Dashboard
  • DNS provider
  • Current DNS records
  • Approximate time DNS changes were made
  • SSL status
  • Plugin connection status, if relevant
  • Error messages
  • Screenshots
  • Troubleshooting steps already taken
  • Urgency level

Where to go next