Bobcares

Quick fix for Nginx SSL connection refused

by | Aug 28, 2019

Popular browsers like Google Chrome, Mozilla Firefox, etc need SSL for websites.

Therefore, website owners have to migrate their websites from HTTP to HTTPS.

Often wrong migration steps result in an Nginx SSL connection refused error.

At Bobcares, we help customers in setting up Nginx SSL as a part of our Server Management Services.

Today let’s have a deep check on this error and the way our Support Engineers fix it.

 

What is the Nginx SSL connection refused error?

Have a vague idea about the error? Let’s make it clear.

As we all know, the Hypertext Transport Protocol aka HTTP fetch pages from the server and display on the browser.

HTTP/2 is the new version of the HTTP protocol and offers high transfer speed.

However, due to security reasons, popular browsers discard older protocols and only support HTTP/2 for HTTPS connections.

Usually, the default listening port in the Nginx server is the standard HTTP port 80. But HTTP/2 only supports HTTPS connections, that require port 443 open in the server.

Therefore when the server does not listen to 443, it shows connection refused error.

 

How do we fix the error?

Usually, the fix for SSL connection refused error involves opening port 443 in the Nginx configuration file. Let’s see how our Support Engineers provide an appropriate fix to this problem.

Firstly, we check the status of port 443 in the server using the netstat command,

netstat -plan | grep :443

On finding it closed, we open the port 443 in the firewall. Here again, different firewalls follow different commands to open a port.

For instance, to open port 443 in iptables, we use the command:

iptables -A INPUT -p tcp --dport 443 -j ACCEPT

Similarly, in the CentOS server, to open port in firewalld, we use,

firewall-cmd --permanent --zone=public --add-port=443/tcp

Next, we edit the Nginx configuration file /etc/nginx/nginx.conf and add,

listen 443 ssl http/2 default_server;
listen [::]:80 default_server;

It will add 443 as the listening port in the Nginx server and thus enables HTTPS connections.
Finally, when Nginx listens on port 443, it looks like,

[root@xxx ~]# netstat -lpan | grep :443
tcp 0 0 1xx.2x.111.23:443 0.0.0.0:* LISTEN 11978/nginx
tcp 0 0 1xx.2x.111.22:443 0.0.0.0:* LISTEN 11978/nginx
tcp 0 0 1xx.2x.111.19:443 0.0.0.0:* LISTEN 11978/nginx

 

[Still stuck with Nginx SSL errors? We can solve it in a jiffy.]

 

Conclusion

In short, the Nginx SSL connection refused error mainly occur due to Nginx’s misconfigurations. Today’s write-up showed how our Support Engineers fix the SSL connection refused error in Nginx servers.

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