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.com
That should answer with the CF DNS you configured.
Also a dig @9.9.9.9 youlemmydomain.com
should answer with the A records you configured in CF.
As other people said, there is already a process running on port 80. To find what exactly you can use the command
sudo ss -lptn 'sport = :80'
or
sudo netstat -nlp | grep :80
(both require)
Also, what do you mean by
I have SSL pre-isntalled with the server
It’s a self-signed cert or letsencrypt (or similar)?
Looking at the Ubergeek77 method, I can see in the docker-compose that they have specified to use caddy to run on port 80 and 443. So my guess is that you don’t need neither nginx nor Apache (caddy is a reverse proxy as well) . Also, why have you installed both? I guess you selected “web server” during the OS installation.
So remove apache and nginx, and try running the install script again.
I know it’s linux and you never reboot it and yadda yadda, but have you tried rebooting both machines?
For what it’s worth, that’s my fstab entry (it’s mounted with a normal user, which is the same which the containers use). I seem to remember I had to change ownership of the /mnt/nasdownload folder (before the mount) to the user used to mount it.
//192.168.1.10/Download /mnt/nasdownload cifs auto,user,uid=1000,gid=1000,rw,iocharset=utf8,suid,credentials=/root/.smbgringo,file_mode=0770,dir_mode=0770,_netdev,vers=3.0 0 0
And there is the opensource selfhosted implementation of that as well of course! https://github.com/juanfont/headscale
Or with opnsense as well