Jump to content

aptalca

Community Developer
  • Content Count

    2379
  • Joined

  • Last visited

Everything posted by aptalca

  1. Go to services/dns resolver and add your host overrides at the bottom
  2. 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
  3. That's host networking, not bridge. See the first item on the list above
  4. 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/
  5. Funny you ask for info. We need a lot more info from you
  6. Arch packages won't work, the others are docker images We don't compile nginx or the modules, because that would be a support and maintenance nightmare. If new packages are needed, you can PR to alpine. That's what I do: https://github.com/alpinelinux/aports/pull/6762 https://github.com/alpinelinux/aports/pull/7710
  7. No brotli package on alpine: https://pkgs.alpinelinux.org/packages?name=*brotli*&branch=v3.9&arch=x86_64
  8. Ironically, macvlan blocks host connections for security as well
  9. With macvlan but it blocks the connection between the host and the container. Why do you need to give it a different IP?
  10. That's macvlan and it blocks the connection between the host and the container
  11. Another user had issues with adguard blocking it. Your issue is likely similar, possibly pi-hole
  12. If there is no setting for http auth, that usually means it doesn't work with it. Nextcloud has its own auth built in so likely it collides with http auth. Do you mean br0? That's macvlan, not bridge, and it blocks connections between host and the containers on it. But I'm making assumptions because you are not providing enough info to understand the situation.
  13. Edited my post above to add info on how to get redirect to www working. What you want to do is, only catch the naked domain and redirect it to www. You don't want ombi.domain.com to redirect to www.domain.com
  14. Change that section back to the defaults: https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/default#L5-L10 Right now it is only catching www.domain.com and it's redirecting it to www.domain.com on 443. The defaults catch everything and redirect it to the https version of whatever's requested. Then you can create a second block where it listens on 443, the server name is domain.com and redirects to www.domain.com
  15. Yes, edit the proxy confs to uncomment the relevant lines. Instructions in there. If you're going to use http auth, first generate the .htpasswd as described in the readme
  16. The webserver is published in two ways: 1. Through the admin gui port (defined in container settings) 2. On the tcp and udp connection ports. You should disable the second one in the openvpn-as gui. And do not make the 943 port available on the internet. That way the gui will only be available on lan
  17. You can set it to anything you like. But that folder has to be mapped in container settings and in nginx you will use the container side of the mount. So if you map /mnt/user/webfiles as /webfiles in container settings, set the root to /webfiles so it will use that share
  18. Guys, it's all in the official readme on GitHub and docker hub. Use bridge networking, don't set the interface variable, make sure your port mapping is correct (@syniex yours is not) and add the cap-add statement. The unraid template was updated a long time ago but you may have to update it manually for existing setups. Or, you can remove the container (keep the appdata config folder) and recreate from a fresh new template from the community apps with the same appdata folder.
  19. Bridge networking? Post your container settings