Jump to content

Recommended Posts

Posted (edited)

Any idea why I would get this error message (Chrome only) when accessing the home page of my website?  And there is no "default.html" file in the public directory (I've checked). Error doesn't appear when using Firefox or Edge.  

This is when only entering only hydroxystudy.info

Sure, if I enter www.hydroxystudy.info it works.  But not everyone will do this.

Upon further testing, it appears the problem is related to Chrome automatically redirecting to https (secure).  Firefox and Edge don't do that.  However, there seems to be some interaction with TCM as well - such that the error message would be displayed.

chrome error.jpg

Edited by 442GlenwoodAvenue
Posted

Hi,

I had tried to recreate the error by browsing http://hydroxystudy.info/ in chrome browser and website just loads fine for me. You can check the attached screen shot to verify. So this might be just a local browser cache issue on your end. Try clearing complete browser cache in Google chrome and re-try again. You can refer below given documentation for help in clearing browser cache in Google chrome and make sure you only clear cache and not cookies.

https://support.google.com/accounts/answer/32050?hl=en&co=GENIE.Platform%3DDesktop

 

 

site.png

Posted

Hi,

Also Chrome might force to secure url https://hydroxystudy.info/ but since you do not have an SSL certificate installed this should be also a reason. Noe that you can enable free SSL certificate we are providing. Free SSL provided by Let's Encrypt which you can install for your account by logging into cPanel and traversing to Security - Let's Encrypt. But note that forcing  secure page on your website is dependent on website design and once you have enabled free SSL certificate you will have to contact your web developer for configuring your website to use and force SSL on it. Your website is a Wordpress installation so you can take advantage of any Wordpress predefined plugins specific for this purpose like WP Force SSL or Really Simple SSL.

 

Posted

OK, I've updated to https. That seems to have taken care of the issue. Should have done that a long time ago. It used to be more complicated a few years ago when I looked into it. 

It's gotten easier over the years.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...