You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only one DNS validation can be set up per Swag container
Ideally multiple DNS of multiple providers but minimally both HTTP and DNS validation of one provider at the same time.
Reason for change
In the case we would like to use different DNS validation on the same server, there will be issues running multiple Swag containers at once with conflicting ports, unless I get multiple IP for the server
The thing here is that, say for example, we are using multiple CDN providers for different domains running under the umbrella of Swag. For example, Cloudflare and Bunny
. Some of these only let you use their CDN if you use their DNS.
Moreover, let's say we have a domain using cloudflare and a subdomain of another domain in the same server. We cannot use DNS validation for the CF one and HTTP for the subdomain
I'm being inspired by the Caddy system where I have some caddy servers with this kind of configs (but I've always prefered to stick to nginx)
Proposed code change
No response
The text was updated successfully, but these errors were encountered:
Is this a new feature request?
Wanted change
Currently, only one DNS validation can be set up per Swag container
Ideally multiple DNS of multiple providers but minimally both HTTP and DNS validation of one provider at the same time.
Reason for change
In the case we would like to use different DNS validation on the same server, there will be issues running multiple Swag containers at once with conflicting ports, unless I get multiple IP for the server
The thing here is that, say for example, we are using multiple CDN providers for different domains running under the umbrella of Swag. For example, Cloudflare and Bunny
. Some of these only let you use their CDN if you use their DNS.
Moreover, let's say we have a domain using cloudflare and a subdomain of another domain in the same server. We cannot use DNS validation for the CF one and HTTP for the subdomain
I'm being inspired by the Caddy system where I have some caddy servers with this kind of configs (but I've always prefered to stick to nginx)
Proposed code change
No response
The text was updated successfully, but these errors were encountered: