SSL not loading in incognito mode

[vaishnavav99_WRG]

I am facing issue while loading the site on incognito mode alone. When I try loading http://demtech.com in incognito mode I get error stating

The connection to demtech.com is not secure

You are seeing this warning because this site does not support HTTPS and you are in Incognito mode.

but the site has proper redirections and works fine in normal mode. We are using a certificate from Let's Encrypt for SSL. We have tested this on multiple devices.

My domain is: demtech.com

My web server is (include version): Apache/2.4.52 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu 22.04.1 LTS

My hosting provider, if applicable, is: bluehost

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

[rg305]

Hi @vaishnavav99_WRG, and welcome to the LE community forum

I can't replicate your warning.
If you are still having this issue, what shows?:
ps -ef | grep -i apache | grep -v grep

[vaishnavav99_WRG]

Hey @rg305 ,

Please find the output of ps -ef | grep -i apache | grep -v grep command

root 3855474 1 0 Oct29 ? 00:00:21 /usr/sbin/apache2 -k start
www-data 3944522 3855474 0 03:26 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4152617 3855474 0 11:09 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4152691 3855474 0 11:10 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153100 3855474 0 11:14 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153237 3855474 0 11:16 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153239 3855474 0 11:16 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153291 3855474 0 11:16 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153509 3855474 0 11:19 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153519 3855474 0 11:19 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153521 3855474 0 11:19 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153554 3855474 0 11:20 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 4153556 3855474 0 11:20 ? 00:00:00 /usr/sbin/apache2 -k start
demtech 4153610 4153291 0 11:20 ? 00:00:00 /usr/sbin/apache2 -k start
websauc+ 4153611 4153509 0 11:20 ? 00:00:00 /usr/sbin/apache2 -k start

[rg305]

I see different PIDs running apache:

@vaishnavav99_WRG

root 3855474
demtech 4153610
websauc+ 4153611

Is that expected?
Have you restarted the system?

[vaishnavav99_WRG]

The presence of multiple users running Apache processes is generally normal and expected.
I have restarted the system.

[webprofusion]

Site looks fine now, perhaps you had content that was linked as http instead of https and that has now been fixed. Worth checking the browser console for warnings when you see this type of problem.

[vaishnavav99_WRG]

Hey @webprofusion, thankyou for helping but we are still facing the problem in incognito or private browsing. This is easily replicable in mobile devices.

• Open chrome incognito or safari private browsing .
• search for http://demtech.com/.

this will throw the error, in normal mode the site works as expected.

[webprofusion]

Are you actually browsing to http:// on purpose?

This is just because chrome incognito no longer allows http by default. Your normal site and https redirection is working fine. This behaviour is expected when using chrome incognito because it refuses to load http (it is now https only)

https://support.google.com/chrome/a/thread/297292592/disable-https-first-mode-incognito?hl=en

[vaishnavav99_WRG]

@webprofusion thankyou for the details. We are actually browsing to http:// , as some of the clients reported it. But its happning even if I try to just call the URL "demtech.com".

I expect demtech.com to redirect to https:// it works as expected in normal browsing mode but throws warning in incognito.

[Nekit]

When I try to visit your website with http:// scheme, chrome in incognito mode actually tries to load the https:// version, but times out after precisely 3 seconds with the warning that you show.

Your site is extremely slow to load, it takes 4+ seconds for the First Byte to arrive. You should look into speeding your website up and the warning should go away.