LiveCode Forums.

It says at https://livecode.com/hosting/pricing/ that letsencrypt is available as a free option on livecode hosting.

I've raised 2 support requests asking how I can get this set up, but have never received a reply. Has anybody using livecode hosting managed to get letsencrypt set up for them?

Yes. I have Let´s encrypt certificates installed on two of my hosting accounts.

What i noticed i when communicating with the hosting support is, that some of my request were solved, but i did not get an email about that. The automatic reply always arrived. Maybe the certificates have been already installed and the email about is was just not sent out.
Did you test if the certificates were installed?

Matthias

matthiasr wrote: ↑

Sat Jun 17, 2017 1:19 am

Yes. I have Let´s encrypt certificates installed on two of my hosting accounts.

What i noticed i when communicating with the hosting support is, that some of my request were solved, but i did not get an email about that. The automatic reply always arrived. Maybe the certificates have been already installed and the email about is was just not sent out.
Did you test if the certificates were installed?

Matthias

Hello. Can you please post instructions on how to setup Let's Encrypt certificates on LiveCode Hosting? Do you have it configured for automatic updates?

Thx.

Probably related:

I'm getting the dreaded error 421 response: The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection.

From some research it appears that this is the result of using a single certificate for multiple domains on a server.
Any chance of this getting fixed?

Here's my simple attempt to get the version string text file - it works once, then fails:

@Mark

I tried your example here and get the content always returned:

2.2.7
2021.07.21

Yeah.
It appears to be a timing thing.
I was trying this in conjunction with an http post command, and the post never closes its socket.

So posting content to https://whatever opens port 443.
If you then try to get something from a different https address
you get the 421 error because port 443 is still marked as being in use.

Mark,

i assume you are using a version of Livecode which includes tsNET?
Could you try the following command before doing a post?

tsNetLibUrlReuseConnection false

Well, I was / am trying to make this as generic as possible, so no - just straight libURL calls.

So you are using an LC edition which does not include tsNET or do you unload tsNET before doing posts?

If you are using an LC version which includes tsNET and you do not unload tsNET then even "normal" liburl calls make use of tsNET.

Right.
I've tried this with both a plain Community release and various others.
To be clear, I'm trying for now to stay clear of tsNet for maximum spread, but I may have to forgo that.

I've tried this with both a plain Community release

I am sorry, that was not clear, otherwise i would not have asked again.