Jump to content

aptalca

Community Developer
  • Content Count

    2666
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by aptalca

  1. 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.
  2. 1) turn off cloudflare proxy 2) fix your port forwarding
  3. 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
  4. Update again. That was already fixed last night
  5. 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" 😉
  6. 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
  7. https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/
  8. 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
  9. Go back a few pages, there was a detailed overview
  10. Why would unraid be forced to do that? They don't currently put out a new release when there is a new docker update, or an update to the Intel gpu drivers, or kernels, etc. They put out a release when they feel like it or when there is a major security fix. We on the other hand feel like we are forced to put out an update for this addon whenever there is a new unraid release. It is plenty of extra work for us.
  11. That ip is what letsencrypt is getting for your domain name. Check your dns settings if that is not your public ip
  12. 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
  13. 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
  14. The letsencrypt log you posted earlier shows port 80 going to unraid gui
  15. Limetech would just have to include the nvidia driver in the unraid build. Nvidia runc could be offered as an official plugin or baked in. That's what chbmb does, unpack unraid, bake in nvidia drivers and runc, and recompile. But because chbmb doesn't exactly know what may or may not have changed in unraid releases (not open source) he has to reverse engineer quite a bit. Qnap on the other hand bakes nvidia drivers and runc in their software.
  16. 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
  17. Your port forwarding is not correctly applied. Try restarting the router
  18. Open a github issue for a feature request and we'll add it when we get to it
  19. I'll look into port share. It sounds like it might be useful