Oxygen 6.0 RC 1 Is Live

Oxygen 6.0 RC 1 Is Live

Learn More

Oxygen logo
Documentation

Troubleshooting Errors

If Oxygen Builder shows errors, fails to load, won’t save, or parts of your site stop rendering, this guide walks you through what to do next. Follow the steps in order and send the requested details to Oxygen Support so we can help you faster.

First Things First: Quick Checks

  • Clear caches: Purge any page/server/CDN cache (e.g., hosting cache, Cloudflare) and your browser cache. Disable caching temporarily while testing.
  • Update software: Ensure WordPress core, Oxygen Builder, and required add-ons are on the latest versions.
  • Test for plugin conflicts: Deactivate all non-Oxygen plugins. If the issue disappears, reactivate plugins one by one to find the culprit. This should be done on a staging site.
  • Check PHP version: Use a recent, supported PHP version per WordPress (for many sites, PHP 8.1–8.3 works well). Your host can switch this for you.
  • Permalinks: Visit Settings → Permalinks and click Save to flush rewrite rules.
  • Oxygen CSS/Assets: If styles look off, regenerate Oxygen’s CSS/asset cache from Oxygen settings. If in doubt, disable CSS caching while you test.

“Terminated” Loads, Previews, or Saves

If the Builder hangs, previews never finish loading, or saves don’t complete, your server may be terminating the request. This is usually due to timeouts or resource limits. Start here:

  • Try again with caches off (host/CDN/plugin) and after disabling other plugins.
  • Watch the browser console (Developer Tools → Console) for errors. Copy those messages to share with support.
  • Ask your host to check server error logs at the exact time of the failure (details below). Timeouts or permission blocks will appear there.

Server Timeouts & Resource Limits

Servers enforce hard limits on how long a process can run or how much memory it can use. Common settings that affect Oxygen:

  • Maximum Execution Time (PHP) (max_execution_time): If requests take longer than this limit, the server kills them. Your host can raise this.
  • Web server timeouts (e.g., Apache FcgidIOTimeout, NGINX fastcgi_read_timeout): If the server stops waiting for PHP, requests terminate. Hosts can increase these; ~90 seconds is a common baseline.
  • Memory limits (memory_limit): Low memory can crash requests. Ask for 512M or higher while troubleshooting.

If you still get terminated requests after you’ve disabled caches and other plugins, your host must adjust these limits or identify the exact failure in logs.

500/50x & Other Server Errors

When servers are misconfigured or overloaded, they return 3-digit error codes. The code helps you and your host narrow down the cause:

  • 500 – Internal Server Error: Often caused by PHP errors or conflicts. Your host should read the PHP and web server error logs to pinpoint the faulty code.
  • 503 – Service Unavailable: Frequently due to server overload or a host’s security layer temporarily blocking requests. Share the timestamp and your IP so your host can find a matching event.
  • 504 – Gateway Timeout: The upstream process took too long. Ask your host to review timeouts and performance.
  • 524 – A Timeout Occurred (Cloudflare): Origin server responded too slowly; the request hit Cloudflare’s 100-second default. Host needs to optimize or increase timeouts on origin (see Cloudflare documentation).
  • 403 – Forbidden: Often a security block (WAF, firewall, security plugin) on admin-ajax, REST, or Builder endpoints. See our dedicated guide: Fixing 403 Errors with Oxygen.

Important: Our support team can’t change hosting settings or access your server logs. Your hosting provider must locate and fix the underlying server issue. Once you have log entries from the exact time of the error, we can advise further.

Check Your Server’s Error Logs (What To Ask Your Host)

The fastest way to surface what’s wrong is to review your server’s error logs for entries that line up with the problem time. Our partner tool WP Debug Toolkit can collect those errors into a single dashboard and export a clean report for support. Use the discount code OXYDOC for a special offer.

If you can’t use this tool, contact your web host’s support team and ask them to provide the specific log entries from around the time you reproduced the issue. To make that possible, include:

  • Approximate time & timezone of the error (e.g., “September 27, 2025 at 2:41 PM America/Los_Angeles”). If unsure, reproduce the problem and note the exact time.
  • Your IP address (visit whatismyip.com to obtain it).
  • URL where the error appears and a screenshot of the error message.
  • Steps to reproduce (e.g., “Open Builder → Edit Header → Click Save”).

Ask your host to check all relevant logs:

  • PHP error log
  • Web server error log (Apache/NGINX)
  • Database error log (MySQL/MariaDB)

Don’t send us the entire server log. Instead, request entries from a few minutes before and after the error time and send those specific lines to Oxygen Support with your reproduction steps.

My Host Says “There’s Nothing in the Logs”

  • Ask them to make sure error logging is enabled and that they’re checking the correct logs for the time you provided.
  • Have them check all three: PHP, web server (Apache/NGINX), and database logs.
  • If the first support tech can’t find entries, request escalation to a higher support tier or try a different support channel (chat/phone).

Remember: hosting is responsible for server stability and logging. Good hosts will quickly surface the cause (timeouts, memory, security blocks, etc.) and apply the right fix.

If Your Host Can’t/Won’t Help

You can still capture PHP errors using WordPress’ built-in debugging. Add the following in wp-config.php (above the line that says “That’s all, stop editing!”):

define( 'WP_DEBUG', true ); 
define( 'WP_DEBUG_LOG', true ); 
define( 'WP_DEBUG_DISPLAY', false ); // keep errors out of the page output
@ini_set( 'display_errors', 0 );

Reproduce the issue, then open /wp-content/debug.log to find entries from the time of the error. Note: logs are often in UTC.

Get SFTP/FTP Access from Your Host

When deeper troubleshooting is required, we may need to make file or configuration changes. Request SFTP/FTP credentials to your web host so we can access files if needed.

  • Ask your web host for: protocol (SFTP preferred), host, port, username, and either a password or SSH key, plus the web root path.
  • Confirm the credentials work and reach your live site’s files (wp-config.php, wp-content/, etc.).

What to Send to Oxygen Support

  • Exact steps to reproduce + the page/template URL.
  • Timestamp & timezone when you reproduced the issue.
  • Your IP address and a screenshot of the error (include the browser address bar).
  • Relevant log excerpts from WP Debug Toolkit or from your host (PHP/web server/database errors).
  • Environment details: WordPress version, Oxygen version, PHP version, and a list of active plugins.

Submit everything at oxygenbuilder.com/support. The more precise your details, the faster we can help.

Still Stuck?

In your support message, tell us exactly where you’re blocked and what you’ve tried so far. Please don’t be shy; communication is crucial, and we want to help you resolve the issue quickly.

About WP Debug Toolkit

We’ve partnered with WP Debug Toolkit to make troubleshooting faster. It centralizes server errors, PHP notices, and environment info into one place and makes it easy to export clean reports for support. Use discount code OXYDOC for a special offer.

  • Install & activate WP Debug Toolkit.
  • Enable logging and reproduce the problem in Oxygen (open Builder, save, etc.).
  • Copy the logs it generates and include them in your support ticket.

WP Debug Toolkit won’t change your site; it just helps you see what the server is already doing behind the scenes without digging through multiple log locations.

Updated on: September 29, 2025