Cloudron Forum

Greetings. Apparently I just fell into same rabbit hole. Im using Cloudron to set up Hetzner VPS with only IPv6 connectivity. Download of cloudron-setup worked well - but execution fails:

##############################################
         Cloudron Setup (latest)
##############################################

 Follow setup logs in a second terminal with:
 $ tail -f /var/log/cloudron-setup.log

 Join us at https://forum.cloudron.io for any questions.

=> Updating apt and installing script dependencies
=> Validating setup token
Could not reach https://api.cloudron.io to complete setup

Is there any reasonable possibilty to work around that? No worries otherwise - then I will buy additional IPv4 from Hetzner, no big deal. Thanks in advance.

Hi @girish, hi @nebulon. Many thanks for perfect explanation, hope to have got that. Have now configured as explained above and apex domain does now also produces perfectly valid cert signed by LE.

Many thanks also for impressingly quick response during weekend - appreciated.

Greetings!

I am pretty new to Cloudron - therefore first of all a very big thank you for the incredible valuable product, highly appreciated.

If have just setup an instance of NextCloud at 'nxtcld.drbigman.org' - with domain 'drbigman.org' provided by porkbun. So far everything is working perfectly fine.

However, when accessing base domain 'drbigman.org', a security warning is displayed and self-signed certificate (as provided for setup of my.drbigman.org from Cloudron) needs to be accepted.

This issue is somewhat similar to the one described at https://forum.cloudron.io/topic/8270/lets-encrypt - however, in my case there is not even any web service configured for the base domain.

As already mentioned: not a real problem at all. Besides showing a warning when accessing base domain, other effects include e.g. that SSL Server Test (https://www.ssllabs.com/ssltest/) will complain about a certificate mismatch when checking base domain (checking 'my.drbigman.org' returns perfect A+ for both IPv4/6).

However, when I checked the Let'sEncrypt wildcard certificate as correctly used for 'nxtcld.drbigman.org', I noticed that it appears to only be issued for (wildcard) domains *.drbigman.org - but not in addition for 'drbigman.org', correct?

IIRC, wildcard '.drbigman.org' does not include base domain 'drbigman.org' itself - but only subdomains. Therefore similar 'plain vanilla' certificates are frequently issued for '.drbigman.org, drbigman.org' - so that they also apply for the base domain.

As recommended in ticket mentioned above, I have also renewed all certs thru dashboard - however, problem remains the same.

Is there a certain reason, why LE cert is not issued for '*.drbigman.org, drbigman.org' - or may I have configured something incorrectly?

Many thanks in advance for your support and advice.