Jump to content

Recommended Posts

Posted

It's working now (clear your cache) but you didn't need to set up SSL for your account, AutoSSL is already enabled on Tommy.

Posted

For others who read this, it can take 24 hours for the SSL to start working after you add or change a domain on a Tommy or Ricky account. In addition, the account must allow plain HTTP connections to the .well-known folder which appears in the docroot for the domain (if you use .htaccess or similar to force HTTPS, an exception must be added for this folder or the redirect must be removed).

  • Like 1
Posted

Sorry, I am new to SSL. I am still having trouble to access my domain with "https". May I know how do I allow plain HTTP connections in .well-known folder?

And, the docroot is it I have to go to my domain provider account to do that?

Posted

There's several issues here.

 

First, your .htaccess file is invalid (probably one of those rewrite rules if I had to guess)...

 

Second, you used ASP.NET with SSL. We only supply ASP.NET on HTTP by default. That support can be moved to SSL if you wish, but doing so will break plain HTTP support for your website, as ASP.NET support cannot be enabled on both protocols at the same time.

 

To demonstrate, I renamed your .htaccess file to .htaccess.old so the forced SSL and URL rewriting were disabled, your site now loads: http://bzysharing.com/home.aspx (please use an incognito window or clear your cache beforehand).

Posted

Krydos has to do that for you. ASP.net for an account only can serve one of the protocols at a time. Do you want to do that?

Posted

Honestly, I'm not even sure if our server honors web.config (it's the IIS equivalent to an .htaccess file). The ASP.NET is not running true .NET under IIS/Windows Server, it's actually Mono+Apache on CentOS.  :unsure:

 

Moving this so the ASP.NET can be moved to SSL for you.

Guest
This topic is now closed to further replies.
×
×
  • Create New...