Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

Community Reputation

152 Very Good


About aptalca

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    If the reverse proxy is already set up via container name as dns hostname, you can remove the 8989 port mapping
  2. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Instructions in the readme
  3. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Ok, as a test, stop the letsencrypt container. Then set up the regular nginx container with the same exact port mappings as letsencrypt. See if you can reach the container using your domain name at both ports 80 and 443
  4. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Nginx doesn't run until it gets a cert
  5. aptalca

    [Support] Linuxserver.io - Plex Media Server

    Post your container settings
  6. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Check the ip on duckdns, if correct, check your port mapping
  7. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Could it be browser cache? There shouldn't be duplicates unless there are two Plex servers are running with the same name but different server ids.
  8. aptalca

    [Support] Linuxserver.io - OpenVPN AS

    So basically you did everything but read the official documentation? See here for the most accurate info: https://hub.docker.com/r/linuxserver/openvpn-as Or here: https://github.com/linuxserver/docker-openvpn-as You may have missed the cap add statement. If it still doesn't work after that, check the logs (both the docker log and the log folder under config folder)
  9. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Leave the one you want to access remotely in host networking and read the top of the proxy conf to see what exactly you need to change for host mode
  10. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    You shouldn't have changed the port if it's connecting via container name. Read the docs for letsencrypt, it's all explained there and the top of each config tells you what to change. Don't change anything else unless you know exactly what you're doing (changing server name to cloud is fine)
  11. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Symlinks work as long as nginx inside the container can follow it and access the target. I'm assuming the symlink is pointing to a share hosting your movies on unraid, but the letsencrypt container does not have access to that share (location not mapped) so nginx read the link but cannot find the target. Here's what you can do: 1) map your movies location into your letsencrypt container as "/movies" and create symlinks in your www folder that point to "/movies/filename"
  12. aptalca

    [Support] Linuxserver.io - OpenVPN AS

    Those errors are harmless. The openvpn package is trying to start itself via systemd after install and also after init and it's failing because there is no systemd service inside the container. We manage it with s6, so you can ignore those errors. Client/admin web pages are managed through the admin gui. By default both are served over port 943, where the naked url gets you the client ui and the /admin subfolder gets you the admin interface. They are all openvpn-as standard behavior.
  13. aptalca

    [support] limetech's docker repository

    Did you update to rc7 through the nvidia plugin?
  14. aptalca

    [Support] Linuxserver.io - OpenVPN AS

    Your previous logs showed a lot of weird errors. Post a new log with your new config
  15. aptalca

    [Support] Linuxserver.io - OpenVPN AS

    Did you forward the udp port on your router as udp?