techno-tim/techno-tim.github.io

Open Source, Community Driven, Documentation for Techno Tim YouTube Videos/ Complete with examples for all your copy pasta needs!

techno-tim.github.io's Issues

traefik-config.yaml cannot be used with k3s local-path?

Seems I'm affected by the error mentioned in your comments: level=error msg="The ACME resolver \"cloudflare\" is skipped from the resolvers list because: unable to get ACME account: open /certs/acme.json: permission denied" when not using the init-container.

Problem is, when using the init-container I face other errors that prevent a successful deployment that I'm struggling to sort out.

When using your manifests verbatim, my traefik pod cannot mount the PVC as k3s local-path and Mayastor NVMF (the two storageclasses available to my cluster) do not support the ReadWriteMany access mode as listed in your traefik-config....

  accessModes:
  - ReadWriteMany
  - ReadWriteOnce

If I comment out the init-container, everything comes up but then I get the error at the top about permissions denied.

Some things I've tried...

1. Limiting the configfile to either RWM or RWO access modes only
2. Changing the command in the busybox init-container from chmod -Rv 600 /certs/* to chmod -Rv 600 certs
3. Update busybox container to 1.32.0
4. Add storageclass to the PVC to use either local-path or nvmf (mayastor)
5. Officially complain on github ;)

Thanks for any assistance/ideas you can provide!

Rancher setup tutorial (Docker, Rancher, Kubernetes, Minecraft)

Dear Tim,

Thank you for the awesome video. I suspect that the instructions in the video may be outdated and not possible to reproduce anymore. I posted a comment on YouTube for that video with the name hakovatube, and I don't want to state the same thing here. Briefly, I tried 3 OSes in VMs (CentOS 8.2, Ubuntu 20.10 and Ubuntu 20.4), spent 2 nights just to be able to add a cluster with no avail. I tried publishing ports to 9090 and 9091 instead of keeping them on 80 and 443, which didn't have any positive impact, and in some cases, rancher became unreachable.The curl script didn't work for any of the above-mentioned OSes, I ended up installing docker from release repositories. I found out that docker from snap requires user's home folder to be the location of persistent settings and therefore should not be used. I may still be missing something but please feel free to start up a new VM and try to reproduce your steps in this video; I suspect that you would find that it is not reproducible anymore.

Thanks.

portainer-2-kubernetes: Failed to start node 'k3d-portainer-server-0': Try to start it manually

Thanks for the videos and instructions on github. I followed the instructions and trying to setup portainer 2.0 with kubernetes on a debian 10 VM (parent host is proxmox) but it keeps failing to start note at the create cluster step

k3d cluster create portainer --api-port 6443 --servers 1 --agents 1 -p 30000-32767:30000-32767@server[0]

After hanging for 10+ minutes here is the result and commands prior to the step:

x@dock:~$ sudo mv ./kubectl /usr/local/bin/kubectl
x@dock:~$ kubectl version --client
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:28:09Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
x@dock:~$ curl -s https://raw.githubusercontent.com/rancher/k3d/main/install.sh | bash
curl: (7) Failed to connect to github.com port 443: Connection timed out
Failed to install k3d
        For support, go to https://github.com/rancher/k3d.
x@dock:~$ curl -s https://raw.githubusercontent.com/rancher/k3d/main/install.sh | bash
Preparing to install k3d into /usr/local/bin
k3d installed into /usr/local/bin/k3d
Run 'k3d --help' to see what you can do with it.
x@dock:~$ k3d cluster create portainer --api-port 6443 --servers 1 --agents 1 -p 30000-32767:30000-32767@server[0]
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-portainer'
INFO[0000] Created volume 'k3d-portainer-images'
INFO[0001] Creating node 'k3d-portainer-server-0'
INFO[0005] Pulling image 'docker.io/rancher/k3s:v1.20.0-k3s2'
INFO[0045] Creating node 'k3d-portainer-agent-0'
INFO[0050] Creating LoadBalancer 'k3d-portainer-serverlb'
INFO[0054] Pulling image 'docker.io/rancher/k3d-proxy:v4.0.0'
INFO[0074] Starting cluster 'portainer'
INFO[0074] Starting Node 'k3d-portainer-server-0'



ERRO[0512] Failed to start node *'k3d-portainer-server-0'
WARN[0512] Failed to start node 'k3d-portainer-server-0': Try to start it manually
INFO[0512] Starting Node 'k3d-portainer-agent-0'
INFO[0516] Starting Node 'k3d-portainer-serverlb'
WARN[0537] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0541] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0541] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0545] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0546] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0546] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0547] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0549] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0550] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0550] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0551] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0551] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0552] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0552] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0553] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0553] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0554] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0554] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0559] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0559] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0560] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0560] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0561] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0561] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0562] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0562] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0563] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0563] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0564] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0564] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0565] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0565] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0566] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0566] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0567] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0568] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0568] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0569] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0569] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0570] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0574] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0574] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0575] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0575] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0576] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0576] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0577] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0577] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0578] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0578] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0579] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0579] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0580] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0580] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0581] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0581] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0582] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0582] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0583] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0583] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0584] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0584] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0585] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0585] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0586] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0586] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0587] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0587] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0588] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0589] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0589] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0590] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0590] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0591] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0591] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0592] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0592] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0593] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0593] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0594] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0594] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0595] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0595] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0596] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0596] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0597] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0597] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0598] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0601] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0601] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0602] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0602] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0603] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0603] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0604] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0604] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0605] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0605] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0606] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0606] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0607] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0607] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0608] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0608] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0609] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0609] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0610] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0610] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0611] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0611] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0612] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0612] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0613] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0613] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0614] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0614] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0615] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0615] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0616] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0616] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0617] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0618] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0618] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0619] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0619] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0620] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0620] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0621] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0621] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0622] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0622] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0623] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0623] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0624] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0624] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0625] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0625] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0626] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0626] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0627] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0627] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0628] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0628] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0629] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0629] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0630] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0630] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0631] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0631] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0632] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0632] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0633] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0633] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0634] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0634] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0635] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0635] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0636] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0636] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0637] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0637] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0638] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0638] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0639] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0639] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0640] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0640] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0641] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0641] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0642] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0643] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0643] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0644] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0644] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0645] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0645] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0646] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0646] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0647] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0647] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0648] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0648] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0649] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0649] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0650] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0650] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0651] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0654] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0654] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0655] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0655] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0656] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0656] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0657] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0657] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0658] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0658] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0659] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0659] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0660] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0660] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0661] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0662] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0662] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0663] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0663] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0664] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0664] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0665] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0665] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0666] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0666] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0667] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0667] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0668] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0668] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0669] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0669] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0670] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0670] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0671] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0671] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0672] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0672] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0673] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0673] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
WARN[0674] Node 'k3d-portainer-serverlb' is restarting for more than a minute now. Possibly it will recover soon (e.g. when it's waiting to join). Consider using a creation timeout to avoid waiting forever in a Restart Loop.
^C

I'm unsure as to how to triage this - are there any special settings that must be enabled on the VM itself?

Update to docker-rancher-kubernetes

A potentially better link for finding the latest Rancher version may be: https://github.com/rancher/rancher/tags

The Rancher team has begun using a lot of tags on the original page: https://hub.docker.com/r/rancher/rancher/tags?page=1&ordering=last_updated

Wrong readme file for Windows Developer Setup

The readme file in the forlder for Windows Developer Setup is for "How to Virtualize Your Home Router / Firewall Using pfSense", which is obviously not the right one.
Would love to have the right commands/written walkthrough of the Windows developer setup.

AI Training Script for running TensorFlow container

Hi Tim, how are you?

I've just completed this tutorial on my homelab and worked like a charm!!!

Nevertheless, there is something missing from de video and for the documentation which is actually how to call the script to initialized the AI training that you mentioned on video (at 6:51 min).

I've looked at dockerhub and there is no details on how to run this image.

I'll really appreciate you share the details.

Thanks in advance!!!

single node rancher on docker installation problem - container is in looped restart

Tim,

the

docker run -d --restart=unless-stopped -p 9090:80 -p 9091:443 --privileged -v /opt/rancher:/var/lib/rancher --name=rancher_docker_server rancher/rancher:latest

command instances a container that is in a constant restart loop. there is some noise about this on the internet; but with no clear solution. any insights how to mitigate?

Kind Regards,

Michael Fene'

Transmission route does not work via config.yml (external service) or Internal (Traefik's network)

In Config:
...
transmission:
entryPoints:
- "https"
rule: "Host(transmission.rexrd.com)"
middlewares:
- default-headers
- addprefix-transmission
tls: {}
service: transmission
....

#endregion
middlewares:
addprefix-transmission:
addPrefix:
prefix: "/transmission/web/"
https-redirect:
redirectScheme:
scheme: https
authelia: # This is NEW
forwardAuth:
address: "http://authelia:9091/api/verify?rd=https://auth.example.com"
default-headers:
headers:
frameDeny: true
sslRedirect: true
browserXssFilter: true
contentTypeNosniff: true
forceSTSHeader: true
stsIncludeSubdomains: true
stsPreload: true
stsSeconds: 15552000
customFrameOptionsValue: SAMEORIGIN
customRequestHeaders:
....

typo in first 13 things video doc

there is a typo in the apt commands for updating system software on the first 13 things video documentation. it says apt-apt

a suggestion for timezone config is also to use dpkg-reconfigure tzdata for a menu based selection of time zones

Reducing Downtime when changing configs

You can/should add the following to your docker-compose files for each container to be able to change configuration with minimal downtime of the functionality provided by the container:

deploy:
  mode: replicated
  replicas: 1
  update_config:
    order: start-first		   # get new container running first before removing old, for less downtime
  rollback_config:
    order: start-first		   # get new container running first before removing old, for less downtime
  placement:
    constraints:
      - node.role == manager  # or e.g. global
  labels:
     "Your e.g. Traefik labels here. Note the indentation of the tag 'labels:', under deploy"

SSL Everything - Error Message

time="2022-03-22T13:53:03Z" level=info msg="Configuration loaded from file: /traefik.yml" time="2022-03-22T13:53:03Z" level=error msg="Cannot start the provider *file.Provider: field not found, node: headers"

How do I fix the above error messages? I used the configurations you posted in your video.

Website

My website is not working

techno-tim.github.io/feed.xml

Line 51 in f693b6a

{% include no-linenos.html content=post.content %}

The repository can't find no-linenos.html in _includes but it's working for your repository.

My repository is linked here.

Multiple VLANs on bridge

Hi,
this is a question related to "first-11-things-proxmox".
You provide a config with multiple VLANs on a single bridge (+ bond).

Question:
What must be configured to get dedicated network (subnets) on a VLAN, e.g.
VLAN 2
192.168.2.0/24
VLAN 3
192.168.3.0/24
VLAN 10
192.168.10.0/24
and a working routing if the main network of Proxmox Server is in 192.168.1.0/24?

Or will this only work with OVS?

THX

Traefik Config Https Redirection

Issue: Https Redirection doesn't work as per the config.yml:

http:
routers:
proxmox:
entryPoints:
- "https"
rule: "Host(proxmox.example.com)"
middlewares:
- authelia
- default-headers
tls: {}
service: proxmox
truenas:
entryPoints:
- "https"
rule: "Host(truenas.example.com)"
middlewares:
- authelia
- default-headers
tls: {}
service: truenas
nextcloud:
entryPoints:
- "https"
rule: "Host(nextcloud.example.com)"
middlewares:
- default-headers
tls: {}
service: nextcloud
#endregion
#region services
services:
proxmox:
loadBalancer:
servers:
- url: "https://192.168.177.11:8006"
passHostHeader: true
truenas:
loadBalancer:
servers:
- url: "https://192.168.177.5"
passHostHeader: true
nextcloud:
loadBalancer:
servers:
- url: "https://192.168.177.9:4430"
passHostHeader: true

#endregion
middlewares:
https-redirect:
redirectScheme:
scheme: https
authelia: # This is NEW
forwardAuth:
address: "http://authelia:9091/api/verify?rd=https://auth.example.com"
default-headers:
headers:
frameDeny: true
sslRedirect: true
browserXssFilter: true
contentTypeNosniff: true
forceSTSHeader: true
stsIncludeSubdomains: true
stsPreload: true
stsSeconds: 15552000
customFrameOptionsValue: SAMEORIGIN
customRequestHeaders:
X-Forwarded-Proto: https
secured:
chain:
middlewares:
#- default-whitelist

Thanks for the video walkthrough.

13 things video addition

to disable auto-rebooting edit /etc/apt/apt.conf.d/50unattended-updrades

uncomment this line:
//Unattended-Upgrade::Automatic-Reboot "false";

There is an official way for regenerating a machine-id

I was bumping into the same issue when cloning VMs in Proxmox VE. After a lot of searching I found a way to generate a new machine-id without rebooting the VM.

https://wiki.debian.org/MachineId

rm -f /etc/machine-id /var/lib/dbus/machine-id
dbus-uuidgen --ensure=/etc/machine-id
dbus-uuidgen --ensure

This generates a new machine id at /etch/machine-id and /var/lib/dbus/machine-id without rebooting.
https://github.com/techno-tim/youtube-videos/tree/master/first-11-things-proxmox could be updated to use the "correct" way of resetting a machine-id?

TLD issue with rancher on k3s

Please add a note at the start that if you have a .local for TLD as your homelab local domain Rancher will not allow it in the URL and will need another TLD on the DNS server setup for it.

Advertise RSS Feed

You should put somewhere on your website (maybe on the sidebar next to the socials) that the RSS feed is at /feed.xml. A lot of techies use RSS daily and advertising it would be a plus.

-reese

Traefik - Missing command

Currently, the "Traefik" portion of the command list has the following commands, in order:

mkdir traefik
cd traefik
mkdir data
touch acme.json
chmod 600 acme.json
touch traefik.yml

In the video, you show yourself going into ./traefik/data to perform the following commands:

touch acme.json
chmod 600 acme.json
touch traefik.yml

Current command structure should be:

mkdir traefik
cd traefik
mkdir data
cd data
touch acme.json
chmod 600 acme.json
touch traefik.yml

how do you get the analytics ID (link below)

techno-tim.github.io/_config.yml

Line 64 in f693b6a

id: 'G-NZ5V7DM8F5' # Fill with your Google Analytics ID

Traefik acme client invalid config

I was following the new Traefik 2, k3s, Rancher guide and i found a acme client issue with the traefik-chart-values.yml. The CF_DNS_API_TOKEN Needed a change to CF_API_KEY

Can't get Traefik2 dashboard working on k3s

Issue: Can't get Traefik2 dashboard working on k3s and rancher

Background:

• I am following Tim's guide listed here -> https://techno-tim.github.io/posts/k3s-traefik-rancher/
• When choosing kubernetes ingress or ingressroute option, can't get the dashboard working

Potential Solution:

• In the https://github.com/techno-tim/techno-tim.github.io/blob/master/reference_files/traefik2-k3s-rancher/config/traefik-dashboard-ingressroute.yml file, annotation needs to be added for ingressClass.

Please comment or let me know if this is not necessary or if I am making a mistake somewhere.

Authelia

In the authelia configuration.yml you need to update this:

host: 0.0.0.0
port: 9091
log_level: debug

to this:

server:
host: 0.0.0.0
port: 9091

log:
level: debug

Incorrect CIDR values for Private Networks (RFC 1918)

Tim,

File: https://github.com/techno-tim/techno-tim.github.io/blob/master/reference_files/authelia-traefik/traefik/config.yml
Problem Section:
default-whitelist:
ipWhiteList:
sourceRange:
- "10.0.0.0/24"
- "192.168.0.0/16"
- "172.0.0.0/8"

Reference: https://en.wikipedia.org/wiki/Private_network
See the column labelled : Largest CIDR block (subnet mask)

If I'm correct, you have several mistakes in the provided whitelist, in that you are enabling a lot more than the RFC 1918 (Private Networks) range, which would be:

• 10.0.0.0/8
• 172.16.0.0/12
• 192.168.0.0/16
  And maybe that was the intent, but the ranges do overlap the private network ranges, so I thought I point that out.

Regards,
Peter

SSL Everything - Incomplete

How this is working? I was able to follow your instructions and everything works but why it is not clear what is going on to me.

This seems to be only for local webservers inside the firewall. You say that things come in through the reverse proxy, but only set up a docker network called proxy that is accessible by the local lan. How does letsencrypt connect to verify an internal webserver without a connection to the internet? Is the local lan dns available publicly? Does the service.local.domain.com resolving publicly as a private ip? When I look it up I see a uuid.cfargotunnel.com with a ipv6 address, although I can not reach the service (maybe ufw). Is traefik creating a cloudflared tunnel somehow? Doesn't acme need to verify the website is publicly available? This is what is confusing to me.

When you say "how do we rout an external service" can you clarify external to docker, but it is still internal to lan as external is typically referred to as public internet. The reason for this ticket is that you did not show how this works with external public dns/ip that is internet available website, so I feel like this video is incomplete. The proxy docker external network appears it would mean that it can reach local lan but can it reach ouside? Is there additional steps needed such as setting up cloudflared or punching holes through a firewall to traefik for external connections to finish this project?

I can't find many good articles on Traefik config and their documentation is not great. Traefik doesn't seem to have any GUI settings and is only a dashboard for what is set in the docker compose files, so it's usefulness seems to me to be very limited. Maybe there is a more useful product that doesn't need so many docker configurations. Maybe Caddy, HAProxy, or Nginx Proxy Manager could be explored in a future video.

I also suggest creating variables in your docker files as that would make things much simpler and less confusing. I appreciate your video as it approaches a very complicated topic succinctly. REF: https://www.youtube.com/watch?v=liV3c9m_OX8

Update to rancher-2-upgrade-backup-restore

Two commands are missing the template text:

Change:
docker create --volumes-from <RANCHER_CONTAINER_NAME> --name rancher-data rancher/rancher:<RANCHER_CONTAINER_TAG>
to:
docker create --volumes-from <RANCHER_CONTAINER_NAME> --name rancher-data- rancher/rancher:<RANCHER_CONTAINER_TAG>

And change:
docker run --volumes-from rancher-data -v $PWD:/backup busybox tar zcvf /backup/rancher-data-backup-<RANCHER_VERSION>-.tar.gz /var/lib/rancher
to:
docker run --volumes-from rancher-data- -v $PWD:/backup busybox tar zcvf /backup/rancher-data-backup-<RANCHER_VERSION>-.tar.gz /var/lib/rancher

Thanks again!

Minecraft data volume backwards

update docs

Promtail config for journald logging, Podman considerations

Hi Tim,

This has been a fantastic resource for getting grafana/loki deployed in my environment! Many thanks!

Fedora doesn't configure journald to log files under /var/log so an additional job in the promtail-config.yml may be needed to scrape the journal files:

- job_name: journal
  journal:
    max_age: 12h
    labels:
      job: systemd-journal
    path: /var/log/journal
  relabel_configs:
    - source_labels: ['__journal__systemd_unit']
      target_label: 'unit'
    - source_labels: ['__journal__hostname']
      target_label: 'hostname'

This also adds the "hostname" label so you can distinguish if you've got multiple hosts sending journald logs to loki.

There are additional volumes to pass into the promtail container as well:

/run/log/journal:/run/log/journal
/etc/machine-id:/etc/machine-id

For those trying to do this with Podman on Fedora I found that loki and grafana can be run as non-root user in a pod with promtail running separately as root, using the public loki port.

acme not working with Traefik config files from your setup.

docker logs -f traefik
time="2021-05-11T16:51:15Z" level=info msg="Configuration loaded from file: /traefik.yml"
time="2021-05-11T16:51:15Z" level=error msg="The ACME resolver "cloudflare" is skipped from the resolvers list because: unable to get ACME account: permissions 640 for acme.json are too open, please use 600"
time="2021-05-11T16:51:15Z" level=error msg="Cannot start the provider *file.Provider: error reading configuration file: /root/docker/traefik/config.yml - open /root/docker/traefik/config.yml: no such file or directory"
time="2021-05-11T16:51:17Z" level=error msg="the router traefik-secure@docker uses a non-existent resolver: cloudflare"
^C
root@r720-photon [ ~/docker/traefik ]# chmod 600 data/acme.json
root@r720-photon [ ~/docker/traefik ]# docker-compose up -d --force-recreate
Recreating traefik ... done
root@r720-photon [ ~/docker/traefik ]# docker logs -f traefik
time="2021-05-11T16:52:06Z" level=info msg="Configuration loaded from file: /traefik.yml"
time="2021-05-11T16:52:06Z" level=error msg="The ACME resolver "cloudflare" is skipped from the resolvers list because: unable to get ACME account: invalid character '-' in numeric literal"
time="2021-05-11T16:52:06Z" level=error msg="Cannot start the provider *file.Provider: error reading configuration file: /root/docker/traefik/config.yml - open /root/docker/traefik/config.yml: no such file or directory"
time="2021-05-11T16:52:08Z" level=error msg="the router traefik-secure@docker uses a non-existent resolver: cloudflare"
^C

Configuring Traefik for Cloudflairs DNS Proxy

Hey All

Following Tim's tutorial I've got everything working great, however, I now want to use Cloudflare's DNS proxy to mask my server's IP in the cloud. I am wondering how to configure Traefik for this. I am guessing that a new entry point is needed in the config.yml is that correct?

K3s installation issues + fixes

From my YouTube comment: https://www.youtube.com/watch?v=UoOcLXfa8EU&lc=UgwZL42zHoDLwqG-XOd4AaABAg

Can't bootstrap due to different token

Check the release notes: https://github.com/k3s-io/k3s/releases/tag/v1.21.3%2Bk3s1

⚠️ Important Upgrade Note ⚠️
If you are using K3s in a HA configuration with an external SQL datastore, and your server (control-plane) nodes were not started with the --token CLI flag, you will no longer be able to add additional K3s servers to the cluster without specifying the token. Ensure that you retain a copy of this token, as is required when restoring from backup. Previously, K3s did not enforce the use of a token when using external SQL datastores.

So, when setting up the k3s instance, you need to use --token="HeresARandomTokenHereWow" and you need to use it for every k3s instance you are setting up.

If you forgot to set a token while setting up the node, you need to drop the database k3s created!

SQL Datastore Address

Another issue that I've found: Using the "@tcp(IpHere:PortHere)" format doesn't work for me for some reason, the service fails with "preparing server: creating storage endpoint: building kine: parse "postgres://postgres:passwordhere@tcp(172.29.2.1:5432)": invalid port ":5432)" after host". Maybe because I'm not using a load balancer for my PostgreSQL server? I don't know but I don't this is the issue.

It works if I use postgres://postgres:[email protected]:5432.

Metrics server not working

I also mentioned that on my comment, but I think this only affects a small percentage of users.

On my Proxmox installation, I have a LAN and a VXLAN (using Proxmox's experimental SDN configuration), and I wanted my Kubernetes nodes to communicate between them using the VXLAN network.

To make that work, you need to add --node-external-ip="172.29.0.1" (where the IP is the VM's VXLAN IP) and --flannel-iface="ens19" (where ens19 is the network interface you want Kubernetes to use for communication) to the k3s command.

I also have the commands I've used to setup my cluster here: https://github.com/PerfectDreams/AthenaKube#master-node

traefik + ssl everywhere + swarm mode + docker-compose.yml

I've been following your step-by-step instructions on how to install traefik + portainer through Put Wildcard Certificates and SSL on EVERYTHING and also your related video https://www.youtube.com/watch?v=liV3c9m_OX8

Everything went fine but now I'm struggling to make it work after having created a Swarm with 3 Raspberry Pi's: I want traefik to work as proxy for containers running on any node of the swarm/cluster.

According to Traefik documentation, for it to work in a Swarm, it must be deployed on a master node (no problem since my 3 nodes are managers). Thus, I included this in the docker-compose.yml:

    deploy:
      #mode: global     #Should it be installed on every manager node or will it suffice with just one?
      placement:
        constraints:
          - node.role == manager

I've also created a new overlay network (instead of the regular bridge mode network you used, called proxy) and modify the docker-compose accordingly.

Besides, it seems that the labels must be nested one level deeper, under the deploy tag, thus:

[...]
    deploy:
      placement:
        constraints:
          - node.role == manager
      labels:
        - traefik.enable=true
        - traefik.docker.network=proxy-overlay
        [more labels here]
networks:
  proxy-overlay:
    external: true

I've also modified the data/traefiik.yml file to include:

providers:
  docker:
    swarmMode: true
    endpoint: "unix:///var/run/docker.sock"
    watch: true
    exposedByDefault: false

I'm using your file as template, tried every possible combination but I still cannot make it work:

techno-tim.github.io/reference_files/traefik-portainer-ssl/traefik/docker-compose.yml

Lines 1 to 45 in ef6b8c9

	version: '3'
	services:
	traefik:
	image: traefik:latest
	container_name: traefik
	restart: unless-stopped
	security_opt:
	- no-new-privileges:true
	networks:
	- proxy
	ports:
	- 80:80
	- 443:443
	environment:
	- [email protected]
	- CF_DNS_API_TOKEN=YOU_API_TOKEN
	# - CF_API_KEY=YOU_API_KEY
	# be sure to use the correct one depending on if you are using a token or key
	volumes:
	- /etc/localtime:/etc/localtime:ro
	- /var/run/docker.sock:/var/run/docker.sock:ro
	- /home/username/traefik/data/traefik.yml:/traefik.yml:ro
	- /home/username/traefik/data/acme.json:/acme.json
	- /home/username/traefik/data/config.yml:/config.yml:ro
	labels:
	- "traefik.enable=true"
	- "traefik.http.routers.traefik.entrypoints=http"
	- "traefik.http.routers.traefik.rule=Host(`traefik-dashboard.local.example.com`)"
	- "traefik.http.middlewares.traefik-auth.basicauth.users=USER:BASIC_AUTH_PASSWORD"
	- "traefik.http.middlewares.traefik-https-redirect.redirectscheme.scheme=https"
	- "traefik.http.middlewares.sslheader.headers.customrequestheaders.X-Forwarded-Proto=https"
	- "traefik.http.routers.traefik.middlewares=traefik-https-redirect"
	- "traefik.http.routers.traefik-secure.entrypoints=https"
	- "traefik.http.routers.traefik-secure.rule=Host(`traefik-dashboard.local.example.com`)"
	- "traefik.http.routers.traefik-secure.middlewares=traefik-auth"
	- "traefik.http.routers.traefik-secure.tls=true"
	- "traefik.http.routers.traefik-secure.tls.certresolver=cloudflare"
	- "traefik.http.routers.traefik-secure.tls.domains[0].main=local.example.com"
	- "traefik.http.routers.traefik-secure.tls.domains[0].sans=*.local.example.com"
	- "traefik.http.routers.traefik-secure.service=api@internal"
	networks:
	proxy:
	external: true

Everytime, every possible change that has come to my mind leads me to a 404 File not found error page when the docker-compose file is deployed.

Can you shed some light on what changes would be needed in your template to make it work on a swarm mode cluster?

Thank you.

Update to first-13-things-linux

The line:
/etc/apt/apt.conf.d/50-unattended-upgrades

should be:
/etc/apt/apt.conf.d/50unattended-upgrades

Thanks!

Unable to obtain ACME certificate for domains \"local...

Excellent write up. Loved the youtube instructions. Everything worked like a charm.

I only ran into a small issue: The certificates filed to create with error:

traefik    | time="2021-09-19T15:34:45-05:00" level=error msg="Unable to obtain ACME certificate for domains \"local.example.tld,*.local.example.tld\" : unable to generate a certificate for the domains [local.example.tld *.local.example.tld]: error: one or more domains had a problem:\n[*.local.example.tld] time limit exceeded: last error: NS ....ns.cloudflare.com. did not return the expected TXT record [fqdn: _acme-challenge.local.example.tld., value: .....]: \n[local.example.tld] time limit exceeded: last error: NS ....ns.cloudflare.com. did not return the expected TXT record [fqdn: _acme-challenge.local.example.tld., value: ...]: \n" providerName=cloudflare.acme
^CERROR: Aborting.

The fix was to place the wildcard to main and the without wildcard to sans

      - "traefik.http.routers.traefik-secure.tls.domains[0].main=*.local.example.tld"
      - "traefik.http.routers.traefik-secure.tls.domains[0].sans=local.example.tld"

After this, both certificates got generated and saved in acme.json

Traefik 2.5.5: Can't issue a certificate

Getting the following errormessage and no certificate:
time="2021-12-19T21:55:26Z" level=error msg="Unable to obtain ACME certificate for domains "xxx.xxx.xxx,.xxx.xxx.xxx" : unable to generate a certificate for the domains xxx.xxx.xxx .xxx.xxx.xxx]: error: one or more domains had a problem:\n[.xxx.xxx.xxx] [.xxx.xxx.xxx] acme: error presenting token: cloudflare: failed to create TXT record: HTTP status 400: Record already exists. (81057)\n[xxx.xxx.xxx] [xxx.xxx.xxx] acme: error presenting token: cloudflare: failed to create TXT record: HTTP status 400: Record already exists. (81057)\n" providerName=cloudflare.acme

The description of episode is wrong

The post 2021-02-01-deep-learning-my-life has the same description underneath the video as the ventoy episode.

Pihole High Availability

Howdy, great video. Just wanted to let you know that to make the High Availability even better would be to use the tool keepalived to maintain that 100% uptime.

Cheers

FQDN vs host name.

Hello Tim!! I am very glad to have stumbled across some of the work you have been doing, however I have gotten stuck with an issue I hope you can help me resolve.
If I enter the FQDN I get the cert for *.example.tld
If I enter the Host (within my search domain) I get a cert for traefik.

am I just dense, or did I miss a step?

thanks, and any additional help would I will be grateful for.

Possible fix for misaligned github logo on site

Hi, maybe someone let the fa-2x tag on the Browser version of the page,
<i class="fab fa-github fa-2x"></i>

causing the github logo, to be misaligned with the circle.

I think this was intended to be on the Mobile version?

maybe this could work but change a bit of the design:

<div class="sidebar-bottom mt-auto d-flex flex-wrap justify-content-center">
  <a
    href="https://twitter.com/technotimlive"
    aria-label="twitter"
    target="_blank"
    rel="noopener"
  >
    <i class="fab fa-twitter"></i>
  </a>
  <a
    href="https://www.youtube.com/channel/UCOk-gHyjcWZNj3Br4oxwh0A"
    aria-label="youtube"
    target="_blank"
    rel="noopener"
  >
    <i class="fab fa-youtube"></i>
  </a>

  <a
    href="https://twitch.tv/technotim"
    aria-label="twitch"
    target="_blank"
    rel="noopener"
  >
    <i class="fab fa-twitch"></i>
  </a>

  <a
    href="https://patreon.com/technotim"
    aria-label="patreon"
    target="_blank"
    rel="noopener"
  >
    <i class="fab fa-patreon"></i>
  </a>

  <a
    href="https://discord.gg/DJKexrJ"
    aria-label="discord"
    target="_blank"
    rel="noopener"
  >
    <i class="fab fa-discord"></i>
  </a>
  <!-- THIS IS THE OLD CODE FOR THE LOGO:
    
    <div class="d-flex flex-row justify-content-center align-items-center">
    <div class="p-1">
      <a
        href="https://github.com/techno-tim/techno-tim.github.io"
        target="_blank"
        rel="noopener"
      >
        <i class="fab fa-github fa-2x"></i>
      </a>
    </div>-->

  <a
    href="https://github.com/techno-tim/techno-tim.github.io"
    aria-label="github"
    target="_blank"
    rel="noopener"
  >
    <i class="fab fa-github"></i>
  </a>

  <!-- THIS IS THE OLD CODE FOR THE TEXT:
    <div class="p-1"> --changed the p-1 to the text
      <div class="d-flex flex-column align-items-start justify-content-end"> --flex-colum to flex-wrap, justify-content-end to justify-content-center
        <div class="text-sm-left">330 stars</div> --added p-1
        <div class="p-0">97 forks</div> --changed to p-1
      </div>
    </div>
  </div>
</div>  -->

  <div class="d-flex flex-weap justify-content-center">
    <div class="p-1 text-sm-left">330 stars</div>
    <div class="p-1">97 forks</div>
  </div>
</div>

The resault:

I don’t intend to use let’s encrypt for ssl — how to modify your ssl everything using Traefik and cloudflare?

Discussed in #137

^{Originally posted by simkimsia May 12, 2022}
I don't want to use let's encrypt and it's for multiple apps running on same Ubuntu server

I wish to use cloudflare for the ssl service as well as for managing the dns and domains

How do I modify the ssl everything tutorial to do this?

can't generate cert. "help wanted"

I have gotten setup to this point however I run into this error:

time="2021-04-27T22:51:14Z" level=info msg="Configuration loaded from file: /traefik.yml"
time="2021-04-27T22:51:21Z" level=error msg="Unable to obtain ACME certificate for domains "local.xyznetwork.page,.local.xyznetwork.page" : unable to generate a certificate for the domains [local.xyznetwork.page .local.xyznetwork.page]: error: one or more domains had a problem:\n[.local.xyznetwork.page] [.local.xyznetwork.page] acme: error presenting token: cloudflare: failed to find zone xyznetwork.page.: ListZonesContext command failed: HTTP status 400: Invalid request headers (6003)\n[local.xyznetwork.page] [local.xyznetwork.page] acme: error presenting token: cloudflare: failed to find zone xyznetwork.page.: ListZonesContext command failed: HTTP status 400: Invalid request headers (6003)\n" providerName=cloudflare.acme

My dns provider is cloudflare I have add the api key from cloudflare. The config has not changed other than the placeholder values.
What am I doing wrong. please let me know what other info that I can provide to receive help

Nginx.conf

can you add a line for loading the stream module to the nginx.conf sample for the ha-k3s install docs?

first line should be this : "load_module /usr/lib/nginx/modules/ngx_stream_module.so;"

Lost for answer traefik + pihole

Hi,

So, i followed you guide on SSL everything (https://www.youtube.com/watch?v=liV3c9m_OX8)... Works like a charm, but what i cannot find. You mention using PiHole for you local DNS (so that would be: https://www.youtube.com/watch?v=kKsHo6r4_rc). But is that BESIDES traefik or ' instead' ? Example:

Proxmox you put in Traefik for PVE1.domain. Do you also put a local DNS in Pihole for this? And if so:

• What DNS provider you use with pihole? Cloudflare or (for example) Unbound?
• What IP does the DNS point to? Traefik or Proxmox itself?

I cannot find these answers online

i am getting this error with portainer

following these configs https://github.com/techno-tim/techno-tim.github.io/tree/master/reference_files/traefik-portainer-ssl

Small Issue in 2 Factor Auth and Single Sign on with Authelia

Morning,

Thanks for the new video. Amazing stuff. There is one super small issue on the document server with this page --> https://techno-tim.github.io/posts/authelia-traefik/

You are missing an "s" in the file name of users_database.yml

Thanks for all your hard work! Look forward to the next video.

McAwesome

traefik-portainer-ssl ipWhiteList not in middleware chain (external vs local proxy)

Hi Tim,

i really like your content. Keep up spreading the homelab spirit.

I started my journey to Traefik with the help of https://github.com/htpcBeginner/docker-traefik. When i saw your video, i thought i could finally proxy all my local services with ssl/tls certificates and also proxy some services externally (e.g Nextcloud).

I noticed that the only thing that keeps your config secure and prevents Traefik from serving your internal sites externally is your router is not forwarding ports 80 and 443 to Traefik (Thanks to the acme dns challenge which works independently of dns A records). You were talking about IP whitelisting of local networks as an additional layer of security if using internally, but it becomes crucial if you port forward to your Traefik instance. Your config does not use the "secured" middleware chain you defined, but uses "default-headers" for all http routers instead.

# You created the middleware chain
http:
  middlewares:
    secured:
      chain:
        middlewares:
        - default-whitelist
        - default-headers
  
# But you never referenced it in your routers
http:
 #region routers 
  routers:
    proxmox:
      entryPoints:
        - "https"
      rule: "Host(`proxmox.local.example.com`)"
      middlewares:
        - default-headers # should reference "secured" middleware chain
      tls: {}
      service: proxmox

Okay, but now how to provide ssl/tls to internal services with wildcard certificates while also beeing able to host some externally (hopefully with the same Traefik instance)? How could I add internal services to Traefik if my Router is allready pointing at Traefik? Does the ipWhiteList middleware provide enough security? Maybe let's figure out together

Best,
Florian

Point proxmox first things article to 7

https://techno-tim.github.io/posts/proxmox-7/

No Documentation for generating basic auth password

techno-tim.github.io/reference_files/traefik-portainer-ssl/traefik/docker-compose.yml

Line 30 in a351a21

- "traefik.http.middlewares.traefik-auth.basicauth.users=USER:BASIC_AUTH_PASSWORD"

For new users, this step may be difficult and confusing as to why they are not able to set their password properly and log in to the Traefik dashboard. There should exist documentation for how to configure this.

K3s Install addition

As mentioned in discord I would recommend adding the following to your k3s deployment. I see multiple pages about the k3s deployment and each are missing the following which will make sure the nodes stay alive even if you over provision pods.

INSTALL_K3S_EXEC= ........ --kubelet-arg system-reserved=cpu=100m,memory=100Mi --kubelet-arg kube-reserved=cpu=200m,memory=400Mi

Update Top 11 Things on Proxmox for v7

Need to update this guide to include v7 and possible v6 in comments