Point arbitrary domains to a cloudron app?
-
How can I get a Cloudron app to receive requests without adding an alias?
For example, I would like to setup
cname.myapp.cloudron.domainand allow users of the app to point their domains there (i.e. a user can make aCNAMErecord forsub.theirsite.comtocname.myapp.cloudron.domain).In some way I'm asking an old question but instead of static files I want to deploy a node.js app that responds dynamically.
-
Technically, how will cloudron serve up a secure site without even knowing a domain? It won't have the certificate for this unknown dynamic domain.
@joseph said in Point arbitrary domains to a cloudron app?:
Technically, how will cloudron serve up a secure site without even knowing a domain? It won't have the certificate for this unknown dynamic domain.
True. I think I'm trying to emulate how PaaS platforms let you add a domain with https, but doing it at the app level instead of the platform (cloudron) level. I was thinking yesterday maybe the Cloudron API can add them and provision certificates behind the scenes.
-
maybe the Cloudron API can add them and provision certificates
But for that you need to add the domain to Cloudron in general and when/if a customer changes their dns settings to have the given domain no longer point to you, you will see failures to generate new certificates.
At my work we also have a service where users can point domains via cname to our service (to enable auto discover for mail clients). What we are using for this is a caddy based webserver doing on demand tls, which then proxies the requests to our actual app.
You can read more about it at https://caddyserver.com/on-demand-tls
-
Not sure if I get the whole point, but is there a reason to not make that domain known by Cloudron? You can add it via the "manual" provider if you anyways manage those DNS records externally. If you add it, you can just set those domains in the app settings in your Cloudron dashboard and things should work as you want.