Tunnels are bit more of a black box than standard https traffic through their proxy. There are pros and cons to each, but since I'm not CGNAT'd I stick with their proxy DNS.
Is the load_balancer mandatory ? Because I have only one IP and for this reason I didn't create the load_balancer section in the conf file but when I execute the script I see this error: Traceback (most recent call last): File "/home/pi/docker/cloudflare-ddns/cloudflare-ddns.py", line 316, in updateIPs(getIPs()) File "/home/pi/docker/cloudflare-ddns/cloudflare-ddns.py", line 248, in updateIPs updateLoadBalancer(ip) File "/home/pi/docker/cloudflare-ddns/cloudflare-ddns.py", line 191, in updateLoadBalancer for option in config["load_balancer"]: ~~~~~~^^^^^^^^^^^^^^^^^ KeyError: 'load_balancer'
I’m definitely not knowledgeable enough to be messing with any of this yet, but I’m subbing to you so that when I do become proficient enough to mess with it I can come back and follow along
I would like to congratulate you on your excellent work, I really like your videos. I would like to ask if possible if you could record a video explaining how to run nginx-proxy-manager together with traefik inside portainer, honestly this is an extreme headache for me and I really need to learn, I believe this is the question of several followers. Thanks in advance.
if there isn't anything that bypasses cloudflare from the internet then I think the arrows should just go from the internet to cloudflare to your modems.
Did you update your image to only support `arm` based processors recently? I originally set everything up using your image on an `amd64` machine but after making some changes and trying to restart the container I run into the below error. I only see a `:latest` tag on Dockerhub. I switched back to the `oznu/cloudflare-ddns` image and it seems to be running fine. `The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v2) and no specific platform was requested`
Just out of curiosity, is there a benefit to using the loadbalancer in cloudflare over just using standard DDNS updating of A records and using the Unifi WAN failover? Or just wanted to play around with the Cloudflare loadbalancing? Ive yet to be able to test it, but in theory if primary WAN goes down and you fail over to secondary long enough the DDNS container will just automatically fetch your secondary WAN IP and update your A records according.
thx for the video, i'm in Europe and never hear or see an ip provide by ISP change O_o is that a think where you live thant your ip change during the year O_o that insane
I'm getting an "error reading config.json" message, and I have no idea why. I'm sure it's something simple and stupid that I've done (it always is), but I can't figure it out.
@@RaidOwl thanks for the reply, it’s funny you mention that. I was wondering if I should leave it in, but I wasn’t sure how to comment it out because I’m not using a load balancer. Think I just need “” for blank?
