biggiesize
-
Posts
131 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by biggiesize
-
-
29 minutes ago, NLS said:
Error response from daemon: No such container: gluetun
I assume you meant:
docker start ddns-updater
...which producted this:
ddns-updater...and then back to command prompt.
And no, the container doesn't actually start.
How can I try an older version maybe?
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
-
11 minutes ago, NLS said:
I know about NGINX, but I haven't yet found time to deal with that. It CAN happen to fill the logs (I have deleted them manually twice).
No the system normally has more RAM free. It is not a RAM issue.
docker run gluetun? Exactly like that?
Unable to find image 'gluetun:latest' locally
docker run ddns-updater
Unable to find image 'ddns-updater:latest' locally
...I am sure I do something wrong.
Sorry...I gave the wrong command... It SHOULD be, exactly:
docker start gluetun
-
6 hours ago, NLS said:
I *think* there is no mention about ddns-updater container anywhere - but I can assure you I have it in my list of installed containers, I even removed it and re-added it 3 times.
quasar-ultima-diagnostics-20220113-1525-anon.zip 228.86 kB · 0 downloads
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.
-
24 minutes ago, xiongster said:
Getting error for wrong credentials. All detailes filled my me- Selecting PVN, VPN eamail and password and REGION.
Is this a new install or was it previously working?
-
8 hours ago, NLS said:
Just change the name? No, I will try.
I cannot see the logs (through the menu at least), as since the container is off, the log window just pops and closes.
Is there another way to find logs for it?
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.
-
1
-
-
4 hours ago, NLS said:
HELP!?
ddns-updater stopped working.
When I start the container, it just immediately stops.
No errors pop up.
I removed (and the image) and reinstalled from user template (that worked fine from months).
Same thing.
Any ideas?
How can I debug this?
I need this functionality.
Hmmm, haven't seen that one yet. Is there anything in the logs? Have you tried creating it under a different app name?
-
4 hours ago, NLS said:
HELP!?
ddns-updater stopped working.
When I start the container, it just immediately stops.
No errors pop up.
I removed (and the image) and reinstalled from user template (that worked fine from months).
Same thing.
Any ideas?
How can I debug this?
I need this functionality.
Hmmm...have seen that one yet. Is there anything in the logs? Have you tried creating it under a different app name?
-
7 hours ago, lovingHDTV said:
Things are running fine now. Sonarr can successfully send requests to qbittorrent and nzbget and import the resulting downloads.
In order to get nzbget to work I had to disable DOT. When I enable DOT, nslookup in GluetunVPN, nzbget and the other dockers it fails to work. I get the following:
sh-5.1# nslookup secure.usenetserver.com Server: 127.0.0.1 Address: 127.0.0.1#53 ** server can't find secure.usenetserver.com: NXDOMAIN sh-5.1# nslookup www.google.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: www.google.com Address: 142.250.191.196 Name: www.google.com Address: 2607:f8b0:4009:81a::2004This is true for the two docker I have that have nslookup installed. My DOT settings are fairly default. I just changed to quad9.
Is there something I need to change in each docker to get this to work?
If I run it on the unraid machine I get:
root@tower:/mnt/cache/appdata/gluetun# nslookup secure.usenetserver.com Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: secure.usenetserver.com canonical name = news.usenetserver.com. news.usenetserver.com canonical name = us.na.news.geo.usenetserver.com. us.na.news.geo.usenetserver.com canonical name = news.iad.usenetserver.com. Name: news.iad.usenetserver.com Address: 85.12.62.221 Name: news.iad.usenetserver.com Address: 85.12.62.240thanks
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.
-
41 minutes ago, Ruffy said:
Hello thanks for the docker, but i have the problem that i can not route other container trough it.
i have setup the container (maybe there is a beginner friendly tutorial somewhere).
have manually setup a custom network named gluevpn
deleted the ports from the other containers and created the standard port in gluetun (as a new port), but it will not work
Did you also put the port in the FIREWALL_VPN_INPUT_PORTS variable?
-
11 minutes ago, Marshalleq said:
Thanks, so linking those with this, they both support using a proxy? I've been using all in one containers up til now, but some recent changes in the binhex one has made me look elsewhere.
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 -
8 minutes ago, Marshalleq said:
So the container installed easily enough. What are people doing for a torrent application? I'd rather have this on unraid than on my local machine - any votes for best container? Thanks.
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.
-
3 hours ago, NLS said:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='ddns-updater' --net='bridge' -e TZ="Europe/Athens" -e HOST_OS="Unraid" -e HOST_HOSTNAME="quasar-ultima" -e HOST_CONTAINERNAME="ddns-updater" -e 'TZ'='Europe/Athens' -e 'PUBLICIP_FETCHERS'='all' -e 'PUBLICIP_HTTP_PROVIDERS'='all' -e 'PUBLICIPV4_HTTP_PROVIDERS'='all' -e 'PUBLICIPV6_HTTP_PROVIDERS'='all' -e 'PUBLICIP_DNS_PROVIDERS'='all' -e 'PUBLICIP_DNS_TIMEOUT'='3s' -e 'UPDATE_COOLDOWN_PERIOD'='5m' -e 'HTTP_TIMEOUT'='10s' -e 'BACKUP_PERIOD'='0' -e 'LOG_LEVEL'='info' -e 'LOG_CALLER'='hidden' -e 'ROOT_URL'='/' -e 'SHOUTRRR_ADDRESSES'='' -e 'HEALTH_SERVER_ADDRESS'='127.0.0.1:9999' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8000]' -l net.unraid.docker.icon='https://github.com/DiamondPrecisionComputing/unraid-templates/blob/main/templates/img/ddnsgopher.png?raw=true' -p '8001:8000/tcp' -v '/mnt/user/appdata/ddns-updater':'/updater/data':'rw' -v '/mnt/user/appdata/ddns-updater/backup':'/updater/data':'rw' 'qmcgaw/ddns-updater' docker: Error response from daemon: Duplicate mount point: /updater/data. See 'docker run --help'. The command failed.So it seems to want to use /updater/data both for the normal and the backup directory.
I cannot edit the script BUT I run the command above myself with the proper changes.
Seems to run fine, when I changed the second path to /updater/data/backups.Yet this needs to be fixed properly.
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.
-
50 minutes ago, docfallingapart said:
OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: "bash": executable file not found in $PATH: unknown
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".
-
55 minutes ago, Enphor said:
Hello, First thank you for your work on these apps.
I'm trying to use ddns-updater with Dreamhost. I have it working, however, when I try to use the host: directive in the config.json file, it yells at me that only "@" is supported. Am I unable to update other hostnames such as www.domain.com instead of juse domain.com?
Thank you!
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
-
37 minutes ago, schuu said:
Could not resolve hostname news.usenetserver.com: Error -2 - Name or service not known
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.
-
9 hours ago, darrenyorston said:
Hello all. Im trying to set up the container to work with ProtonVPN. There are a lot of config options in the container template; I dont know which are required or not. Im wanting to use the container as a proxy for certain browsers on some of my devices. I was hoping that I could use my local PiHole for DNS/Adblocking if at all possible. Anyone able to share a sanitised version of their config?
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:
-
2 hours ago, jimmy898 said:
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.
-
1 hour ago, ainuke said:
Error response from daemon: conflicting options: port publishing and the container type network modeThat 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
-
29 minutes ago, ainuke said:
Sorry, that was my bad. I was looking too far up in the log; the http server error was from when it was shutting down.
Everything is working now, although to get access to the containers' UI (NZBGet and Sonarr) on the LAN, their ports need to be manually specified/added. From the description, I thought that was the purpose of ADDIDIONAL_FIREWALL_INPUT_PORTS?
Not really worried about it at this point, given that it's functional; just curious.
Thanks for your help!
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.
-
10 minutes ago, ainuke said:
I'm getting a "ERROR http server: http: Server closed" error when restarting Gluetun, with both the other containers stopped.
Can you post the Gluetun conatiner log after you try to start it?
-
On 8/21/2021 at 10:27 AM, Opawesome said:
@biggiesize, if I may: how about adding a choice like "other/custom" in the dropdown menu for the "VPN_SERVICE_PROVIDER" variable in your docker container template, as well as adding the variable "OPENVPN_CUSTOM_CONFIG" right after, with a nice little description such as "OPTIONAL if you selected 'other/custom' in the 'VPN_SERVICE_PROVIDER' list above, please enter here the path to the .ovpn configuration file that Gluetun should use. https://github.com/qdm12/gluetun/wiki/Openvpn-file" ?
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.
-
36 minutes ago, ainuke said:
Ok, did that, but now when I start sonarr or nzbget containers, I get "Execution Error No such container"
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.
-
1 hour ago, ainuke said:
"Error: ConnectFailure (No route to host): 'http://**.*.*.***:6789/jsonrpc'".
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.
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
in Docker Containers
Posted
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.