biggiesize

Members
  • Posts

    72
  • Joined

  • Last visited

Everything posted by biggiesize

  1. Are you pointing to a specific vyprvpn server in your config? You might try a different server or region. I'm sure you already have but I would also double check your credentials take sure they work logging into the vyprvpn website.
  2. I just looked at the server list file and I do not see servers for Ashburn. The wiki itself is not always up to date with the latest server changes. I would double-check with Privado that the servers are still valid. If they are, submit a bug report in github for the issue so the dev can work it. https://raw.githubusercontent.com/qdm12/gluetun/master/internal/storage/servers.json
  3. Absolutely! I am not using port 8080 either so that "shouldn't" be causing issues. Since you're using the LinuxServer container, there is a fairly easy way to get it running. Edit qbittorrent and add an environment variable called "DOCKER_MODS" with a value of "ghcr.io/gilbn/theme.park:vuetorrent". (Obviously without quotes) Optional: You can choose between a few themes. You can find those here. Just add another variable called "TP_THEME" with a value of the theme you choose. (e.g. TP_THEME=dark) Next, inside qbittorrent, go to Settings -> WEBUI, check Use alternative Web UI and enter its location /vuetorrent, then save. You might need to restart the container but I can't remember.
  4. That was my assumption. To my knowledge, while it may be possible, this is not a supported or intended use of Gluetun as it is a VPN client replacement. My suggestion would be to contact the developer and discuss this use case with him . https://github.com/qdm12/gluetun/issues/new/choose
  5. This sounds like you are trying to make Gluetun act like a reverse proxy of sorts, which it is not designed for. What is your ultimate goal for this setup?
  6. I just pushed a new version. It should be updated in CA within an hour. With the changes I made, you may need to delete the old container and create a new one.
  7. It does look like there is a newer version. I will do my best to update it this weekend.
  8. FIREWALL_VPN_INPUT_PORTS and FIREWALL_INPUT_PORTS need a comma separated list of all the ports that need to talk through gluetun (e.g. 7878,8989,9898,etc). FIREWALL_OUTBOUND_SUBNETS needs your local subnet in CIDR form (e.g. 192.168.1.0/16).
  9. Did you place those ports in both FIREWALL_VPN_INPUT_PORTS and FIREWALL_INPUT_PORTS. Also, did you place your local subnet in FIREWALL_OUTBOUND_SUBNETS?
  10. Can you send me screenshots of the configs for gluetun, radarr and nzbget? Make sure to hide any sensitive info like IPs, Usernames and passwords.
  11. My apologies, work picked up and took most of my night. I will look at your logs asap after I grab some rest.
  12. I just pushed a change to the template that I believe should fix your install error. The appstore should pick up the new template in ~30 minutes.
  13. Pretty sure the only logs that would show deletion would be the system logs. The application logs only show what runs inside the container. You can got to Tools->Diagnostics and download the logs for me to look at. Make sure to check the box for anonymity.
  14. I have not seen glutetun be removed after an update. Can you reinstall it through the appstore? You should be able to find it under previous apps and it maintain your settings. Could possibly be startup order. Make sure that glutun starts before all the apps that use it for network.
  15. Yeah I was curious about that. AFAIK public release is still on rc2 but I could be wrong. Either way, I am not sure where to go from here. I don't think it's an app problem so much as it is a generic container problem. I would probably post something in the General Help section and have one of the mods look at the logs. They will have a much better knowledge base than I do. If they do deem it an issue with the app then I will try to engage the dev. I will always try to help in anyway I possibly can. I apologize for you facing this issue and me not being able to resolve it for you.
  16. From that description, since it didn't give an error, it sounds like the app is starting and then immediately stopping. Yes you can test an older version. For ddns-updater, edit the container and for the repository put: qmcgaw/ddns-updater:v2.4.0
  17. Sorry...I gave the wrong command... It SHOULD be, exactly: docker start gluetun
  18. I agree, I don't see any mentions specifically in the logs. There is a lot of NGINX chatter which may lead to the syslog filling up. I did notice that the logs indicate there is only 400MB RAM free. That could cause issues but not certain. I'm curious to see if you stop some other containers if gluetun will start. Also, can you check the dashboard and see the docker image utilization and if it is full? I think it should be under Memory. We could also check if the app is throwing an error when starting. You can open up a terminal window and run: docker run gluetun The app name will obviously be whatever you named the container. If it does give an error it should show in the terminal window.
  19. Yes, but first, try to start the container just so it will be towards the end of the logs. Go to Tools->Diagnostics. At the bottom of the page there should be a download button (make sure anonymize is checked) and upload the here so I can take a closer look.
  20. Hmmm, haven't seen that one yet. Is there anything in the logs? Have you tried creating it under a different app name?
  21. Hmmm...have seen that one yet. Is there anything in the logs? Have you tried creating it under a different app name?
  22. I'm assuming that BLOCK_MALICIOUS is set to "ON" for the Unbound DNS resolver, which it really should be for security reasons as it blocks IPs and hostnames for malicious sites. Usenetserver is a common false positive. You can simply put "usenetserver.com" (without quotes) in the UNBLOCK variable and it will resolve the issue.