03-04-2016, 01:58 AM
No. It would appear unter http(s):yourserver.com:port/.wellknown and that is not enough. Letsencrypt requires port 80/443 because these ports require root to bind to. That way they ensure the certificate issuer has root access to the server the domain is running under (that way they make sure not anyone who gets a user account there can issue certificates)
A better way would be just running the letsencrypt client normally, add read access to the key and so on for the user cuberite is running as (with ACL) and symlink the certificate/key (=to the live directory). That way you only have to make sure the ones in live are not outdated and can use them with as many stuff as you want to but still doesn't allow globally readable key
A better way would be just running the letsencrypt client normally, add read access to the key and so on for the user cuberite is running as (with ACL) and symlink the certificate/key (=to the live directory). That way you only have to make sure the ones in live are not outdated and can use them with as many stuff as you want to but still doesn't allow globally readable key