cloudflared VS ddclient

# Install apt dependencies !apt install dotnet-sdk-7.0 git # Install Clouldflared (not on apt) !wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb !dpkg -i cloudflared-linux-amd64.deb # Download StableSwarmUI !git clone https://github.com/Stability-AI/StableSwarmUI # Download ComfyUI backend %cd /content/StableSwarmUI !mkdir /content/StableSwarmUI/dlbackend %cd /content/StableSwarmUI/dlbackend !git clone https://github.com/comfyanonymous/ComfyUI %cd /content/StableSwarmUI/dlbackend/ComfyUI # Setup ComfyUI !pip install -r requirements.txt

Something like cloudflared would be awesome. https://github.com/cloudflare/cloudflared

if you're on windows, you can install it with the exe: https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-amd64.exe (or https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-386.exe if your using 32bit windows.)

%cd /content/naifu !pip install virtualenv && bash ./setup.sh !curl -Ls https://github.com/ekzhang/bore/releases/download/v0.4.0/bore-v0.4.0-x86_64-unknown-linux-musl.tar.gz | tar zx -C /usr/bin !curl -Lo /usr/bin/cloudflared https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 && chmod +x /usr/bin/cloudflared !/content/naifu/venv/bin/python -m pip install -qq pytorch_lightning==1.7.7

As an alternative to traditional ingress, you can use cloudflared to expose web apps on Cloudflare via encrypted tunnels: https://github.com/cloudflare/cloudflared

It's not an issue anymore. Your main concerns are power and internet stability. Plus, upload speed. The rest can be worked out.

https://www.cloudflare.com/products/tunnel/

https://github.com/cloudflare/cloudflared

https://developers.cloudflare.com/cloudflare-one/connections...

I would suggest a reverse proxy tunnel. There is a great and mostly free one I personally use by Cloudflare. You will need a domain, cloudflare account and install the cloudflared client on your machine. For security you can lock down this tunnel in many ways as cloudflare gives you many many options. Zero trust is a good one to look at if you are wanting to secure what ever you want to expose with a login through google or GitHub.

I shared the same feeling until I gave up on "fixing" nextcloud for external access. Slapped cloudflared tunnel on it. You may have to disable Rocket Loader to get the homepage to work properly but after that it just works.

mariadb: # https://github.com/linuxserver/docker-mariadb/releases image: lscr.io/linuxserver/mariadb:${MARIADB_VERSION:-latest} container_name: nextcloud_mariadb environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - MYSQL_ROOT_PASSWORD=${NEXTCLOUD_MARIADB_ROOT_PASSWORD} - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_PASSWORD=${NEXTCLOUD_MARIADB_PASSWORD} volumes: - ${NEXTCLOUD_PATH}/mariadb:/config security_opt: - no-new-privileges:true restart: unless-stopped labels: - "com.centurylinklabs.watchtower.enable=true" redis: # https://hub.docker.com/\_/redis?tab=tags image: redis:${REDIS_VERSION:-latest} container_name: nextcloud_redis security_opt: - no-new-privileges:true restart: unless-stopped labels: - "com.centurylinklabs.watchtower.enable=true" cloudflared: # https://github.com/cloudflare/cloudflared/releases image: cloudflare/cloudflared:${CLOUDFLARED_VERSION:-latest} container_name: nextcloud_cloudflared_tunnel command: tunnel run environment: - TUNNEL_TOKEN=${CLOUDFLARED_TUNNEL_TOKEN} restart: unless-stopped labels: - "com.centurylinklabs.watchtower.enable=true" watchtower: ## https://containrrr.dev/watchtower/ image: containrrr/watchtower:${WATCHTOWER_VERSION:-latest} container_name: nextcloud_watchtower environment: - WATCHTOWER_CLEANUP=${WATCHTOWER_CLEANUP:-false} - WATCHTOWER_LABEL_ENABLE=${WATCHTOWER_LABEL_ENABLE:-false} - WATCHTOWER_SCHEDULE=${WATCHTOWER_SCHEDULE:-0 0 0 * * *} ## https://pkg.go.dev/github.com/robfig/[email protected]#hdr-CRON\_Expression\_Format volumes: - /var/run/docker.sock:/var/run/docker.sock - /etc/localtime:/etc/localtime:ro restart: unless-stopped

Check your distribution's repos first, but Ddclient doesn’t have an automatic installation procedure. Get the tar-file from https://github.com/ddclient/ddclient/releases and untar it. Copy the perl script to your favorite location (ex. /usr/sbin) and create a

As I recall ddclient is a perl script or some such. It should be relatively easy to just download and build it. https://github.com/ddclient/ddclient/releases

FROM alpine:3.17.3 RUN apk update && apk upgrade RUN apk add git make autoconf automake perl-io-socket-inet6 perl-io-socket-ssl WORKDIR /opt RUN git clone https://github.com/ddclient/ddclient.git WORKDIR /opt/ddclient RUN ./autogen && ./configure --prefix=/usr --sysconfdir=/etc/ddclient --localstatedir=/var RUN make && make VERBOSE=1 check && make install RUN rm /etc/ddclient/ddclient.conf && touch /opt/ddclient.config && ln -s /opt/ddclient.config /etc/ddclient/ddclient.conf RUN chmod 600 /etc/ddclient/ddclient.conf ENTRYPOINT ["/bin/sh"] CMD ["-c", "ddclient; while true; do sleep 3600; done"]

Hello u/porkbunregistrar. I tried to use ddclient with porkbun. I use latest ddclient image from linuxserver.io Here link to dockerhub: https://hub.docker.com/r/linuxserver/ddclient/tags They use version 3.10.0 On the official github repository https://github.com/ddclient/ddclient current version is 3.10.0 also.

So a came accros Inadyn which compared to the current state of DDclient, is being actively maintained. More info here from what i am talking about.

You can use ddclient, it supports a lot of DNS providers: https://github.com/ddclient/ddclient

I did try using ddclient (https://github.com/ddclient/ddclient) before writing my own script but couldnt get it to work on my rpi.

If someone has to deal with dynamic IP addresses and wants to use dynamic DNS as well, there's also the pretty nice ddclient package: https://ddclient.net/

I've been using it with NameCheap pretty successfully for a while now, here's an example of some of the integrations it supports: https://ddclient.net/protocols.html (sadly no DigitalOcean integration as of yet, but this might be of use to others)

You would create one A record and use something like ddclient to update the IP address whenever it changes. Then create as many CNAME records (these are like an alias) as you want and point them to the A record.