Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

Everything posted by aptalca

  1. You forgot to rename the second variable name in your works one. Fix the last line for proxy pass
  2. Post the new confs you're using and check the error log in the config folder
  3. Try changing the variable name to upstream_nextcloud_works
  4. You can do so through the plug-in. Select a stock build
  5. Return all those values to the defaults. Only add your lan subnet to the routing section
  6. Perhaps read the documentation? On github or docker hub
  7. Download a new client config. Your current config was generated before you fixed the hostname on your server.
  8. Nope. Certbot added an up to 10 minute delay to renewal attempts so no more renewals during container start. Only via cron
  9. Do you shut down your server at night? There should be a renewal attempt every night at 2:08am
  10. Yeah, but it's good to have a backup, in case you can't connect to one for some reason. I have my pfsense one with udp on the standard port, the container on unraid that is tcp stream proxied by letsencrypt on port 80 and wireguard on an rpi3. Some public wifi block all outgoing udp connections and tcp over non-http/s so the port 80 one saved my a$$ quite a few times
  11. You don't need to add that line to the bottom, it's already in proxy.conf Is znc on the same user defined bridge network as letsencrypt? Is the container named "znc"? Is it running? Can you reach it via http://unraidip:6501 ?
  12. Post a screenshot of your container settings. Your networking is selected in there
  13. 1. Ignore that error. Openvpn tries to start itself via systemd but our image uses s6 instead. We start it later. 2. No ideas about intermittent connectivity 3. Don't set it to match your lan config, they will clash. Make sure it has different subnets used for the openvpn network (leave those as is). Just add your network's subnet into vpn settings/routing. And make sure routing is set to to nat and the other 2 questions are answered yes. What kind of networking are you using?
  14. Just read the last few posts man, come on now
  15. Docker blocks connection between host and macvlan. Not much you can do about it
  16. Go to services/dns resolver and add your host overrides at the bottom
  17. All the conf files are in the config folder. /config/nginx/site-confs/default is the one you want to edit for https redirection. There are instructions in there
  18. That's host networking, not bridge. See the first item on the list above
  19. Assuming this is a fresh install, go to http://unraidip:32400/web from a computer that is in the same network subnet as unraid If the subnet is different, you can use the ssh tunnel method described at the bottom of this page under on a different network: https://support.plex.tv/articles/200288586-installation/
  20. Funny you ask for info. We need a lot more info from you
  21. Post a screenshot of your container settings