Error message "This Connection Is Not Private"

Question

Hi,

I don’t understand why when I enter the url directly (https://mysite.com), it works very well.

However, when I search for “my brand name” from a search engine and try to access my website, I get an error message “connection not private” and it redirects me to the url https://othersite.com.

I checked nginx’s .conf file. I restarted nginx. I checked the ssl certificate.

Thanks.

Bobby · Answer

Hi there, Based on what you’ve described, it seems there might be a discrepancy between what is indexed on search engines and the actual content of your website. It sounds like Google has indexed a different site based on the mysite search term. To break this down: Direct URL Access : When you enter the URL https://mysite.com directly into your browser, you’re bypassing any intermediary steps and going straight to the site. The fact that this works without issues is a positive sign. It indicates that your server, Nginx configuration, and SSL certificate are likely set up correctly. Search Engine Results : When you search for “mysite” on a search engine, you’re presented with results that the search engine has indexed in the past. If the first result is redirecting you to a different website, it’s possible that the search engine has old or incorrect data associated with your domain. There could be several reasons for this: Previous Ownership : If your domain was previously owned by someone else, there might still be old indexed data. Hijacking or SEO Spam : In some cases, sites get compromised and have unwanted redirects injected. While you haven’t seen any evidence of this in your nginx configuration, it’s a possibility. Incorrect Search Result : Sometimes, search engines might show an incorrect or unrelated site as a search result due to various reasons including SEO techniques employed by other sites. Steps Forward : To address the issue, I recommend the following: Google Search Console : Sign up for Google Search Console (formerly Webmaster Tools) . This tool allows you to see how Google views your site. Once you’ve verified your domain, you can check for any crawl errors or security issues. Importantly, you can also submit your site’s sitemap to ensure Google accurately indexes your current content. Check Other Search Engines : Verify if this behavior is consistent across other search engines. If it’s a Google-specific issue, then focusing on the Google Search Console is key. Otherwise, you might need to address it with multiple search engines. Manual Review : Double-check your site’s files and database, especially if you’re using a CMS. Sometimes malicious redirects are injected into .htaccess files or within the database. In conclusion, while your direct URL access is functioning correctly, it’s essential to ensure search engines correctly index your site to ensure visitors can find you easily. Starting with the Google Search Console will give you insights into any potential issues or discrepancies Google may have with your site. Hope that this helps! Best, Bobby

KFSys · Answer

Heya, The error message “This Connection Is Not Private” is typically associated with SSL/TLS certificate issues. However, if your website is working fine when accessed directly via URL but showing this error when accessed from a search engine, the problem may be more complex. Here are some steps to diagnose and fix the issue: SSL/TLS Certificate : Double-check the validity of your SSL/TLS certificate. You can use online tools like SSL Labs Server Test to assess the status and configuration of your certificate. Ensure you have the correct intermediate certificates (chain) installed, if applicable. Nginx Configuration : Check your server blocks for any unintentional redirects. Make sure there are no configurations in place that could be redirecting traffic coming from certain referrers (like search engines). Look for any mention of “othersite.com ” or unexpected redirect rules in your configuration. Web Application : If you’re using any CMS or other web application, ensure it is not compromised. The redirection might be due to malicious code inserted into your application. Check .htaccess or equivalent configuration files for any unexpected redirection rules if you’re using software that utilizes such files (though .htaccess is mainly for Apache, not Nginx). Search Console : Check Google Search Console (formerly Webmaster Tools) for any notices or issues related to your domain. Make sure that the correct version (www vs. non-www, http vs. https) of your site is verified and set as the preferred version. DNS Hijacking or Cache : Ensure your domain’s DNS records haven’t been tampered with. Login to your domain registrar or DNS provider and verify the DNS settings. Clear your local DNS cache and your browser’s cache. Sometimes, old or cached DNS records can cause such issues. Malware Scan : It’s possible (though less likely) that a malware on your local system is causing this behavior. Run a full malware scan on your computer. Check with Your Hosting Provider : If you’re using a shared hosting provider, reach out to them and ask if they’ve experienced similar issues with other clients. HTTP Headers : Check the HTTP headers returned when you try to access the website from a search engine. Tools like curl can help. Run a command like curl -I https://mysite.com/ to see the headers. External Links : Check if there are any external links or resources on your site that could be causing redirection or mixed content issues. If after going through these steps, the problem persists, you may want to consider seeking help from a cybersecurity professional or a system administrator who can provide a deeper investigation into the issue.

alexdo · Answer

Hello @2b0c9f00c48c44aeb337263a462e06 I’ll follow Bobby’s recommendation on requesting a review from Google Search Console (formerly Webmaster Tools) . As mentioned you can submit your site’s sitemap to ensure Google accurately indexes your current content which should resolve your issue here. Hope that this helps!

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

Error message "This Connection Is Not Private"

Related questions

How to change existing certbot/nginx to wildcard domain?

SSL Certificate not updateable

Is there any way to delete duplicate Let's Encrypt certificates from Plesk Admin?

Rebuilt a Wordpress OpenLiteSpeed + Ubuntu 24 droplet and /opt is missing

Issue with Let's Encrypt Certificate on Web App

Encrypted at rest? What are the encryption protocol and key strength used on Digital Ocean?

Best approach to migrate server from droplet to droplet with floating/reserved ip

SSL caddy with droplet

What token should I create for let's encrypt?

Easy Certificate Question

"Failed to validate nameserver records: a non DigitalOcean Name Server was found for [domainname].info domain"

easy cerbot question

Report this

Error message "This Connection Is Not Private"

Related questions

How to change existing certbot/nginx to wildcard domain?

SSL Certificate not updateable

Is there any way to delete duplicate Let's Encrypt certificates from Plesk Admin?

Rebuilt a Wordpress OpenLiteSpeed + Ubuntu 24 droplet and /opt is missing

Issue with Let's Encrypt Certificate on Web App

Encrypted at rest? What are the encryption protocol and key strength used on Digital Ocean?

Best approach to migrate server from droplet to droplet with floating/reserved ip

SSL caddy with droplet

What token should I create for let's encrypt?

Easy Certificate Question

"Failed to validate nameserver records: a non DigitalOcean Name Server was found for [domainname].info domain"

easy cerbot question