biggiesize

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.

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

Sorry...I gave the wrong command... It SHOULD be, exactly: docker start gluetun

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.

Is this a new install or was it previously working?

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.

Hmmm, haven't seen that one yet. Is there anything in the logs? Have you tried creating it under a different app name?

Hmmm...have seen that one yet. Is there anything in the logs? Have you tried creating it under a different app name?

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.

Did you also put the port in the FIREWALL_VPN_INPUT_PORTS variable?

They do support using a proxy but the safer option is to use the gluetun container as the network option. There are a few extra steps with ports and such but there are some excellent resources out there that show how to accomplish it. Here are a couple of resources. https://github.com/qdm12/gluetun/wiki/Connect-a-container-to-gluetun

I'm glad that everything went smoothly for you so far. Personally, for torrenting, I use qbittorrent from the LinuxServer guys with the VueTorrent WebUI but I have also used Deluge from Binhex. Either are excellent choices. It really depends on your personal preference.

Thank you for catching this. That shouldn't be a folder redirect but instead a variable location. I have tested the correction and pushed the updated config. Should be fixed the next time CA runs the scan for config changes.

I believe he only uses /bin/sh and not bash in the container. Only thing I can think of ATM is the "Console shell command" field in the container settings is "bash" instead of "shell".

Unfortunately, I dont know the correct answer to your question. It may be for your provider @ is the only supported record. Below is a link to the example config the dev has provided, along with the available settings, specifically for Dreamhost. You can always open an issue on the Github repo with your question. The dev is usually good about working through those quickly. Also, something I just thought of is make sure the record your trying to update is an A or AAAA record. CNAME records are not yet supported but are in the roadmap. https://github.com/qdm12/ddns-updater/blob/master/docs/dreamhost.md

I had the same issue a while back. For me it was being flagged as malicious in Unbound. Try adding "usenetserver.com", without quotes, to the UNBLOCK variable.

Hello there Other than the variables marked as required in the template, for ProtonVPN you need to set these variables: VPNSP=protonvpn OPENVPN_USER OPENVPN_PASSWORD I don't see why you couldn't use PiHole for that purpose. You would need to set these variables: DOT=off DNS_PLAINTEXT_ADDRESS=<PiHole IP> You shouldn't need to Add the variables, just change them in the template. Also, the dev has an extensive Wiki on the various settings here: https://github.com/qdm12/gluetun/wiki

The dev has rolled back the last change. You should be able to do a force update on the container and be moved working again.

That looks like 2 issues. Make sure you set the Network Type drop-down to None Looks like the port used for LibreSpeed is either attached to both the LibreSpeed and Gluetun containers or the port is already in use by something else. The simplest way is to open the terminal for the container and run the below command apk add speedtest-cli && speedtest-cli

Just a little back story... Originally for containers on Unraid, you only needed to add the individual ports as variables to the VPN container that were needed. This was largely a security flaw within the iptables settings (the rules VPNs use to determine if traffic is allowed). With that flaw patched you still need to specify the ports in individual variables so that Unraid knows which ports go to which containers but you also add the list of ports to the ADDITIONAL_FIREWALL_INPUT_PORTS so that the VPN itself know it's OK to allow those ports to communicate into the VPN tunnel. Also, just a heads up, I will be pushing a new template out either today to tomorrow (hopefully) that includes lots of changes. You may have to re-enter info as some of the variable names have changed to align with the dev's variable names. I understand this might break users configurations temporarily but I would rather rip the band-aid off sooner than later.

Can you post the Gluetun conatiner log after you try to start it?

Just wanted to let you know that the dev added a "custom" option for "VPN_SERVICE_PROVIDER". I plan on getting the template updated with it and any relevant variables sometime today.

Restart Gluetun and make sure that there aren't any errors staring up in the log. Then refresh the page and double check the nzbget and sonarr network settings. Whenever you change settings in a template it recreates the container with a new GUID. Since sonarr and nzbget use that to determine the container to use as the network connection.

Try putting the CIDR for your local subnet (usually something like 192.168.0.0/32 or 10.0.0.0/16) in the FIREWALL_OUTBOUND_SUBNETS variable.

I'll be glad to help figure this out. Can you post a screenshot of you Glutune config? Obviously, black out any IPs, subnets, username/passwords, etc.