phreeq

After all the headaches I had, I did start doing weekly backups for my containers. Learned that lesson the hard way Sent from my ONEPLUS A5010 using Tapatalk

Just an update, my problem was indeed me. After fixing the cloudflare.ini file, my certs renewed just fine.

Did yours renew after adding the line? I'm asking because mine is failing renewal and I do have the dns_cloudflare_credentials = /config/dns-conf/cloudflare.ini line in the conf file. **Update** I found that my cloudflare.ini file didn't have my data in it. I had a problem with all of my dockers due to a bad upgrade to my cache drive a while back, so I guess the problem was me. I'll check back in tomorrow to see if the renewal goes right.

Unfortunately, life got in the way and I was not able to attempt the restore. I did get two of my systems to do an image backup with no problems and I plan on trying to switch from test to latest when I get home tonight.

First backup is running, over the weekend I'm going to try a full image restore from backup and make sure it all works.

This worked. Thanks!

@TechFireSide, you beat me to it. To be fair, I did try both with and without privileged toggled on

As soon as you've got it up, I'll give it a run. Until then, I guess I'll wipe out the current one.

I tried the same thing and got the same results. Only difference is that I'm running 2x X5550 Xeons

I'm seeing the same thing here. Haven't had a chance to do much playing around to see if I can find a fix yet, but about to do that now.

No problem. I'm just glad I was able to help out

Excellent, glad to hear that Sent from my ONEPLUS A5010 using Tapatalk

As a bit of warning, I had a few dockers set up before starting down the path of using letsencrypt, so I never did set up the custom bridge. I had to make the call to the IP address instead of using the name, but I hacked it together from my radarr conf file. server { listen 443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_bitwarden bitwarden; proxy_pass http://192.168.1.xxx:8888; } } Hope this helps

I've got it working, but I can't get to my conf right now. Heading to bed, but I'll get it to you tomorrow Sent from my ONEPLUS A5010 using Tapatalk

So totally missed that part, thanks! Now I just need to figure out the whole dns validation part, wish me luck

I just know that I'm missing something, but I can't figure out what. If any of y'all can give me a hand, I'd appreciate it.