Jump to content

Link with letsencrypt.org


Recommended Posts

I think @SnoopGT is asking Byet/iFastNet to include Let's Encrypt in their free hosting; That has been asked before and, as far as I am aware, has been rejected due to incompatibilities between the servers and LE (eg. aes.js blocking Let's Encrypt verification system).

Let's Encrypt is already included in Premium Hosting, so I doubt it is coming to free hosting anytime soon.

Link to post
Share on other sites
  • 2 weeks later...

LE has limitations for verification that would be impossible to implement on free hosting automatically on registration and/or under subdomain names. Depending on how LE works, and the server configuration here, can't users who pay for their own domains and link them to free hosting (which is far more common than the latter for legitimate individuals) have the ability to somehow "temporarily disable" aes.js protection for certain things like the LetsEncrypt validator, and other such things (maybe for 12 hours per month would be a reasonable term)? I recall some time ago (probably 6 months now maybe?) trying to add a TLS certificate for an owned domain through COMODO manually and it didn't have any way to verify ownership that would work.

Given modern steps to ensure your sites are taken seriously on the first hit (regardless of where it's hosted) include having a valid TLS connection, this would be a reasonably good compromise to the suggestion.

On an unrelated note, it is worth mentioning that MySQL on the free hosting is forcing MyISAM for tables right now and won't accept 4-byte characters despite me forcing it to. Something odd is up...

Edited by aerocirno
Link to post
Share on other sites
  • 2 years later...
On 7/3/2019 at 3:20 PM, aerocirno said:

LE has limitations for verification that would be impossible to implement on free hosting automatically on registration and/or under subdomain names. Depending on how LE works, and the server configuration here, can't users who pay for their own domains and link them to free hosting (which is far more common than the latter for legitimate individuals) have the ability to somehow "temporarily disable" aes.js protection for certain things like the LetsEncrypt validator, and other such things (maybe for 12 hours per month would be a reasonable term)? I recall some time ago (probably 6 months now maybe?) trying to add a TLS certificate for an owned domain through COMODO manually and it didn't have any way to verify ownership that would work.

Given modern steps to ensure your sites are taken seriously on the first hit (regardless of where it's hosted) include having a valid TLS connection, this would be a reasonably good compromise to the suggestion.

On an unrelated note, it is worth mentioning that MySQL on the free hosting is forcing MyISAM for tables right now and won't accept 4-byte characters despite me forcing it to. Something odd is up...

No. I've successfully implemented LE for byethost with this tool. A guide is here.

Link to post
Share on other sites

Join the conversation

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

Guest
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...