-
I installed the docker and found it could not be used due to it only access 443 port for domain, bu for most of homer user, ISP blocked the port 443 and 80. some SSL certification could be certified by HTTP-01 challenge. so could add the function(DNS-01) for it? thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
This comment has been hidden.
This comment has been hidden.
-
Honestly I don't think this is worth being implemented as you can already configure the dns challenge using a reverse proxy. Here is a general documentation on using it behind a reverse proxy: https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md And here is how to configure caddy (as your reverse proxy) to use the dns challenge: https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148 |
Beta Was this translation helpful? Give feedback.
-
OK, Hope the new feature could solve it, or the reverse proxy could have optional solution, so we can use self-defined proxy to solve it. otherwise it can not go to next step fully. thanks! |
Beta Was this translation helpful? Give feedback.
-
I am adding some documentation for this with #876 |
Beta Was this translation helpful? Give feedback.
I am adding some documentation for this with #876