How to Fix the ERR_CONNECTION_REFUSED Error in Chrome

Aug 14, 2023

How to Fix the ERR_CONNECTION_REFUSED Error in Chrome

Trying to access a site only to face the ERR_CONNECTION_REFUSED error in Google Chrome? 🙅‍♂️ Here are a few tips on how to fix it! 👉 Subscribe: https://www.youtube.com/c/Kinsta?sub_…

Nowadays everything is instantaneous, so being barred from accessing websites due to the ERR_CONNECTION_REFUSED error can be really frustrating. Despite it being no fun, sometimes getting this error is a sign that something serious has gone wrong.

This error can be really confusing for average users. That’s because it’s hard to distinguish whether the problem is with your WordPress site or due to an external factor, such as network or browser issues.

However, the ERR_CONNECTION_REFUSED message is very common and usually refers to non-WordPress-related issues. Luckily, troubleshooting the reason behind this error it’s a relatively easy task. In this video, we’ll explain what the message means and how to fix it.

ℹ️ About Kinsta

Kinsta is an award-winning Cloud Platform designed to host and manage your WordPress sites, Applications, and Databases faster and more efficiently. Trusted by 25,000+ companies worldwide, from developers, startups, and agencies, to multinational brands, we guarantee lighting-fast performance, enterprise-level security, ease of use, and exceptional support.

🚀 Try our flagship Managed WordPress Hosting plans and get $240/month worth of premium features included in every plan. That’s free unlimited migrations, 20% faster load times thanks to Google’s fastest servers and Premium Tier network backed by Cloudflare’s 275+ CDN locations worldwide, and 24/7/365 multilingual technical support from humans in less than 2 minutes.

👉 Try risk-free with our 30-day money-back guarantee Powerful Managed WordPress Hosting

👤Follow us:
► https://kinsta.com/blog/
► https://kinsta.com/newsletter/
► https://twitter.com/kinsta
► https://instagram.com/kinstahosting
► https://facebook.com/kinstahosting

💡Discover all of our hosting solutions ► https://kinsta.com/

🕘Timestamps

0:00 How to Fix the ERR_CONNECTION_REFUSED Error in Chrome
1:38 What Is the ERR_CONNECTION_REFUSED Error?
2:38 Check the Status of the Website
3:16 Restart Your Router
3:52 Clear Your Browser’s Cache
5:16 Assess Your Proxy Settings and Adjust Them as Needed
6:53 Disable Firewall and Antivirus Software Temporarily
7:44 Clear Your DNS Cache
9:19 Change Your DNS Address
10:54 Disable Any Chrome Extensions
12:22 Reinstall the Chrome Browser

📚 Resources

📙 The Complete Guide on How to Fix the ERR_CONNECTION_REFUSED Error in Chrome
► https://kinsta.com/blog/err_connectio…

#err_connection_refused #GoogleChrome

Content

0.1 -> Hey everyone, I'm Mike.

1.15 -> And today we're going to be going over nine tips

3.43 -> that will show you how to fix

4.67 -> the connection refused error in Chrome.

7.145 -> (upbeat music)

12.78 -> In a digital world, hooked on instant gratification.

15.5 -> One of the last things you want to experience

17.3 -> when browsing is an error message

19 -> such as the connection refused error.

21.89 -> This can be incredibly frustrating

23.58 -> and may even be a sign

24.83 -> that something has gone seriously wrong.

26.57 -> For the average user, the really confusing errors

28.97 -> are the ones that can be hard to distinguish

30.59 -> between a problem with your WordPress site

32.37 -> and something else such as a network or browsing issue.

35.91 -> The connection refused error message is especially common

38.8 -> and usually a non WordPress site related error message

41.89 -> you'll sometimes see in Chrome.

43.69 -> Fortunately, it's relatively easy to pinpoint

46.09 -> the cause of this problem,

47.54 -> and this video will explain how to fix it.

50.33 -> But before we get too far, I want to let you know

52.76 -> that there'll be links and more resources

54.52 -> in the video's description below,

56.42 -> and remember

57.253 -> subscribe and ring that bell to get notifications

59.95 -> for future helpful content.

62 -> All right. Let's get started.

64.02 -> Fixing this connection refused error typically

66.03 -> involves the following steps.

67.98 -> Check to see if the page itself is down,

70.41 -> restart your router,

72.39 -> clear your browser's cache.

74.77 -> Assess your proxy settings

76.03 -> and adjust them as needed

78.1 -> temporarily disable Antivirus and Firewall software.

81.86 -> Flush your DNS cache,

83.84 -> change your DNS address,

85.98 -> disable any outdated Chrome extensions

88.45 -> and re-install your Chrome browser.

91.01 -> But first,

91.843 -> let's take a deeper look

92.98 -> into what this error actually means.

97.43 -> Unfortunately, encountering errors goes hand in hand

100.22 -> with using the internet.

101.19 -> There are hundreds of possibilities from the white screen

103.32 -> of death to the classic 404 error,

105.54 -> to the connection timed out error.

107.87 -> When you visit a website using Google Chrome

109.84 -> and encounter the message, this site can't be reached

112.62 -> it means that your attempt to connect was refused.

115.44 -> This error code also appears in other browsers,

117.97 -> in Mozilla, you'll see the message unable to connect.

121.09 -> And in Microsoft edge, it says,

122.507 -> "Hmmm... can't reach this page."

125.4 -> As of most error messages, the connection refused error

128.4 -> lets you know that something has gone wrong

130.37 -> without being kind enough to tell you why it's happened.

133.07 -> This means it's up to you to find

134.72 -> and resolve the root issue if possible,

137.44 -> although the range of potential causes

139.32 -> can make troubleshooting tricky.

140.83 -> It is possible to fix the connection refused error

143.73 -> let's walk through nine steps you can take

145.59 -> starting with the ones most likely to provide an answer.

151.42 -> Your first step should be

152.29 -> to check the status of the website

153.65 -> you're trying to access.

155 -> As you've already mentioned

156.03 -> the connection refused error can sometimes be caused

158.47 -> by the site server rather than your own internet connection.

162.03 -> A simple way to check whether this is the case

163.73 -> is to visit another webpage.

165.26 -> If the error message occurs again

166.96 -> the problem most likely originates with your connection.

169.506 -> If the second page loads correctly, however

171.84 -> the first site was probably at fault.

173.86 -> You can also check out

174.761 -> https://downforeveryoneorjustme.com

176.946 -> enter the address of the non-functioning page

179.15 -> and click on or just me?

181.28 -> This site will then assess

182.44 -> whether the page is offline or online.

185.46 -> Unfortunately, when a page is down

187.14 -> the only thing you can do is wait for it to be fixed.

189.64 -> However, if the page is up and still not loading for you

192.57 -> it's time to do some further troubleshooting.

197.43 -> As a tried and tested method

198.96 -> for fixing many internet related issues.

201.08 -> Your next step will be to try turning it off

203.7 -> and back on again,

205.37 -> restarting your home or office router

206.99 -> doesn't come with 100% guarantee

208.976 -> but the process takes just a few minutes.

211.15 -> So it's worth the try

212.36 -> when you're dealing with a potential connection issue

215.09 -> to do this disconnect the power supply from your router

218.01 -> you'll then need to wait for about 30 seconds

219.9 -> before plugging it back in.

221.57 -> Once the router has booted up again

223.35 -> try to access the page that returned an error.

226.03 -> If it loads, then you're good to go.

227.9 -> If not, well then onto the next potential solution.

234.41 -> Like any good internet browser,

236.1 -> Chrome will store information

237.58 -> and its cache on your computer or device.

239.91 -> This includes your browsing history, saved login data

243.08 -> and cookies.

243.99 -> All of which are recorded in order to load the

246.07 -> relevant pages more quickly than next time they're visited.

249.28 -> Although they're useful,

250.44 -> caches can cause numerous issues when they become outdated.

253.56 -> This is because the cache version of a page

255.93 -> is likely to no longer match the current live version.

259.75 -> Fortunately, this problem is easily solved

262.14 -> by clearing your cache.

263.85 -> But before you do that, you can easily check to see

266.13 -> if it's a browser cache issue.

267.59 -> By first opening up your browser in Incognito mode

271.07 -> or you can try a different browser.

272.605 -> If you're still seeing the error, then you'll want to

274.91 -> proceed with clearing your cache.

277.07 -> To do so begin by opening up Chrome's primary menu

280.76 -> in the top right corner of your browser window.

283.76 -> From there select more tools.

286.18 -> You can then click on clear browser data

289.27 -> on the resulting page.

290.56 -> You'll need to make sure that all the lists

292.26 -> of file categories are selected.

294.16 -> If they aren't

294.993 -> Chrome won't be able to empty the entire cache.

297.63 -> Instead it will remove the most recent entries

300.65 -> which won't result in the desired effect.

302.8 -> An alternative method of completing this process

304.88 -> is to enter this following URL into your address bar

308.71 -> the resulting screen should grant you access

310.92 -> to the same options

311.96 -> we've previously discussed.

316.02 -> With security threats consistently on the rise.

318.63 -> It's no wonder many people are now

319.873 -> using individual solutions to protect their sensitive data.

323.67 -> A popular way of doing this is through proxy servers.

326.38 -> A proxy lets you go online under a different IP address

329.42 -> and acts as an intermediary between your browser

331.93 -> and the websites you visit

333.61 -> as well as keeping your IP address private.

335.85 -> It can also help to filter cache data

337.91 -> and server communications.

339.81 -> Just as with caching a proxy server can be useful

342.85 -> but can also cause the connection refused error message.

346.85 -> For example,

347.73 -> a web server might reject the IP address

349.78 -> attached to a proxy server

351.31 -> and then reject the actual connection as a result.

354.17 -> It's also possible

355.01 -> that the proxy is offline or incorrectly configured.

358.07 -> In short, if the error message and question occurs

360.89 -> it's worth checking out your proxy settings.

362.95 -> Chrome actually has its own proxy section

365.39 -> which can make the step a particularly simple process.

368.39 -> After all.

369.223 -> You won't need to spend any time searching

370.78 -> for the correct tools in your browser

373.25 -> to get started

374.24 -> access the settings menu in your Chrome browser.

377.02 -> This will open up the complete menu of options.

379.55 -> Under the system section,

381.04 -> you'll need to click Advanced

382.3 -> at the bottom to see this,

383.9 -> you should find an entry titled open proxy settings

387.2 -> by selecting it you'll be taken to the corresponding menu.

390.25 -> Your next step depends on the system

391.72 -> you're currently using,

393.24 -> Windows users will want to click on LAN settings

395.53 -> and uncheck the use proxy server for LAN option.

399.22 -> If you're a Mac user, you should immediately find yourself

401.85 -> in the relevant menu.

403.53 -> You'll then have to uncheck all selectable proxy protocols

406.65 -> and check to see if the connection refused error message

409.52 -> has been resolved.

413 -> Firewalls and antivirus software intended to protect users

416.28 -> and their systems.

417.34 -> They scan your device regularly

419.03 -> and automatically block any suspicious activity.

422.02 -> You may start to notice a recurring theme here.

424.24 -> However, this type of advanced security

426.13 -> can at times lead to connection issues.

428.52 -> This is because Firewalls can often block pages

430.71 -> they don't need to

431.99 -> or reject content that is completely safe

434.8 -> to check whether this is the case for you.

436.67 -> Try disabling your firewall and antivirus programs.

439.87 -> Of course, this is only advised if you know, for sure

442.47 -> that the site you're intending to visit is safe.

445.01 -> Additionally, you should only disable this kind

447.2 -> of software temporarily.

448.87 -> Switch it back on after you finished checking to see

451.17 -> whether the error has been resolved.

452.97 -> So you don't become vulnerable to attacks.

454.73 -> If you repeatedly encounter errors

456.32 -> because of your firewall or antivirus software

458.93 -> you may want to consider changing what you're using.

464.064 -> As what of an extension to an earlier troubleshooting step.

467.22 -> Your next task will be to clear your DNS cache.

470.25 -> Although most people are aware

471.73 -> that their browser creates a cache,

473.4 -> not as many know

474.55 -> that their operating system does the same thing.

477.22 -> For example, your DNS cache contains

479.72 -> all of the temporary entries for pages

481.59 -> you've accessed within your browser.

483.95 -> These entries store key information related

486.24 -> to the domain names and addresses of the pages you visited.

489.67 -> The purpose of this feature is similar

491.28 -> to that of other types of caches.

493.32 -> It accelerates the loading process as it eliminates

495.97 -> the need to contact a site's DNS server repeatedly.

499.4 -> This will save you time in the long run.

501.45 -> However, you may occasionally see some short-term issues.

505.21 -> If a stored entry, no longer matches the current version

507.81 -> of the website it refers to,

509.248 -> technical errors like the connection refused error message

512.211 -> are not unusual.

514.09 -> Fortunately, clearing your DNS cache is a quick

516.9 -> and easy solution.

517.95 -> Again, how you'll do this will depend

519.751 -> on your operating system.

521.91 -> With Windows,

522.75 -> you'll launch the start menu

523.9 -> by pressing the Windows key and search for CMD.

527.39 -> This should return the command prompt

529.41 -> in the command prompt run the following command.

532.1 -> You will then see a confirmation

533.55 -> that it has successfully flushed the DNS resolver cache.

537.07 -> On a Mac,

537.903 -> you'll need to do the following

539.14 -> click on Go,

539.973 -> up in the finder tool bar and then click on Utilities

543.19 -> open the terminal, run the following command

546.18 -> and you'll need an administrator access to do this.

548.29 -> When you've done that

549.17 -> try accessing the problem site again

551.35 -> hopefully if you followed all of our advice

553.73 -> it should be working by now.

555.3 -> If not your DNS may require some more attention.

560.8 -> As we discussed before an outdated DNS cache entry

564.05 -> is a potential source of issues

565.45 -> like the connection refused error.

567.45 -> However, the DNS address itself can also be responsible

570.81 -> for these kinds of problems.

572.47 -> This is because it can become overloaded

574.5 -> or even go completely offline.

576.11 -> In the majority of cases

577.36 -> your DNS server address is automatically obtained

580.04 -> from your internet provider.

581.42 -> However, you can change it if required

583.87 -> how you'll do this will again

584.89 -> depend on the operating system you're using.

587.17 -> Let's explore how Mac users can complete this process.

590.13 -> First you'll need to open up system preferences,

593.04 -> on the resulting screen

594.34 -> select the option marked Network

596.75 -> you'll then need to click on Advanced,

598.73 -> from there, select the DNS option found

601.14 -> at the top of the screen

602.83 -> to add a new DNS server

604.22 -> click on the plus button.

606.04 -> To edit an existing DNS server, instead

608.37 -> double click on the DNS IP address you wish to adjust.

611.72 -> You could try temporarily changing these

613.41 -> to a public DNS server, such as Google or CloudFlare.

617.2 -> Some prefer to use Google's public DNS long-term

620.22 -> due to them sometimes being more reliable.

622.51 -> CloudFlare also offers a secure and blazing fast free DNS.

626.76 -> Here's a tip,

627.82 -> If you're already using a free DNS server

629.93 -> and having issues

631.15 -> removing it and defaulting back to your ISP's DNS servers

634.95 -> also sometimes fixes things.

637.07 -> Google and CloudFlare aren't perfect 100% of the time.

640.17 -> And there have been a few instances

641.56 -> where we've noticed switching back has resolved the issue.

644.53 -> Once you've changed your DNS address, you can then

646.52 -> attempt to access the site again

648.48 -> and cross your fingers.

652.75 -> There's no denying that installing extensions

654.79 -> often contributes

655.68 -> to a more well-rounded Google Chrome experience.

658.22 -> The many extensions offered can add key features

660.93 -> and even help to automate complex processes.

663.7 -> However, a large number of the extensions available

666.2 -> for Google Chrome are not developed

668.05 -> by the browsers developers.

669.35 -> Instead they're usually created by third parties.

671.85 -> This can mean there's no real guarantee the work

674.09 -> as you intend,

675.16 -> or they will be correctly updated over time.

678.05 -> Incorrect or outdated extensions

679.78 -> are likely to cause numerous issues

681.95 -> including the connection refused error message.

684.77 -> For this reason, it's important to regularly

686.81 -> audit the extensions that are attached to your browser.

689.64 -> To do that first open the extensions menu

691.79 -> in your Chrome browser, you can then begin to assess

694.66 -> each of your installed extensions in turn.

697.21 -> Start by questioning whether you actually need each one.

700.07 -> If an extension is no longer necessary

702.16 -> you can remove it.

703.37 -> Next, find out when each extension

705.4 -> that you want to keep was last updated.

707.78 -> Ideally it should have been updated

709.48 -> within the last three months.

711.08 -> Any longer than that could be a sign

712.85 -> that the is being neglected by its developers.

715.89 -> If possible, you want to remove those extensions

718.036 -> and replace them with newer alternatives.

720.65 -> Of course, new and fully updated extensions

722.86 -> can still sometimes cause problems.

724.55 -> If you suspect that this is the case,

726.04 -> begin by disabling all of your attached extensions.

729.24 -> If the site you've been trying to access

731.02 -> loads after doing this

732.61 -> you'll know that at least one of them is at fault.

735.35 -> You can then reactivate one extension

737.11 -> at a time until you've honed in on the problem software.

743.35 -> As with any other application

744.78 -> Chrome itself is never going to be completely bug free.

748.11 -> Your installation of the browser can contain various issues

751.07 -> especially if it hasn't been updated in a while.

753.86 -> What's more problems between your browser

756.05 -> and operating system are surprisingly common.

758.44 -> As a result, sometimes the only solution is to completely

761.26 -> re-install Chrome.

762.76 -> You can do this by removing the current installation

764.88 -> from your device.

766.07 -> You can then download the most recent version

768.12 -> of the browser by visiting the official Chrome website.

771.16 -> So you may be wondering

772.41 -> what if none of these solutions work, Mike?

774.88 -> This is usually a sign

775.89 -> that something more serious is wrong on the server side.

778.85 -> In other words, what the website itself,

781.2 -> unfortunately in this scenario,

782.57 -> the only thing you can do

783.94 -> is be patient.

785.32 -> It's likely that the website's owners are working hard to

788.01 -> resolve any issues and things will resume

790.26 -> like business as usual before too long.

792.35 -> If accessing the site is a matter of urgency

794.6 -> you could try reaching out to its owners directly.

797.31 -> There are numerous ways to do this.

798.67 -> Although social media and email are particularly effective

802.48 -> and unlikely to be affected by any website downtime.

806.3 -> You want to explain the problem you're facing

808.08 -> and mention that you've tried several solutions to no avail.

811.58 -> Hopefully the team behind the website gets back

813.81 -> to you to discuss the best course of action.

816.3 -> You may even be doing them a favor.

818.05 -> If you happen to make them aware of an issue

819.67 -> they don't know what's preventing access to their site.

822.82 -> If you're a Kinsta client

823.9 -> and it's your own WordPress site that is having the issues

826.41 -> feel free to reach out to our support team.

828.38 -> We are here 24/7 to help.

832.1 -> Kinsta's WordPress hosting can speed up your website

834.47 -> by up to 200% and you'll get 24/7 support

837.59 -> from our expert WordPress engineers.

839.74 -> Let us show you the Kinsta difference,

841.63 -> try a free demo of our MyKinsta dashboard

844.397 -> at demo.kinsta.com.

846.65 -> Thank you for watching.

847.62 -> And don't forget to subscribe for more tutorials

849.88 -> explainers and helpful content like this.

852.122 -> (upbeat music)

Source: https://www.youtube.com/watch?v=Cvgnjzg4B2g