Lunarpages Web Hosting Forum

Author Topic: Let's Encrypt  (Read 65983 times)

Offline rlamprey

  • Newbie
  • *
  • Posts: 1
Re: Let's Encrypt
« Reply #45 on: August 30, 2018, 09:33:19 AM »
I'm looking for an easy way to implement https protocol on a LP addon domain that I have set up but essentially don't currently use.  I would like that domain to hold my luxcal calendar, but initially not much else.  Since I will be the only one using the domain, I don't need to deal with search-engine rankings, shopping-cart security, and the like. Just secure transmission of passwords, calendar data, and the like.

This thread currently ends with a wonderful-appearing, short .htaccess script that MrPhil claims is doing the trick.  I am a novice at this sort of thing and would love to get a simple solution, but I understand that the world is seldom simple. Could someone give me a brief description of what I need to do, and do I need to purchase SSL certificates, etc.?

Much obliged.

Offline MrPhil

  • Senior Moderator
  • Berserker Poster
  • *****
  • Posts: 6429
Re: Let's Encrypt
« Reply #46 on: August 30, 2018, 10:51:28 AM »
My understanding is that Auto-SSL should work OK with an add-on domain. Whether you need to do anything extra to enable it on the add-on domain, I don't know. It did get set up automatically for my subdomain, so presumably it is set up for your add-on.

Test your application(s) with typing in https: instead of http:. You might need to change some configuration file for your application's internal links to use https: instead of http:. If you want your entire site to be under SSL, put the code in the root .htaccess file. You will have to make some adjustments if you have anything but one domain, so you don't overwrite a URL with a different domain name. You also need to find out if your subdomain or add-on domain is changed at some point to primary-domain/sub-or-addon/ format.

If you don't want your whole site to be under SSL, you could leave out the code from /.htaccess and put it in the various applications' subdirectory's .htaccess. If you don't know where to go from here, you could post what the structure is of your site and what should be forced to be under SSL and what should happen to various domains, subdomains, and add-ons. I can try to help out with that. Remember that a [R=301,L] flag sends the revised address back to the visitor's browser and says, "use this instead".
Visit My Site

E-mail Me
-= From the ashes shall rise a sooty tern =-