ssl_error_rx_record_too_long

This page explains how to resolve the “SSL received a record that exceeded the maximum permissible length” error (error code: ssl_error_rx_record_too_long). This error is typically caused by server configuration rather than WooCommerce settings, commonly involving SSL certificate setup, port settings, and VirtualHost settings.

Symptoms

↑ Back to top

When this error occurs, your browser displays an error page instead of loading your site over HTTPS. The exact message varies by browser:

• In Firefox, you see: “SSL received a record that exceeded the maximum permissible length” with error code ssl_error_rx_record_too_long.
• In Chrome or Edge, you may see: “This site can’t provide a secure connection” or ERR_SSL_PROTOCOL_ERROR.
• In Safari, you may see: “Safari can’t open the page because Safari can’t establish a secure connection to the server.”

The error typically appears on all HTTPS pages of your site, not (remove — avoid implying tasks are simple) within WooCommerce.

Cause

↑ Back to top

This error occurs when your browser expects an SSL-encrypted response but receives unencrypted data instead. The following are the most common causes:

• No SSL certificate installed. Your site URLs are set to use HTTPS, but your server does not have a valid SSL certificate installed or configured.
• Incorrect port configuration. SSL traffic uses port 443 by default. If your server is configured to listen for SSL on a different port, or if port 443 is serving non-SSL content, the browser receives unexpected data.
• Misconfigured VirtualHost settings. On Apache servers, the VirtualHost for port 443 may be missing or incorrectly configured, causing the server to respond with plain HTTP instead of HTTPS.
• Site URL set to HTTPS without SSL configured. If the WordPress Address or Site Address in Settings > General uses https:// but the server is not set up for SSL, every page request triggers this error.

Solutions

↑ Back to top

Start by identifying the cause using the diagnostic steps below, then apply the appropriate fix.

Check your site URLs

↑ Back to top

1. Go to Settings > General in your WordPress dashboard.
2. Check the WordPress Address (URL) and Site Address (URL) fields.
3. If both URLs begin with https://, confirm with your hosting provider that a valid SSL certificate is installed and active for your domain.
4. If no SSL certificate is installed and you do not need HTTPS, change both URLs to use http:// instead of https://. If you cannot access the dashboard because of the error, ask your hosting provider for assistance or update the URLs directly in the database.

Verify your SSL certificate

↑ Back to top

Use an online SSL checker tool (such as SSL Labs or SSL Shopper) to verify that your SSL certificate is correctly installed. If the tool reports errors, contact your hosting provider and share the results so they can correct the configuration.

Contact your hosting provider

↑ Back to top

If you have confirmed that your site URLs are correct and the issue persists, contact your hosting provider or server administrator. Ask them to review the following:

• Whether a valid SSL certificate is installed for your domain.
• Whether the server is configured to listen for SSL connections on port 443.
• Whether the Apache or Nginx VirtualHost configuration for port 443 is correct and points to the right document root.

Because this error is caused by server-level configuration, your hosting provider is best positioned to diagnose and resolve it.

Questions and support

↑ Back to top

Do you still have questions and need assistance? 

• If you’re looking to extend the core functionality shown here, we recommend reviewing available extensions in the WooCommerce Marketplace.
• Need ongoing advanced support or a customization built for WooCommerce? Hire a Woo Agency Partner.
• Are you a developer building your own WooCommerce integration or extension? Check our Developer Resources.

If you weren’t able to find the information you need, please use the feedback thumbs below to let us know.