aptalca

Are you using https?

It's explained in the readme

Post your docker run

You didn't even mention the name of the plugin. I don't know what to tell you.

Did you change it to host networking? Because right now nginx isn't even starting. You said "I'm being told that the cert. . . has expired". Who told you that? Email or browser?

https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/

That email means, "one of the certs that you received with that email address is expiring". In this case, it's not the cert that your server is currently using.

1) turn off cloudflare proxy 2) fix your port forwarding

You can have access to your entire lan in bridge mode. Don't change every setting in the gui, especially don't try and change the server ip. Just add your subnet to the nat settings and check the box to allow clients access to other devices on your lan

Update again. That was already fixed last night

Glad to hear you figured it out. And just an fyi, "Literally just upgraded the container to the latest version" often means "I changed a bunch of other things as well but I can't remember at the moment" 😉

It's been discussed to death. Harmless lua error. Unrelated. Server ready means nginx is up and running. Check your dns settings and port forwarding

https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

You know about "mc", right? Midnight Commander

Not sure, it's a docker security feature to block connections between host and macvlan. I don't recommend using macvlan unless you really have to. I only have 2 services on macvlan just so I can set up an ip based rule to let them bypass vpn. But even that is a fringe case

Use bridge networking

No idea with the little info you provided

That ip is what letsencrypt is getting for your domain name. Check your dns settings if that is not your public ip

You can leave it. When you type address in the url bar (inside your lan), use https so the requests go to letsencrypt. Http requests will go to unraid's port 80

That was just added a few days ago. It will be included in the next letsencrypt build: https://github.com/linuxserver/reverse-proxy-confs/pull/111

The readme explains how to troubleshoot that

Look into hairpin nat

The letsencrypt log you posted earlier shows port 80 going to unraid gui

It's your router and/or port settings. I'm assuming you're running unraid on port 443. Your router is redirecting internal (lan) requests to your domain to the unraid ip in the same 443 port, so you're getting unraid. You can move unraid's https port to something else and run letsencrypt on 443 instead