Getting Started

Deployment Deployment - Diagnose Migrations Staging

Site Management

Backups Client Reporting Passwords Plugin Automation Plugin Management - Global Plugins & Themes - Diagnose Plugins & Themes - General Plugins & Themes - Git Plugins & Themes - Logs Must Install White Label WordPress Updates

Caching & Performance

Caching Caching - Blogs/Articles Caching - Diagnose Caching - Git Caching - WooCommerce Redis Optimize & Scale

Security

Security Security - Firewall

SMTP, CDN & DNS

SMTP SendGrid CDN CDN - AWS CDN - Cloudflare CDN - Diagnose Domains & DNS

Server & Tools

Analytics & Logs CRON Jobs Database Debug Tool Git Monitoring PHP Settings Redirects SEO Tools Server Errors sFTP SSL

Staq Billing

Staq Billing > Account Staq Billing > Client Staq Billing > Setup

Media

Media Media - Diagnose Media - Optimize

Accounts & Billing

Accounts & Billing

General

WordPress Hosting Website Diagnose Troubleshoot - Other

403 Server Error


On this page

    Encountering a 403 Server Error is mostly like due to:

    • a production website still has dev links that no longer points since it’s now on production
    • an SSL generation or renewal issue.

    Dev link appearing in a production website

    Firstly, check the URL or link that has the 403 Forbidden error. Does it look like a production URL or is it the dev (or development) or staging link?

    If that is the case, you’ll have to do a search/replace inside the database to correct this. You can do a search and replace inside the database via 2 methods either via the Staq dashboard or inside the WordPress backend. Check out this guide on how to do a search/replace inside the WordPress database.

     

    DNS configuration causing SSL to fail to generate or renew

    SSL: Understanding the Cause

    SSL certificate issues on Staq are primarily related to the following:

    • DNS Misconfiguration: A records not pointing to Staq’s system.
    • DNS Propagation: Delays in DNS updates after taking a website live i.e. the TTL on your DNS is set high.
    • Multiple A Records: Duplicate or conflicting entries for the same domain.
    • Cloudflare Proxy: Interference with SSL authentication when proxy status is enabled.
    • Too Many SSL Generation Attempts: Excessive failed attempts can result in a temporary ban from Let’s Encrypt.

    Diagnosing SSL Issues

    Step 1: Verify DNS Configuration

    1. Go to the website’s Staq Panel and click Domains.
    2. Check if the domains have a warning symbol, which indicates a mismatch or misconfiguration.
    3. Use a tool like MX Toolbox to perform a DNS lookup for your domain and verify that the A records match the IP address provided in the Staq Panel.

    Example: For domains such as www.example.com and example.com, ensure that both point to the correct Staq IP address.

    Step 2: Check for Duplicate A Records

    If multiple A records exist for the same domain (e.g., pointing to different IP addresses), delete the unnecessary entries. Duplicate records will cause SSL validation to fail.

    Step 3: Check for AAAA Records

    Inside Staq Panel > Domains, if you have i.e. the root domain and www domain setup, make sure that you do not have AAAA records that correspond to the root or www domains inside your DNS. If you see this, delete the AAAA records since they will not allow the SSL to generate.

    Step 4: Cloudflare Proxy

    If you’re using Cloudflare, ensure the proxy status for non-www and www records is disabled during SSL certificate creation or renewal. This allows Let’s Encrypt to verify the domain without interference.

    Disable Proxy in Cloudflare
    Alternatively, if you wish to take advantage of our Staq to Cloudflare API integration, see this guide so that you can keep Cloudflare proxy enabled. This will allow SSL creation and auto-renew to occur seamlessly.

    Resolving SSL Issues

    Step 1: DNS Propagation

    If DNS changes were recently made, wait for DNS propagation to complete. Once completed, ensure that all A records point to Staq’s system.

    Step 2: Regenerate SSL Certificate

    After resolving DNS issues, navigate to the SSL section in the Staq Panel and click Generate SSL Certificate:

    Generate SSL Certificate

    Step 3: Bring Services Back to Staq

    • If you manage your DNS through a third-party provider, update the A records to point to Staq’s IP addresses (found in the Staq Panel under Domains).
    • If you wish to move your DNS management to Staq, retrieve the NS records from the Staq Panel under DNS Zone and update them in your domain registrar’s settings.

    Additional Considerations

    Conclusion

    Ensuring all your links are correct inside the database will remove the 403 error. Alternatively, if it was a DNS configuration, resolving SSL certificate issues often comes down to ensuring proper DNS configuration and addressing factors like proxy settings and propagation delays. Follow the steps outlined in this guide to diagnose and resolve issues effectively. If you encounter persistent problems, reach out to Staq Support for further assistance.

    Need some help?

    We all do sometimes. Please reach out to our support team by dropping us a support ticket. We will respond fast.