aptalca

Community Developer
  • Posts

    3064
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by aptalca

  1. Check the plex server gui settings and make sure transcoding folder is set to "/transcode"
  2. 99:100 you set that in the template as PUID/PGID
  3. The container doesn't touch media folders as they are not essential and they are user owned and managed. The container only fixes permissions on the config folder, which is essential for its own operations. We used to fix permissions on media folders but for every person who wants that, there are ten people who don't
  4. They need to be owned by user 99:100, not root
  5. Create a new server block as a catch all, set it as default, and serve the 404 or block. That way anything that doesn't match another server block will match there
  6. They see the gpu even if you don't pass the gpu id. But they can't connect unless you pass it correctly
  7. You're manually running commands inside the container and heavily customizing it, therefore we can no longer provide support.
  8. 502 means letsencrypt can't reach code-server. You likely forgot to put them in the same user defined bridge network
  9. Check the nginx logs to see what ip is listed as the source when you connect over vpn. I suspect it will look like the openvpn container ip as everything is nat'ed through that
  10. We're not the admins of duckdns service. https://groups.google.com/forum/m/#!forum/duckdns
  11. You have way too many modifications there. Either contact the author of the guide you used, or use our guide here: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/
  12. Oh yeah I did overlook on mobile 😄 I thought you were trying to send emails from within the container. That's exactly what you want for proxy. The nginx.conf I believe has a very basic sample in there which you can enable and modify: https://github.com/linuxserver/docker-letsencrypt/blob/master/root/defaults/nginx.conf#L85