Bobcares

SSL_ERROR_UNRECOGNIZED_NAME_ALERT in Nginx Proxy Manager

by | Jul 17, 2024

Learn how to fix SSL_ERROR_UNRECOGNIZED_NAME_ALERT error in Nginx Proxy Manager. Our Nginx Support team is here to help you with your questions and concerns.

SSL_ERROR_UNRECOGNIZED_NAME_ALERT in Nginx Proxy Manager

SSL_ERROR_UNRECOGNIZED_NAME_ALERT in Nginx Proxy ManagerHave you been running into SSL certificate errors when trying to access your website over HTTPS (port 443)?

According to our Experts, this usually indicates a problem with the SSL certificate configuration.

Browsers expect a valid SSL certificate that matches the domain name being accessed.

The SSL_ERROR_UNRECOGNIZED_NAME_ALERT error indicates a security mismatch. The website’s SSL certificate doesn’t match the domain name we are trying to access.

Let’s look at some common causes and fixes for this error.

Common Causes

  • Incorrect SSL Certificate Configuration

    The server does not have a certificate that matches the requested hostname. Also, the Nginx configuration may not include the correct server block for the requested hostname.

  • DNS Issues

    The domain name does not point to the correct server IP address. Sometimes, there are issues with DNS propagation.

  • Misconfigured Nginx Proxy Manager

    In case, the Nginx Proxy Manager is not set up correctly to handle the requested domain, we will run into the error. Sometimes the error is because the SSL certificates may not be correctly assigned in NPM.

Troubleshooting Tips

  1. First, make sure the domain name is correctly pointed to the server’s IP address running Nginx Proxy Manager. We can use tools like `nslookup` or `dig` to verify DNS settings.

    nslookup bobcares.com
    dig bobcares.com

  2. Also, make sure the SSL certificate for the requested domain is correctly installed and associated in Nginx Proxy Manager. We have to check the certificate’s validity and make sure it covers the requested hostname.
  3. Then, open the Nginx configuration files and check for the server block corresponding to the requested domain. Furthermore, check if the server block includes the correct `server_name` directive.

    For example:

    server {
    listen 443 ssl;
    server_name bobcares.com;
    ssl_certificate /etc/nginx/ssl/bobcares.com.crt;
    ssl_certificate_key /etc/nginx/ssl/bobcares.com.key;
    # Other configurations
    }

  4. Next, check the Nginx Proxy Manager settings:
    • Log in to the Nginx Proxy Manager dashboard.
    • Then, go to the Hosts section and make sure the requested domain is correctly configured.
    • Also, check the SSL certificate is correctly assigned to the domain in the SSL section of the domain settings.
  5. Then, make sure the Nginx Proxy Manager and its components are up to date. Sometimes, issues can be resolved by updating to the latest version.
  6. Also, check the Nginx logs for more detailed error messages. We can find the logs usually at `/var/log/nginx/error.log` and `/var/log/nginx/access.log`.

    tail -f /var/log/nginx/error.log

Let us know in the comments if you need further help with the error.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to fix SSL_ERROR_UNRECOGNIZED_NAME_ALERT error in Nginx Proxy Manager.

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