Troubleshooting · Troubleshooting
How to Fix ERR_CONNECTION_REFUSED in WordPress
Short answer
ERR_CONNECTION_REFUSED means the browser reached your site's server, but the server refused the connection. Check whether the site fails on other devices first. If it fails everywhere, restart the web server, check the firewall and the Cloudflare SSL/TLS mode, and contact your host if the refusal continues.
Key takeaways
- ERR_CONNECTION_REFUSED means the server actively refused the connection, so the browser never reached WordPress.
- Chrome describes the error as the page not letting Chrome connect, or the page being blocked.
- If the site fails on every device, the fault is on the server; if it fails on one computer, the fault is local.
- Cloudflare uses port 80 for Flexible mode and port 443 for Full and Full (strict) mode, as of November 2026.
- A stopped web server, a firewall block, or a missing SSL certificate on port 443 are the most common server-side causes.
- WordPress Site Health, found under Tools → Site Health, lists critical issues after the site loads again.
What does ERR_CONNECTION_REFUSED mean in WordPress?
It means the browser reached the server's address, but the server refused the connection, so no page loaded.
Google Chrome Help describes the error in one line: “The page didn't let Chrome connect or the page is blocked.” Get help with common error messages in Chrome
A refused connection is an active answer, not silence. The server, or a firewall in front of it, said no at once. That differs from a timeout, where the browser waits and hears nothing back.
In WordPress, the error usually sits below WordPress itself. WordPress never gets the request, so no WordPress page, login screen, or error page can appear. The fix depends on where the refusal happens, so start by finding that place.
Browsers use port 80 for plain HTTP and port 443 for HTTPS, as of November 2026. If nothing listens on the port the browser tries, the connection is refused. A server that only listens on port 80 refuses every HTTPS request on port 443.
Is the problem on your site or on the visitor's computer?
Open the site on another device and network, such as a phone on mobile data, to see if the refusal follows the site or the computer.
| What you see | Likely place | Next step |
|---|---|---|
| The site fails on every device and network | Your server | Check the web server, firewall, and Cloudflare settings |
| The site loads on mobile data but not on Wi-Fi | Your computer or network | Work through the browser and network fixes |
| The site loads in one browser but not another | That browser | Clear its cache, check extensions, and check its proxy settings |
If the site fails on every device, the server is the likely cause. If it loads on mobile data but not on your Wi-Fi, the fault sits on your network or computer. If it loads in Firefox but not in Chrome, the fault sits in Chrome.
How do you fix ERR_CONNECTION_REFUSED as a visitor?
Reload the page, check the address for typos, then clear the browser cache and test the site in a private window.
- Check the address for typos, including any port number after the domain, then reload the page once.
- Try the site in another browser. Mozilla Support advises trying another browser to separate a browser fault from a wider fault. Server Not Found - Troubleshoot connection problems
- Open a private window and load the page there. If it works, an extension or stored browsing data is a likely cause.
- Clear cached images and cookies. In Chrome, open Settings, then Privacy and security, then Delete browsing data, and select cached images and files plus cookies.
- Turn off your VPN and check your proxy settings. The Chrome error page itself suggests checking the proxy and the firewall.
- Flush the DNS cache. On Windows, open Command Prompt and run
ipconfig /flushdns, then reload the page. - Restart your router and your device, then try the site again.
Stop at the step that fixes it. If the site still refuses after every step, the fault is likely on the server, so move to the owner checks below.
How do you check if your web server is running?
Log in to your hosting control panel and check the server status page, then ask your host to restart the web server if it shows as stopped.
A stopped web server is the most direct cause. Cloudflare's docs list an offline origin web server application as one of the two common causes of its Error 521 page, which is the Cloudflare form of the same refusal. Error 521: Web server is down
Check the host status page first. If the host reports an outage or maintenance, wait for the host to finish before you change anything on your site.
If you have server access, confirm the web server process is running and listening on ports 80 and 443. If it stopped after a restart or a crash, start it again and watch for errors in the server log.
After a restart, load the site in a fresh private window. If the homepage and the login page both load, the restart fixed it. If the refusal returns within minutes, a crash or a resource limit is likely, so check the logs and contact your host.
Why does a firewall or security plugin refuse connections?
A firewall, security plugin, or host security rule can reject connections before WordPress loads, which looks the same as a stopped server.
Cloudflare's docs name blocked Cloudflare requests as the second common cause of Error 521, next to an offline origin. Error 521: Web server is down
A WordPress security plugin can also lock out visitors after it flags an address or a login pattern. A WordPress.org support thread records a site that went unreachable after a security plugin treated a login tool as an attack. ERR_CONNECTION_REFUSED
- Open the security plugin log and look for your IP address or the time the error started.
- Add your IP address to the plugin allow list, then reload the site.
- Pause the firewall or security plugin for a short test only. If the site loads, the block was the cause.
- Turn the protection back on after the test and fix the rule, instead of leaving the site unguarded.
If a host firewall is the cause, only the host can change it. Ask the host to check whether its firewall or a rate limit is rejecting your connections.
How do you fix the Cloudflare connection refusal?
Check the Cloudflare SSL/TLS mode against the port your origin listens on, and allow Cloudflare's IP ranges through the origin firewall.
| Cloudflare SSL/TLS mode | Cloudflare to origin | Origin port |
|---|---|---|
| Flexible | HTTP | 80 |
| Full | HTTPS | 443 |
| Full (strict) | HTTPS, certificate checked | 443 |
Cloudflare connects to the origin on port 80 when the mode is Flexible and on port 443 when the mode is Full or Full (strict), as of November 2026. If the origin only listens on port 80 while the mode is Full, every connection is refused.
If the site shows Error 521 instead of the browser error, the refusal is between Cloudflare and the origin. Read our guide to fix Cloudflare Error 521 for the full origin checks.
For a short test, switch the Cloudflare proxy off for the record, which is called DNS-only or grey-clouded mode. If the site loads with the proxy off, the fault sits in the Cloudflare settings or the path to the origin.
Check the mode under SSL/TLS in the Cloudflare dashboard. Our guide to Cloudflare SSL settings for WordPress explains each mode and when to use it.
How do you check for a wrong port or missing SSL certificate?
Try the site over plain HTTP and over HTTPS, and compare the results, because a refusal on one scheme points to that scheme's port or certificate.
If http:// loads but https:// is refused, nothing listens on port 443 or no certificate is installed. Install a certificate on the origin, then set Cloudflare to Full or Full (strict).
A WordPress.org support reply records a site that refused every HTTPS request because no SSL was set up on the server at all, while the owner relied only on the Cloudflare proxy. The fix was to install a certificate on the server itself.
Check that the domain's DNS records point to the current server IP. A record that still points to an old server can send browsers to a machine that refuses the connection. If the refusal looks like a DNS fault instead, read our guide to fix DNS_PROBE_FINISHED_NXDOMAIN.
If you moved hosts or changed DNS recently, allow time for the change to spread. Our guide explains how long DNS propagation takes and how to check it.
How do you use WordPress Site Health and debug logs to find the cause?
Open Tools → Site Health in the WordPress dashboard to read the Status and Info tabs, then check wp-content/debug.log for PHP errors.
WordPress added Site Health in version 5.2, and its docs describe two tabs: Status, which lists critical issues and recommended improvements, and Info, which lists technical details. Site Health: keep your website healthy
Site Health cannot run while the whole site refuses connections, so use it after the site loads again, or on a staging copy. It still helps you find the plugin or setting that stopped the server.
For PHP errors, WordPress docs describe WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY. Debugging in WordPress WP_DEBUG is false by default in wp-config.php.
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
With these lines, WordPress writes errors to wp-content/debug.log without showing them to visitors. Read the newest entries in that file to find the plugin, theme, or line that failed.
WordPress 5.2 also added a fatal error handler, so a crashing plugin shows a recovery message instead of a blank screen. Debugging in WordPress
Delete debug.log and set WP_DEBUG back to false when you finish. Leaving debug mode on can expose file paths and other details to visitors.
How do you know the fix worked?
Load the homepage and wp-admin in a fresh private window on two devices, and confirm both return the site instead of the error.
- The homepage loads without the refusal message.
- The WordPress login page at /wp-admin loads and accepts a login.
- The site loads in a second browser and on mobile data.
- The same pages load again after 10 minutes, not just once.
If the site loads after you paused a firewall or security plugin, turn the protection back on and add an allow rule instead of leaving it off. A fix that depends on disabled security is not a fix.
A 502 error after the refusal clears is a different fault, with its own cause. Read our guide to fix the 502 Bad Gateway error if that page appears next.
When should you contact your host?
Contact your host when the site refuses connections on every device and network, and you cannot reach the hosting panel or restart the web server.
Give the host the exact error text, the time it started, the URLs that fail, and whether the failure is on HTTP, HTTPS, or both. Short, exact details get a faster answer than a general report that the site is down.
Ask the host to confirm the web server is running, the firewall allows ports 80 and 443, and no server-side block lists your address. Hosts can also check server logs that you cannot see.
If the host finds the server healthy, the fault is likely in Cloudflare settings, DNS, or a plugin, so work through those checks next. If the host finds a server fault, ask what caused it and what will stop it from returning.
What mistakes should you avoid?
Do not keep clearing the cache or reinstalling WordPress when the server itself refuses the connection, because neither step reaches the server.
- Clearing the cache again and again while the server refuses every connection.
- Turning off the firewall or security plugin for good instead of fixing the rule that blocked you.
- Switching Cloudflare to Full or Full (strict) before the origin listens on port 443 with a certificate.
- Leaving WP_DEBUG set to true on a live site after you finish, which can show errors to visitors.
- Editing wp-config.php without a backup, since one wrong character can break the whole site.
- Assuming a fix on one computer proves the site is fixed for every visitor.
Frequently asked questions
Is ERR_CONNECTION_REFUSED the same as ERR_CONNECTION_TIMED_OUT?
No. ERR_CONNECTION_REFUSED means the server actively refused the connection, so the browser got a fast no. ERR_CONNECTION_TIMED_OUT means the browser waited and got no answer at all. A refusal points to a stopped service, a wrong port, or a firewall rule, while a timeout points to a slow, overloaded, or unreachable server.
Can a WordPress plugin cause ERR_CONNECTION_REFUSED?
Yes. A security plugin or firewall plugin can block an IP address or reject connections before WordPress loads, which looks the same as a stopped server. Check the plugin log for your address, add it to the allow list, or pause the plugin for a short test. If the site loads while it is paused, fix the plugin rule and turn the protection back on.
Why does my site work on my phone but not on my computer?
The fault is likely on your computer or network, not on the server. Your Wi-Fi network, VPN, proxy settings, firewall, or antivirus may block that site, or your browser cache may hold a bad entry. Try mobile data, another browser, and a private window to narrow it down, then clear the cache and check the proxy and firewall settings.
Why does the error appear only on HTTPS?
HTTPS uses port 443, while plain HTTP uses port 80. If nothing listens on port 443, or no SSL certificate is installed on the origin server, every HTTPS request is refused while HTTP still works. Install a certificate on the server, confirm it listens on port 443, and set Cloudflare to Full or Full (strict) if you use Cloudflare.
How long does it take to fix ERR_CONNECTION_REFUSED?
A browser-side fix takes a few minutes, since it is only a cache clear, a proxy change, or a restart. A server-side fix depends on what stopped the server, such as a crashed web server, a firewall rule, or a missing certificate. If your host reports an outage, the fix waits on the host, so ask for a time when you report it.
Sources
- Get help with common error messages in Chrome Google Chrome Help
- Error 521: Web server is down Cloudflare Docs
- Debugging in WordPress WordPress.org Documentation
- Site Health: keep your website healthy WordPress.org Documentation
- Server Not Found - Troubleshoot connection problems Mozilla Support
- Editing wp-config.php WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
