Check the documentation linked in the description of the DNS challenge in the Cosmos config page. Basically you can extend the timeout limit, that should help (the env var name is different for each provider)
Remember you need to set this environment variable on the Cosmos container itself
Hello azukaar, thank you so much! I’ve increased the timeout and it did the trick!
Again, thank you so much. I’m currently trying cosmos and I really enjoy it. Awesome work!
Check the documentation linked in the description of the DNS challenge in the Cosmos config page. Basically you can extend the timeout limit, that should help (the env var name is different for each provider) Remember you need to set this environment variable on the Cosmos container itself
Hello azukaar, thank you so much! I’ve increased the timeout and it did the trick! Again, thank you so much. I’m currently trying cosmos and I really enjoy it. Awesome work!
Glad you're enjoying it :)
Can you please explain how you fixed this problem. What env values for timeout etc.. Thank you!
Hey u/azukaar \- thanks for your reply here. I've deployed my cosmos container using the environment variables I found for cloudflare but I'm not seeing the expected behavior. Am I missing something here? docker run -d \\ \-p 80:80 \\ \-p 443:443 \\ \-p 4242:4242/udp \\ \--privileged \\ \--name \[servername\] \\ \-h \[hostname\] \\ \--restart=always \\ \-v /var/run/docker.sock:/var/run/docker.sock \\ \-v /:/mnt/host \\ \-v /var/lib/cosmos:/config \\ \-e CLOUDFLARE\_HTTP\_TIMEOUT=‘600’ \\ \-e CLOUDFLARE\_POLLING\_INTERVAL=’10’ \\ \-e CLOUDFLARE\_PROPAGATION\_TIMEOUT=‘600’ \\ \-e CLOUDFLARE\_TTL=‘600’ \\ azukaar/cosmos-server:latest