Last updated: April 25, 2026

Quick Answer

Error code: -379 is a network-level error that typically appears in Google Chrome and Chromium-based browsers, signaling that a connection attempt failed due to an unexpected or empty server response. It most often occurs when a server closes the connection before sending any data, leaving the browser with nothing to display. Clearing the browser cache, checking server configuration, and verifying SSL/TLS settings resolve the issue in most cases.

Key Takeaways

• Error code: -379 maps to ERR_EMPTY_RESPONSE in Chromium-based browsers, meaning the server sent back no data at all.
• The error can originate on either the client side (browser, local network) or the server side (misconfigured web server, firewall, or hosting environment).
• Clearing browser cache and cookies is the fastest first step and resolves the issue for many users.
• Server-side causes include misconfigured .htaccess files, exhausted PHP memory limits, and aggressive firewall rules that drop connections silently.
• SSL/TLS mismatches between the browser and server can also trigger this error.
• Website owners and developers face this error more often than casual users because it frequently stems from deployment changes or plugin conflicts.
• If the error appears only on one specific page, the problem is almost always server-side or page-specific (redirect loops, heavy scripts).
• Checking the browser’s developer console (Network tab) provides the fastest diagnosis path.

---

What Is Error Code: -379?

Error code: -379 is an internal Chromium error code that corresponds to the string ERR_EMPTY_RESPONSE. When Chrome or any Chromium-based browser (Edge, Brave, Opera) encounters this error, it means the browser successfully established a TCP connection to the server but received zero bytes in response — no HTTP headers, no body, nothing.

This is different from a “404 Not Found” error, where the server does respond but says the resource doesn’t exist. With -379, the server goes completely silent.

Who sees this error most often:

• Website developers after pushing code changes or switching hosting providers
• Users on corporate networks with strict firewall or proxy rules
• Site owners after installing new plugins, themes, or server-side scripts
• Anyone whose ISP or router is intermittently dropping connections

---

What Causes Error Code: -379?

The root cause of error code: -379 sits in one of two places: the client (browser/network) or the server. Knowing which side is responsible cuts troubleshooting time significantly.

Client-Side Causes

Cause	Why It Triggers -379
Corrupted browser cache	Cached data conflicts with the server response cycle
Faulty browser extensions	Ad blockers or VPN extensions intercept and drop the connection
Antivirus/firewall software	Security tools silently block outgoing or incoming packets
DNS resolution failure	Browser connects to the wrong IP, server sends nothing
Unstable local network	Packet loss causes the connection to drop mid-handshake

Server-Side Causes

Cause	Why It Triggers -379
PHP memory limit exhausted	Script crashes before sending headers
.htaccess misconfiguration	Redirect loop or invalid rule causes Apache to drop the connection
Nginx return or deny rules	Server silently drops the request
SSL/TLS handshake failure	Incompatible cipher suites cause the connection to close immediately
DDoS protection / WAF rules	Firewall blocks the request without sending a response
Server resource exhaustion	CPU or RAM maxed out; worker processes unavailable

Quick rule: If the error appears on multiple websites, the problem is almost certainly on the client side. If it only appears on one specific site or page, look at the server.

---

How to Fix Error Code: -379 as a Regular User

These steps apply to anyone seeing error code: -379 in their browser, regardless of whether they own the website.

Step 1: Reload the page
Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to force a hard reload, bypassing the cache for that single request.

Step 2: Clear browser cache and cookies
In Chrome: Settings → Privacy and Security → Clear Browsing Data → select “Cached images and files” and “Cookies” → Clear data. This resolves a large portion of client-side -379 errors.

Step 3: Disable browser extensions
Open an Incognito window (which disables most extensions by default). If the page loads, a browser extension is the culprit. Disable them one by one to identify the offender.

Step 4: Check your antivirus and firewall
Temporarily disable third-party antivirus web-shield features and test again. Re-enable immediately after testing.

Step 5: Flush DNS cache

• Windows: Open Command Prompt and run ipconfig /flushdns
• Mac: Run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Linux: Run sudo systemd-resolve --flush-caches

Step 6: Try a different network
Switch from Wi-Fi to mobile data (or vice versa). If the page loads on a different network, the issue is with your ISP, router, or local firewall.

Step 7: Try a different browser
If the page loads in Firefox but not Chrome, the problem is browser-specific, not server-side.

---

How to Fix Error Code: -379 as a Website Owner or Developer

Website owners have more diagnostic tools available and more potential fixes to apply. Start with the browser’s developer console before touching server settings.

Step 1: Check the Network Tab

Open Chrome DevTools (F12) → Network tab → Reload the page. Look for the failing request. The status column will show “(failed)” with no response headers. This confirms the server sent nothing.

Step 2: Review Server Error Logs

Check your hosting control panel or SSH into the server and review:

• Apache: /var/log/apache2/error.log
• Nginx: /var/log/nginx/error.log
• PHP-FPM: /var/log/php-fpm/error.log

Look for entries timestamped at the moment of the error. Common log messages that correlate with -379:

• PHP Fatal error: Allowed memory size exhausted
• upstream timed out
• client closed connection while waiting for request

Step 3: Increase PHP Memory Limit

In wp-config.php (for WordPress) or php.ini:

define('WP_MEMORY_LIMIT', '256M');

Or in php.ini:

memory_limit = 256M

Step 4: Check .htaccess for Redirect Loops

A common trigger for -379 on Apache servers is a redirect loop caused by a malformed .htaccess rule. Temporarily rename the file to .htaccess_backup and test. If the error clears, the file contains the problem.

Step 5: Review SSL/TLS Configuration

Use SSL Labs’ free SSL test to check for handshake errors, expired certificates, or unsupported cipher suites. A failed TLS handshake causes the server to drop the connection before sending any response — a textbook -379 scenario.

Step 6: Check WAF and Hosting Firewall Rules

If the site uses Cloudflare, Sucuri, or a hosting-level WAF, check the firewall event log for blocked requests matching the URL that triggers the error. Whitelist legitimate traffic or adjust the rule sensitivity.

Understanding how search engines and web infrastructure interact can also help developers diagnose why crawlers and users encounter different error patterns on the same server.

---

Does Error Code: -379 Affect SEO?

Yes — if error code: -379 persists on a page, it can negatively affect search engine rankings and crawl coverage.

When Googlebot requests a URL and receives an empty response (the server-side equivalent of -379), Google treats it similarly to a server error. If the empty response repeats across multiple crawl attempts, Google may:

• Reduce crawl frequency for the affected URLs
• Drop the page from the index if the error persists for an extended period
• Flag the site as unreliable in quality assessments

For site owners managing 404 redirects and technical SEO, understanding how empty responses differ from standard 4xx and 5xx errors is critical. A 404 tells Google the page is gone; a -379/empty response tells Google nothing at all, which can be worse for crawl budget.

Monitoring your backlink profile alongside server error rates helps identify whether lost links correlate with periods of server instability.

If your site’s content strategy depends on consistent crawlability, resolving -379 errors quickly should be a priority — not an afterthought.

---

Error Code: -379 vs. Similar Browser Errors

Understanding how -379 compares to related errors prevents misdiagnosis.

Error Code	Name	Meaning
-379	ERR_EMPTY_RESPONSE	Server connected but sent zero bytes
-6	ERR_FILE_NOT_FOUND	Local file missing
-101	ERR_CONNECTION_RESET	Connection was reset mid-transfer
-102	ERR_CONNECTION_REFUSED	Server actively refused the connection
-105	ERR_NAME_NOT_RESOLVED	DNS lookup failed
-200	ERR_CERT_COMMON_NAME_INVALID	SSL certificate mismatch
-324	ERR_EMPTY_RESPONSE (older code)	Older Chromium equivalent of -379

Note: Some older documentation references -324 as the empty response error. In more recent Chromium builds, -379 is the code surfaced to users, though the underlying ERR_EMPTY_RESPONSE string remains consistent.

---

Interactive Diagnostic Tool

Use the tool below to identify the most likely cause of your error code: -379 based on your situation:

---

Common Mistakes When Troubleshooting Error Code: -379

Even experienced developers make these errors when dealing with -379:

Mistake 1: Clearing cache without testing in Incognito first
Clearing cache is time-consuming and irreversible for session data. Test in Incognito first — it takes five seconds and gives the same diagnostic information.

Mistake 2: Assuming the problem is always client-side
Many tutorials focus on browser fixes, but server-side causes are equally common. Always test whether the error affects other sites before touching browser settings.

Mistake 3: Ignoring server logs
The server error log almost always contains the exact reason for the empty response. Skipping it means guessing instead of diagnosing.

Mistake 4: Increasing PHP memory without finding the root cause
Bumping memory limits is a band-aid. If a script is consuming excessive memory, find and fix the script rather than just raising the ceiling indefinitely.

Mistake 5: Not checking SSL certificate expiry
An expired or misconfigured SSL certificate causes the TLS handshake to fail silently, producing a -379 error. Check certificate validity as part of the standard checklist.

For developers managing SEO-driven content at scale, server reliability directly affects organic performance — making these fixes more than just a technical concern.

---

FAQ: Error Code: -379

Q: Is error code: -379 the same as ERR_EMPTY_RESPONSE?
Yes. Error code: -379 is the numeric identifier Chromium uses internally for ERR_EMPTY_RESPONSE. Both refer to the same condition: the server connected but returned zero bytes.

Q: Does -379 mean the website is down?
Not necessarily. The website’s server may be running, but a specific configuration issue, script crash, or firewall rule is preventing it from sending a response to your browser.

Q: Can a VPN cause error code: -379?
Yes. VPNs can route traffic through servers that block certain connections or introduce packet loss, causing the server to receive an incomplete request and drop the connection without responding.

Q: How long does it take to fix -379?
Client-side fixes (cache clear, extension disable) take under five minutes. Server-side fixes vary: a simple .htaccess correction takes minutes, while diagnosing a complex script memory issue may take hours.

Q: Will Google penalize my site for -379 errors?
Google does not issue manual penalties for server errors, but persistent empty responses reduce crawl coverage and can cause pages to drop from the index over time.

Q: Is -379 specific to Chrome?
The error code and label are specific to Chromium-based browsers. Firefox and Safari display different error messages for the same underlying condition (empty server response), but the root cause is identical.

Q: Can a CDN cause this error?
Yes. CDN misconfigurations, origin pull failures, or aggressive CDN-level firewall rules can cause the CDN edge node to drop connections without forwarding a response, producing a -379 on the client.

Q: Does restarting the router fix -379?
Sometimes. If the cause is a stale DNS entry or a dropped connection at the router level, a restart clears it. But if the cause is server-side, restarting the router has no effect.

Q: How do I tell if the problem is my ISP?
Switch to a mobile hotspot or a different Wi-Fi network. If the error disappears, the problem is with your primary network or ISP.

Q: Can WordPress plugins cause -379?
Yes. Plugins that add heavy processing to page loads (security scanners, page builders with unoptimized queries) can exhaust PHP memory or execution time, causing the server to terminate the response before sending any data.

---

Conclusion

Error code: -379 (ERR_EMPTY_RESPONSE) is a clear signal that something broke the communication between a browser and a server before any data could be exchanged. The good news: it’s almost always fixable, and the fix is usually straightforward once the source is identified.

Actionable next steps:

1. Start with Incognito mode — if the page loads there, a browser extension or cache is the culprit.
2. Test on a different network — if that fixes it, the problem is local (router, ISP, or antivirus).
3. Check server error logs if you own the site — the log entry will name the exact failure.
4. Verify SSL certificate validity using a free tool like SSL Labs.
5. Review recent changes to plugins, themes, .htaccess, or server configuration if the error started suddenly.
6. Monitor crawl coverage in Google Search Console after fixing the error to confirm Googlebot can access affected pages again.

For site owners, pairing technical error resolution with a solid SEO content strategy ensures that server stability and organic visibility reinforce each other — because a page that can’t load can’t rank.

---

References

• Chromium source code — net/base/net_error_list.h (The Chromium Project, 2024): https://source.chromium.org/chromium/chromium/src/+/main:net/base/net_error_list.h
• Google Search Central — HTTP status codes and crawling (Google, 2023): https://developers.google.com/search/docs/crawling-indexing/http-network-errors
• SSL Labs SSL Server Test (Qualys, 2024): https://www.ssllabs.com/ssltest/