Jump to content

aptalca

Community Developer
 View Profile  See their activity

  • Posts

    3,064

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Everything posted by aptalca

  1. aptalca
    For something internal only, you can use our nginx image. You can drop the web files into folder www and set the default site conf accordingly.
  2. aptalca
    That only works with subdomains confs, not subfolder
  3. aptalca
    No, that's the logic built in. You can do "ls *.conf" to see the active ones. How is tab completion difficult? It's the first part of the naming scheme that's unique per app, and it matches the conf before the .sample And how frequently do you edit them honestly?
  4. aptalca
    If the reverse proxy is already set up via container name as dns hostname, you can remove the 8989 port mapping
  5. aptalca
    Instructions in the readme
  6. aptalca
    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
  7. aptalca
    Nginx doesn't run until it gets a cert
  8. aptalca
    Post your container settings
  9. aptalca
    Check the ip on duckdns, if correct, check your port mapping
  10. aptalca
    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.
  11. aptalca
    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)
  12. aptalca
    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
  13. aptalca
    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)
  14. aptalca
    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"
  15. aptalca
    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.
  16. aptalca
    Did you update to rc7 through the nvidia plugin?
  17. aptalca
    Your previous logs showed a lot of weird errors. Post a new log with your new config
  18. aptalca
    Did you forward the udp port on your router as udp?
  19. aptalca
    No nano inside openvpn container. He needs to edit it on unraid directly via "nano /mnt/user/appdata/openvpn-as/etc/as.conf"
  20. aptalca
    If you have existing data, you're fine. Only on a brand new install with the latest version, data wasn't being stored properly. It's fixed now. I basically focused so much on upgrades that I didn't notice a bug that affects new installs
  21. aptalca
    It seems there is a bug for new installs. Looking into it. EDIT: Yup, missed something for new installs. PR submitted, should be merged soon. After update, it will reset one more time but then it should be good.
  22. aptalca
    Run it in bridge mode as shown on GitHub or docker hub page
  23. aptalca
    Glad you got it sorted. I'd highly recommend backup options if the server is remote. I personally have 3 options: 1) openvpn on router 2) openvpn on unraid 3) wireguard on an rpi
  24. aptalca
    Alright ladies and gents, the rewrite for openvpn has been pushed to master and there is a new build on docker hub. You should be able to return to linuxserver/openvpn-as or update to 2.7.3 safely
  25. aptalca
    Once we merge to master, I'll notify here so you can switch back to the "linuxserver/openvpn-as" image
×
×
  • Create New...