Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

  • 0 Votes
    4 Posts

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

  • AdGuard Home Wildcard aliases

    Moved Solved AdGuard Home
    0 Votes
    56 Posts

    @ByMynix if you want to stick with Porkbun please email them and link as the post reproducing the issue. You can also cc and we are happy to respond.

  • 0 Votes
    2 Posts

    You could install Cloudron within a subdomain. This way you could do something like for Cloudron itself and * for the Wildcard DNS entry.

  • Bug in adding new domain

    Solved Support
    0 Votes
    19 Posts

    @girish thank you! And thank you again for your prompt help!

  • 0 Votes
    2 Posts

    You can add custom certificates as mentioned in

  • Using my own certificates

    Solved Support
    0 Votes
    8 Posts

    @eivlil01 said in Using my own certificates:

    @girish I'm using the DNS based challenge, but for a wildcard entry.

    Cloudron only supports http based challenge for wildcards, or DNS based challenge but then it creates one entry per app.

    Ah, I see what you are saying now. So you have a wildcard DNS entry pointing to the server but also use DNS automation to get wildcard certs. Indeed, Cloudron does not support that.

  • 0 Votes
    18 Posts

    @girish Yes I did, and the problem with the certificates is now fixed. Thank you!

  • 0 Votes
    5 Posts

    @girish That would be ideal! In fact if that can come in the next couple of months, I'll hold off my own DNS change until that's there. Because the whole "my." doesn't really conform to the standards that people expect when they need to enter in their server names for a mail server. I'd definitely love if Cloudron could use it's own "mail" subdomain and it's own certificate for the mail server portion so that I can still have clients connect to mail.<domain>.<tld> without impact since that's what I have told a dozen or so to do already over the last 1.5 years. 🙂

    And no, the decision wasn't anything to do with Cloudron or DigitalOcean really. My main reason for the move away from DigitalOcean isn't anything to do with Cloudron or DigitalOcean. If you're curious... the decision was mostly for two reasons:

    A movement from both myself and my clients to keep everything (as much as possible) in Canada. And my current DNS provider (LunaNode) has their infrastructure in Canada only (well France too, I believe). It's one of those "shop local" sort of things.

    The DNS provider I currently use has a great feature that I can take advantage of in the future when running a secondary Cloudron server as a mirror image of the first one (waiting for that clustering capabilities in the future, hint hint haha). The advantage is that they have monitoring tools I can use, and based on those monitoring tools they can automatically update DNS records to the other IP address if monitoring detects one of the servers as "down" for whatever reason. To me this is like the health checks in load balancing, but I don't have to pay for load balancing with this solution. 😉 I see this as a further advantage to using LunaNode for the DNS management.

    So yeah, nothing to do with Cloudron or DigitalOcean really, so no worries there. Just a decision made for various reasons (the biggest two above, but also a bit of my own OCD and others haha).

    I will keep my primary domain on DigitalOcean then for now if you think the SSL cert for the mail subdomain would arrive in the next couple of months. 🙂 Because I think that's a fantastic idea, and I think that was something I mentioned or questioned back when I started using Cloudron because I was so surprised that it had to be "my." as that's not something that conforms to the standards of mail server hostnames, and I wanted to keep things more standard for my clients to avoid having to explain non-standard implementations. I say standard loosely here as I realize there's no official standard, but it's more a de-facto one that mail. is the subdomain to use, or imap., etc.

    Hope that helps. 🙂