WAN IP requirements for Lets Encrypt - Error:


#1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: transfer.btwcompany.co.nz

I ran this command: Liquid Files > config > Enable Let’s Encrypt

It produced this output: Could not retrieve random token from transfer.btwcompany.co.nz. The most likely cause of this is that http://transfer.btwcompany.co.nz/ is not pointing to the LiquidFiles system. If you want to use Let’s Encrypt Certificates with LiquidFiles, you will need to permanently configure http://transfer.btwcompany.co.nz to point to your LiquidFiles system.

My web server is (include version): Liquid Files v3.2.14

The operating system my web server runs on is (include version): Linux

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): NO


#2

Does LiquidFiles provide a more detailed error message? What was it checking?

That error message isn’t from Let’s Encrypt – LiquidFiles might have received an error from Let’s Encrypt and changed the message, or it might have been performing its own check.

You might have better luck asking on LiquidFiles’s forum – there may not be many people here who know how its client works.

I wonder if it’s a problem that http://transfer.btwcompany.co.nz/ redirects to https://transfer.btwcompany.co.nz:443/ – including the port in the URL is valid but not necessary, and maybe some things react badly.


#3

Sounds like the check of one of the 3rd party clients to me. Didn’t dehydrated do such a check?

In any case, the error is from the client at LiquidFiles.