Comment on [deleted]
lemmyselfhosted@lemmy.world 11 months agoThank you for the replies. Nginx was causing the issue. I installed but now I face the 526 Invalid SSL certificate error.
I tried putting my API Token in the conf.env and redeply with ./deploy -f but the error persists. Maybe I should somehow manually enter the Cloudflare certificate, but I’m not sure where should I do it.
From where I bought the domain, they do not let me to use their DNS servers to point to anything but their servers, so I used Coudflare for setting up the DNS records for the domain.
When I first opened the https:// on my server after I got it, the nginx had SSL certificate, the connection was secure. I suppose I have to manually do something here, but not sure what.
Im_old@lemmy.world 11 months ago
looking at the install instructions it doesn’t say you have to use CF cert, only the api token in the conf.env file. So if you have done that you should be ok.
I’m curious about the DNS thing from your registrar. If they are the authoritative DNS, even putting the right records in CF won’t make a difference. But maybe you can tell your registrar that CF DNS is authoritative, by creating a SOA DNS record in your registrar, pointing at CF DNS (I can only fnid references to 1.1.1.1 or adam.ns.cloudflare.com).
Looking at the deployment templates it doesn’t say that you have to use ANY certificate. I think caddy generates one (or import one from CF) at deployment. If I was you I’d start from scratch with a new OS installation WITHOUT nginx/apache. Base OS, docker/docker-compose, and run the script again (after you fixed the DNS). If you want to find who is the SOA for your domain I think the command should be
dig @9.9.9.9 SOA youlemmydomain.comThat should answer with the CF DNS you configured.
Also a
dig @9.9.9.9 youlemmydomain.comshould answer with the A records you configured in CF.lemmyselfhosted@lemmy.world 11 months ago
Thank you for the help, I will try it out!