Bobcares

GCP Connection Refused – How to fix

by | Jun 28, 2021

Wondering how to fix the GCP “Connection Refused” error? We can help you.

Often customers having VM instances on the Google cloud platform report to us that they receive a connection refused while trying to access the server via a browser.

Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services.

Today we will see how our Support Engineers fix this for our customers.

How to fix GCP Connection Refused error

Before going into the steps for fixing this error we can see what causes this error.

Cause:

Following are some of the common causes:

1. Firewall rules or tags being misconfigured in one of the following ways:

  • Not having a proper tag that allows Compute Engine to apply the appropriate firewall rules to the instance.
  • Doesn’t have a firewall rule that allows traffic to the external IP address for the instance.

2. We might be trying to access the VM using an https address. The URL must be http://[EXTERNAL_IP] rather than https://[EXTERNAL_IP].

Steps to fix this error

Following are the steps that our Support Engineers do to fix this error:

For ensuring the VM instance has the correct tags we can do the following:

1. Firstly, from the Google Cloud Console, go to the VM instances page.

2. Then go to VM instances and select the instance we wish to connect to.

3. After that click Edit and select  Firewalls

4. From there we must ensure that the Allow HTTP traffic box is checked. If it is not checked, check it.

5. Finally we can save the changes.

For ensuring that a proper firewall rule exists we can do the following:

1. Firstly from the Google Cloud Console, go to the Firewall rules.

2. Here we need to look for a firewall rule that allows all IP ranges through tcp:80.

3. If we could not find the rule, we can create one by clicking Create firewall rule.

4. Then enter a name for the rule, such as default-allow-http.

5. In the Source IP ranges section, enter 0.0.0.0/0 to allow traffic from all sources.

6. And under Protocols and ports, check Specified protocols and ports and enter tcp:80.

7. After creating the firewall rule we can check whether the issue persists.

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to fix the GCP “Connection Refused” error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF