Blog

Seen a “401 Unauthorized” or “Access Denied” message when visiting a website?

This error means your browser couldn’t prove you have permission to view a page.

The good news: it’s easy to fix. This guide explains what causes the 401 error and walks you through the steps to resolve it quickly.

Let’s get started!

Understanding the 401 Unauthorized Error

When you browse the internet, your web browser and the website’s server exchange messages to deliver the content you want to see. Most of the time, these exchanges are successful, and you never see any error codes. However, if you don’t have the necessary permissions to access a web page, you will see the 401 Unauthorized Error.

A 401 error happens when the server can’t verify your identity. In most cases, your login credentials are missing, invalid, or expired.

You might see this error displayed in a few different ways, but they all mean the same thing:

• “401 Authorization Required”
• “HTTP 401 Error – Unauthorized”
• “Access Denied”

This is a client-side error, meaning the problem is caused by the browser sending either incorrect or incomplete credentials to the server.

401 vs. 403 Errors – What’s the Difference?

The 401 and 403 errors look similar but mean different things:

Suggested read: How to Fix a 502 Bad Gateway Error

Common Reasons for a 401 Error

Once you understand what causes a 401 error, fixing it is simple. Follow these steps to resolve the issue and regain access.

1. Incorrect Login Details

Let’s start with the most obvious and common cause: a simple typo. You might have accidentally misspelled your username or entered the wrong password. Check for common mistakes like having Caps Lock on or mixing up similar characters like the number ‘0’ and the letter ‘O.

2. Outdated Browser Cache and Cookies

All modern browsers store bits of information from websites you visit in a local storage area called the browser cache. It also saves small files called browser cookies that remember your login status, site preferences, and other session data.

Storing this information locally is great for website performance, but it can sometimes cause a 401 error. If your browser’s cache or cookies become corrupted or outdated, your browser might send an old, invalid login token to the server. The server, seeing these incorrect credentials, denies you access and returns a 401 error.

3. An Incorrect URL or an Outdated Link

Sometimes the problem is as simple as a mistake in the web address. You may have typed the incorrect URL or clicked on an old bookmark that points to a page that no longer exists or has been moved behind a login wall. Certain pages on a website are meant to be private and require authentication. If you try to access one directly without being logged in, the server will correctly block you with a 401 error. Always double-check that the URL is correct and that you’re trying to access a public page or are properly logged into a private area.

4. Plugin or Theme Incompatibility (For Website Owners)

Security or firewall plugins can sometimes block valid logins after an update or misconfiguration. Temporarily disabling them can help identify the issue. This is a common source of WordPress errors, and it is often triggered after a recent update to a plugin, a theme, or the WordPress core itself.

5. Firewall Issues

A firewall (either on the website’s server or even on your own network) can cause a 401 error. A Web Application Firewall (WAF) is designed to identify and block suspicious traffic. If it detects what it perceives as a threat from your IP address (perhaps due to multiple failed login attempts), it may block your access to prevent a potential attack, which would result in a 401 Unauthorized response.

How to Fix a 401 Error (Step-by-Step)

Now that you understand what the 401 error is and where it comes from, it’s time to troubleshoot 401 issues and get you back in. We’ll start with the simplest solutions and work our way up to more technical fixes. Follow these steps in order, as the problem is often resolved within the first few steps.

1. Double-Check the URL

This may sound overly simple, but an incorrect URL is a frequent cause of this error. Make sure you have typed the web address correctly. Pay close attention to ensure you haven’t accidentally tried to access a page that is restricted to administrators or logged-in users.

If you clicked on a link from an email or another website, it might be an outdated link that now points to a protected resource. Try navigating to the website’s main homepage and then finding the page you need from there.

2. Review Your Login Credentials

The most common problem is a simple mistake in your username or password. Before trying anything else, carefully re-enter your login details.

• Check for typos.
• Ensure your Caps Lock key isn’t on.
• If you’re still locked out and are not 100% sure of your password, the safest bet is to use the “Forgot Password?” or “Reset Password” link on the login page. This eliminates any guesswork.

3. Clear Your Browser’s Cache and Cookies

If the URL and your login details are correct, the next step is to check your browser’s stored data. Outdated or corrupted cache and cookies can cause your browser to send invalid authentication information to the server. Clearing the browser cache is a quick and easy way to fix 401 errors.

Here’s how to do it on popular browsers:

• In Chrome or Firefox, open Settings → Privacy → Clear browsing data.
  
• Select Cookies and Cached images/files, then confirm.
  
• Restart your browser and try again.

After clearing the data, close your browser completely, reopen it, and try logging in again.

4. Deactivate Your WordPress Plugins (For Website Owners)

If you are experiencing the 401 error on your own WordPress site after an update, then a plugin (especially a security or firewall plugin) may be causing this error. The easiest way to check this is to deactivate WordPress plugins.

• If you can access your dashboard: Navigate to Plugins > Installed Plugins. Select all plugins by checking the top box, and from the Bulk actions dropdown, choose Deactivate. If the error disappears, you know a plugin was the cause. Reactivate them one by one, checking the site after each activation, until the error returns. The last plugin you activated is the culprit.
• If you are locked out of your dashboard: You’ll need to use an FTP client or your hosting provider’s File Manager. Navigate to the wp-content folder and find the plugins folder. Rename it to something like plugins_old. This will deactivate all plugins. If you can now log in, rename the folder back to plugins and then follow the one-by-one reactivation process from your dashboard.

5. Check the HTTP Headers (For Advanced Users)

This is a more technical step. When a server sends a 401 response, it also includes additional headers. These headers contain data that specifies which authentication scheme the server requires (e.g., Basic, Bearer). You can view this header using your browser’s developer tools.

1. Open the page causing the 401 error.
2. Right-click anywhere on the page and select Inspect or Inspect Element.
3. Go to the Network tab.
4. Reload the page. You’ll see a list of network requests.
5. Find the request with a 401 status (it will be red). Click on it.
6. In the details pane, look for the Headers tab. This can give a developer clues about why the authentication is failing.

6. Contact the Website Administrator

If none of these steps work, contact the site administrator.

Include:

• The URL causing the error
• The time it occurred
• The steps you’ve already tried

This information will help them identify and resolve the issue much faster.

Wrapping Up: Fixing 401 Errors the Easy Way

In this post, we’ve seen that “401 error” is rarely a sign of a major problem. More often than not, it’s a simple miscommunication between your browser and the server, usually caused by a minor issue like a typo, an outdated browser cache, or a conflicting plugin.

Most 401 errors are easy to fix, often caused by old logins, cached data, or a simple typo.

But if you manage multiple sites, dealing with access issues, plugins, and performance can take up valuable time.

RunCloud helps you focus on your work while it handles the rest – from security to server management.

Start your free RunCloud trial today and spend less time troubleshooting.

Still using a @gmail.com or @yahoo.com address for your business?

A custom domain email, like contact@example.com, instantly boosts trust and makes your brand look credible and professional. It’s also free advertising as every email you send reinforces your website.

The only catch is that setting it up means dealing with a few confusing DNS terms: MX, SPF, DKIM, and DMARC.

This guide breaks them down in plain English and shows how to configure everything correctly using tools like RunCloud and Cloudflare.

Let’s get started!

Why Proper Email Configuration is Necessary

Even if your email already works, proper configuration is critical for three reasons:

1. Building Credibility & Brand Trust

A custom domain email is your digital business card. It instantly builds credibility and brand trust. An address like contact@example.com shows you are an established, legitimate business, whereas a generic @gmail.com address can appear unprofessional and temporary to potential clients.

2. It Helps Avoid the Spam Folder

The single most important technical reason for proper setup is to prevent emails from landing in the spam folder. Major providers like Google and Yahoo now require email authentication (SPF & DKIM) to verify that you are who you say you are. Without these records, your invoices and client proposals will likely be rejected or land in spam.

3. Protecting Your Brand from Spoofing & Phishing

Proper email configuration is an important security measure that protects your brand’s reputation from fraud. These records make it nearly impossible for malicious actors to “spoof” your domain and send phishing emails pretending to be you. This safeguards your customers from scams and prevents the irreversible damage to your brand trust that occurs when your name is tied to fraudulent activity.

What Do You Need for Your Business Email Setup

Before we get into the technical settings, let’s break down the three simple things you need to get started. We’ll also cover what you can expect to spend, so there are no surprises.

A Custom Domain Name

A domain name is your unique digital address on the internet (e.g., example.com). The great news is that if you already have a website, you do not need to buy a new domain. You can use the same one for your email at no additional cost.

If you are buying a domain name for the first time, then you should try to pick something that is short and memorable but also represents your brand. Some companies go a little overboard with this and end up spending millions of dollars on a domain name. However, there is no need for that, and if you don’t have a domain yet, you can purchase one from a domain registrar like Namecheap, GoDaddy, or Cloudflare. A standard .com domain typically costs around $10 to $20 per year.

An Email Hosting Provider

This is the service that will actually handle sending, receiving, and storing your emails. While some basic web hosting plans include free email, a dedicated provider offers far better reliability, security, and features.

Professional email hosting is very affordable and is usually priced per user (or per mailbox). Depending on the provider and features you need, you can expect to spend between $3 and $12 per user per month. There are far too many good email providers available out there to cover in one post, so we recommend reading the following posts if you want to learn more:

• 10 Best Self-Hosted Email Server Platforms to Use in 2025 
• 15 Best Email Hosting For Small Business (2025)
• The 19 Best, Reliable Transactional Email Services 2025

Access to Your Domain’s DNS Records

This sounds technical, but it’s simply the control panel where you tell the internet where to send your email. It’s like a switchboard for your domain, and you just need to know where to find it. You can typically access your DNS settings through the same company where you bought your domain (your registrar) or with your website hosting provider.

Access to managing your DNS records is free. This essential feature is included with your domain registration or hosting plan.

A Step-by-Step Guide to DNS Records for Business Email

Let’s dive into the technical details. This part can seem intimidating, but it’s just a matter of copying and pasting the right information into the right boxes. We’ll walk through setting up each of the four records one by one.

For this guide, we’ll demonstrate how to add these records using Cloudflare, a very popular and free DNS provider known for its speed and user-friendly interface. The steps will be very similar, no matter which DNS provider you use.

First, log in to your Cloudflare account, select your domain, and navigate to the DNS > Records section. This is where we’ll be working.

How to Set up MX Records

If your domain is a building, then the MX (Mail Exchange) record is the mailing address on the front door. It tells the internet exactly which server to use to deliver your emails.

Your email provider (like Google Workspace or Zoho Mail) will give you a list of their mail servers and a “priority” number for each. Your job is to enter these into your DNS settings.

1. In your Cloudflare DNS panel, click Add record.
2. Select MX from the “Type” dropdown menu.
3. In the Name field, type @. This symbol simply means it applies to your main domain, and your emails will look like contact@example.com. If you want to use a subdomain for a separate email server, then you can type the subdomain here. For example, if you type txns here, then the resulting email address will look like contact@txns.example.com
4. In the Mail server field, enter the first server address your email provider gave you (e.g., test.google.com).
5. In the Priority field, enter the corresponding priority number (e.g., 10).
6. Click Save.

Important: Your email provider will probably give you multiple MX records. You must repeat this process for every single one they provide, each with its own unique server and priority number.

How to Set up SPF Record

An SPF (Sender Policy Framework) record tells all other mail servers which email systems are officially allowed to send email on behalf of your domain.

An SPF record is created as a TXT record. You can only have one SPF record per domain, so if you already have one, you’ll need to edit it rather than add a new one.

1. In Cloudflare, click Add record.
2. Select TXT for the “Type.”
3. In the Name field, type @.
4. In the Content field, paste the SPF value your email provider gave you. For Google Workspace, it looks like this: v=spf1 include:_spf.google.com ~all
5. Click Save.

What does SPF Records mean:

1. v=spf1: This just identifies it as an SPF record.
2. include:_spf.google.com: This is the list of servers that can send emails on your behalf. It tells everyone on the internet to check and approve anything Google sends on your behalf.
3. ~all (Soft Fail): This tells servers that if an email comes from a sender not on the list, they should accept it but mark it as suspicious. It’s safer to start with this. –all (Hard Fail) tells them to reject the email completely.

How to Set up a DKIM Record

DKIM (DomainKeys Identified Mail) is like a unique, unbreakable wax seal on a letter. It uses a cryptographic signature to prove that the email genuinely came from you and its content hasn’t been altered in transit.

First, you’ll need to generate a DKIM key inside your email provider’s admin panel. This process will give you two pieces of information: a selector (the name for the record) and a public key (the long text value).

1. In Cloudflare, click Add record.
2. Select TXT for the “Type.”
3. In the Name field, paste the selector your provider gave you. It will look something like google._domainkey.
4. In the Content field, paste the entire long public key text. Be careful to copy the whole thing, as it can be very long.
5. Click Save.

To learn more about this, check out our full-length article on DKIM – What Is It & Why Your Emails Need It.

How to set up a DMARC Record

DMARC (Domain-based Message Authentication, Reporting, and Conformance) checks both the SPF records and the DKIM records. Based on what it finds, it follows your instructions on what to do with unverified mail and sends you reports on email activity.

If you have an existing domain that is sending out emails, we strongly recommend starting with a “monitor only” policy to avoid accidentally blocking legitimate emails.

1. In Cloudflare, click Add record.
2. Select TXT for the “Type.”
3. In the Name field, type _dmarc.
4. In the Content field, paste the following starter policy: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com (You are supposed to replace this email with your actual email, but read the next section to find what we recommend).
5. Click Save.

Understanding the DMARC policy:

1. v=DMARC1: Identifies the record.
2. p=none: This is your instruction. Here, none means “monitor only” and don’t take any action. Later, you can change this to p=quarantine (send to spam) or p=reject (block entirely).
3. rua=mailto:…: This tells servers where to send daily reports about your email activity, which is incredibly useful for spotting issues. These reports are sent in XML format and are best viewed using specialized software. We recommend using the Postmark DMARC report tool instead of publishing your personal email on the internet.

Suggested read: How to Flush DNS Cache on Windows, Mac, and Linux

Using RunCloud and Cloudflare for Effortless DNS Management

If the steps above seemed tedious and prone to error, you’re not alone. Managing DNS records directly at your domain registrar or a basic hosting panel often comes with frustrating challenges:

• Clunky Interfaces: The control panels are frequently outdated and confusing to navigate.
• Disconnected Workflow: You have to jump between your server management panel, your email provider’s instructions, and your DNS provider’s website, increasing the chances of making a copy-paste error.
• Slow Updates: After you make a change, you can be left waiting for hours due to slow DNS propagation and left wondering if you did it correctly. If you make a mistake, correcting it can be just as slow and stressful.

RunCloud simplifies DNS management by integrating directly with Cloudflare.

Instead of jumping between multiple dashboards, you can add or edit DNS records straight from your RunCloud panel.

This reduces the risk of typos, speeds up propagation, and keeps your workflow consistent across sites and domains.

Final Thoughts

Setting up MX, SPF, DKIM, and DMARC isn’t just a technical detail as it’s what ensures your emails reach inboxes, not spam folders.

Taking a few minutes to configure these records protects your brand, improves deliverability, and builds long-term trust with your clients.

With RunCloud and Cloudflare, you can handle these configurations from one clean dashboard. No more switching between panels or waiting for updates.

Manage DNS and hosting the smart way. 

Get started with RunCloud and set up a professional email the right way.

FAQs & Common Troubleshooting

Seeing the SSL_ERROR_RX_RECORD_TOO_LONG message in Firefox?

This error usually means your browser or server isn’t handling HTTPS traffic correctly – often due to a simple configuration issue.

This guide explains what causes the error and how to fix it, whether you’re a site visitor or a server administrator.

What the SSL_ERROR_RX_RECORD_TOO_LONG Error Means

When you use Firefox to browse the web, you might occasionally see the error message “SSL_ERROR_RX_RECORD_TOO_LONG”. While the name sounds complicated, the reason behind it is usually quite simple.

Firefox shows this error when it tries to load a secure (HTTPS) page but receives an unencrypted or invalid response instead. In most cases, the site’s SSL configuration is incorrect, or it’s using outdated security protocols.

This error can be caused by multiple issues. Let’s break down the common causes:

Common Server-Side Causes of the Error

In most situations, the problem isn’t with your computer or browser but with how the website you’re trying to visit is set up.

• Incorrect port configuration: Firefox connects to HTTPS sites through port 443. If the server handles plain HTTP traffic on this port, Firefox will stop the connection and show this error.
  
• Outdated security protocols: Servers still using old SSL or TLS versions (1.0 or 1.1) can’t complete the handshake with modern browsers.
  
• Certificate problems: Expired, misconfigured, or mismatched certificates prevent Firefox from validating the site’s identity.

Common Browser or Client-Side Causes

Although it is less common, this error can also be caused by the settings on your own computer or within Firefox.

• Cached data: Outdated cookies or cache files can confuse Firefox when a site’s security settings change.
  
• Proxy settings: Incorrect proxy configuration (especially on corporate networks) can block HTTPS connections.
  
• Extensions: Overactive security or ad-blocker add-ons may interfere with the TLS handshake.

Suggesed read: How to Fix err_ssl_protocol Error

How to Fix the SSL_ERROR_RX_RECORD_TOO_LONG Error

We now know what causes the SSL_ERROR_RX_RECORD_TOO_LONG error. Let’s see how to fix this quickly and easily:

Clear Your Browser’s Cookies and Cache

As we explained above, sometimes browsers try to connect using outdated information, which can cause errors. To fix this, we will simply clear and delete all the cookies and cache for that particular site. This forces Firefox to download a fresh, correct copy of the website.

1. Clear cache and cookies: Go to Settings → Privacy & Security → Clear Data, select both checkboxes, and confirm. Then restart Firefox and reload the page.

2. Check proxy settings: Go to Settings → General → Network Settings → Settings…. Choose No proxy, unless you’re on a network that requires one.

3. Disable extensions: Restart Firefox in Troubleshoot Mode. If the site loads, re-enable your add-ons one at a time to find the culprit.

4. Update Firefox: Go to Help → About Firefox to install the latest version.

Check Your Proxy Settings

Most home internet users connect directly to the web. However, some users on a company or school network use a “proxy server”. This proxy server intercepts all the traffic coming into the network, which can cause errors on the site. If you are using a proxy server, make sure it is configured correctly on your computer:

1. Go to the Settings menu again (click the three lines in the top-right).
2. On the General tab, scroll to the bottom to “Network Settings” and click the Settings… button.

3. This will open a new window. The correct setting for most home users is “No proxy“. If it’s set to something else, change it to “No proxy” and click OK.

Note: If you are on a corporate or school network, you may need a proxy. If changing this setting breaks your internet connection, revert it and check with your IT department.

Temporarily Disable Your Browser Add-ons

As we discussed above, some browser extensions interfere with network connections, and you can fix this by simply disabling the problematic extension.

1. The fastest way to do this is by restarting Firefox in Troubleshoot Mode (previously called Safe Mode). This temporarily disables all your add-ons.
2. Click the three-line menu, go to Help, and then select Troubleshoot Mode….
3. Click Restart.

Once Firefox restarts, try visiting the website again. If it works now, you know an add-on is the problem! You can then follow the steps below to find out which one.

4. Go to the menu and select Add-ons and Themes (or press Ctrl+Shift+A).
5. Click on Extensions.
6. Disable your extensions one by one using the blue toggle switch, reloading the problem website after each one. When the site finally loads correctly, you’ll find the extension causing the issue.

Update Your Browser

The world of internet security is constantly evolving. Every few years, new security protocols (the “rules” for the handshake) are released, and old ones are retired. An outdated browser might not know the latest, most secure handshake that modern websites use to communicate on the Internet. Making sure Firefox is up-to-date ensures it has all the modern tools it needs to connect securely.

1. Click the three-line menu and go to Help.
2. Select About Firefox.
3. A small window will pop up and automatically check for updates. If an update is available, it will download and install it for you.

If none of the browser fixes worked, the issue is almost certainly on the server. Here’s how to diagnose and correct it as a developer.

How Developers and Admins Can Fix the Error

If you are a website administrator, then you are in the best position to resolve the “SSL_ERROR_RX_RECORD_TOO_LONG” error for your website. This error is almost always a sign of a server-side misconfiguration, where the server sends an unexpected response during the initial TLS handshake. The following detailed checks will help you diagnose and fix the underlying issue.

Use an Online SSL/TLS Diagnostic Tool

Before you spend too much time manually combing through configuration files, you should use an external tool to give you a detailed report. These services test your server from the perspective of an external client and can pinpoint subtle misconfigurations that are easy to miss.

You can use a service like Qualys SSL Labs’ SSL Test or DigiCert SSL Installation Diagnostics Tool to perform a deep analysis of your entire SSL/TLS setup. It will grade your configuration and provide a detailed report on protocol support, key exchange, cipher strength, and certificate chain issues.

The report will explicitly flag common problems such as an incomplete certificate chain (“Chain issues: Incomplete”), support for insecure protocols, or weak cipher suites. This provides an actionable checklist of items to fix within your server’s configuration files.

Verify Your Server’s Port and Protocol Configuration

This is the most frequent cause of the error.

Verify Port and Protocol Settings

• NGINX: Add listen 443 ssl; to your configuration block.
• Apache: Use <VirtualHost _default_:443> and ensure SSLEngine on is enabled with valid certificate file paths.

Check Certificate Installation

• Install both your main certificate and the intermediate chain from your CA.
• Confirm the certificate’s CN or SAN matches your domain.
• Renew any expired certificates.

Update TLS and Cipher Settings

• Enable TLS 1.2 and 1.3 only.
• Disable older protocols (TLS 1.0, 1.1, SSLv2, SSLv3).
• In RunCloud, select your preferred TLS version from the dropdown menu in the TLS settings.

Audit the SSL Certificate Installation and Validity

A faulty SSL certificate setup can prevent the TLS handshake from even beginning properly. The browser needs to validate a complete and correct certificate “chain of trust” to proceed. Any break in this chain or mismatch in information will cause connection failures.

• Check for Correct Installation: Ensure that you have installed not just the primary domain certificate but also the necessary intermediate certificates provided by your Certificate Authority (CA). A missing intermediate certificate breaks the chain of trust, and while some browsers can fetch them, it is not reliable behavior.
• Verify Domain Name Matching: The certificate’s Common Name (CN) or, more modernly, a name in the Subject Alternative Name (SAN) field must exactly match the domain the user is accessing. A certificate issued for www.example.com will not be valid for example.com unless both are listed in the SAN.
• Confirm Expiration: While usually leading to a different error, an expired certificate can sometimes contribute to configuration issues that manifest as this error. Always confirm your certificate is within its validity period.

Update and Strengthen Your TLS Version and Cipher Suites

Modern browsers, including Firefox, have deprecated older, insecure versions of the TLS protocol (specifically TLS 1.0 and 1.1). If your server is configured only to support these outdated versions, Firefox will refuse to connect, which can sometimes result in this specific error. You must ensure your server is configured to negotiate a modern, secure protocol.

• Enable Modern Protocols: Your server configuration should be set to enable TLS 1.2 and TLS 1.3, the current industry standards for security.
• Disable Obsolete Protocols: Explicitly disable support for TLS 1.0, TLS 1.1, and all versions of SSL (SSLv2, SSLv3). This not only resolves compatibility issues but is also the best security practice to protect against known vulnerabilities.

If you are using RunCloud, you can do this very easily by selecting the right value from a dropdown menu in your TLS certificate settings.

Simplifying SSL Management with RunCloud

Configuring SSL manually can be slow and error-prone.

RunCloud simplifies it with one-click SSL setup, automatic renewals, and a staging environment for safe testing, helping you avoid common issues like this Firefox error.

One-Click SSL Certificates with Auto-Renewal

RunCloud offers a seamless integration with Let’s Encrypt, a free and trusted certificate authority. With RunCloud, you can:

• Install SSL with a Single Click: Secure your websites with a valid SSL/TLS certificate in seconds, directly from your RunCloud dashboard.
• Automated Renewals: RunCloud automatically handles the renewal of your Let’s Encrypt certificates, ensuring your sites remain secure without any manual intervention. This eliminates the risk of expired certificates causing errors.

Making changes directly to a live server can be risky and can inadvertently lead to configuration errors. RunCloud’s staging environment provides a safe sandbox to test any modifications before deploying them to your production site.

Once you’ve verified that your changes are working correctly in the staging environment, you can easily sync them with your live site.

Final Thoughts: Simplify SSL Management

Managing SSL manually can take hours – and a single misstep can break your site.

With RunCloud, you can deploy, renew, and manage SSL certificates in seconds through an intuitive dashboard.

Start your free RunCloud trial today and secure your sites the easy way.

FAQs