Jump to content

Recommended Posts

Posted

Hi !

 

I am attempting to migrate https://ipworld.in to heliohost. My primary domain at heliohost is life.heliohost.org

 

1) At heliohost I have created a directory public_html/ipworld  and put various files etc. there and configured database etc. Via https://life.heliohost.org/ipworld the site is accessible.

 

2) Have changed yesterday DNS for ipworld.in to point to ns1.heliohost.org and ns2.heliohost.org.

 

3) Created an add-on domain ipworld.in via c-panel at heliohost .  Document root for the domain is public_html/ipworld .

 

4) Using SSL/TLS manager in C-panel, installed ssl certificate for ipworld.in

 

Yet now when I try to access https://ipworld.in through a browser it shows :

===

Ahoy! You're seeing this page because you've reached a website on our service that's not configured to accept secure connections (HTTPS).

If you're a visitor, try visiting this site again, removing the "https" in front of the website domain. Please note that your connection to this user's website will not be secure.

If you're the webmaster of this site, we recommend you take a few minutes to set up SSL so your visitors can connect securely. You can do this from your control panel. If you need assistance, please visit our support forums or Wiki.

Thanks for choosing HelioHost!

Sincerely,

=====

 

The 'set up SSL' link above points to https://wiki.helionet.org/Installing_a_Let%27s_Encrypt_SSL_Certificate which shows a 'Page not found' error.

 

Please advise what am I doing wrong and how to rectify it. Thank you.

 

 

 

 

Posted

Please clear your cache. SSL on that domain works fine for me.

 

As for that link, yeah, we upgraded the wiki and all the documentation links broke.

Posted

It's related to how you have the software for your website configured. The software is likely configured to expect the .in domain and no folder in the path, so using the heliohost.org subdomain and having the subfolder in the path breaks it.

 

It's quite common for a site to not work correctly when accessed like this. Simply access it as it's intended and you're good. You might want to toss an index file in the root of public html that redirects to the correct domain, even if only so the directory listing isn't visible.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...