Earache

Anyone using nzbToMedia? I'm getting this error which causes everything to download but not process. nzbToMedia: Exception TypeError: "'NoneType' object is not callable" in <bound method PosixProcess.__del__ of <core.nzbToMediaUtil.PosixProcess object at 0x148737796710>> ignored

Would this be done via the docker config the nginx config?

Can you use multiple domains with this?

I'm getting this now... Post-process-script nzbToMedia-nightly/nzbToNzbDrone.py ... failed (terminated with unknown status) All the settings are correct so I don't understand what is happening here...

IPV6 not working at all. ifconfig does not show an IPV6 address at all, while unRAID has one set.

Has anyone setup a reverse proxy for Grafana? I've found a solution in the tutorial on reddit but it doesn't work. I'll quote it so people don't have to go searching. If anyone is still stuck set the env variable for the root url in the container to: root_url = %(protocol)s://%(domain)s:%(http_port)s/grafana and then use the following for the nginx.conf: location /grafana/ { proxy_pass http://IP_HERE:3000/; } This doesn't work for myself. Anyone have a solution?

Care to PM me the template?

I would be willing to test it as the current container doesn’t work for me. I can’t find an answer to the question of does my ISP block port 80.

I'm trying to do this via the Nginx container and adding certbot to it but I'm stuck adding the cert to Nginx. Anyone have a guide on how to do it this way (I believe people were doing it this way before).

Nope still get Failed authorization procedure. sub.domain.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://sub.domain/.well-known/acme-challenge/dcVgooswjuwm_DhQXskQSuKDbRdmN4qKyZTxbDzFg9g: Timeout ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

Rogers Internet (Canada). They apparently don't block it so I don't know wtf is going on. I'm using an EdgeRouter Lite, so either my port-forwarding is farked or Rogers decided to block the port?

Hmm, I'm not sure because this was working with duckdns.org before it broke, and now it won't even work with duck.

I'm trying to use my own domain (namecheap) but either I setup the DNS wrong or I'm missing something. I have my docker on seperate IPs (example 192.168.1.4, .5,.6 etc) and I'm not sure if this is causing the issue or not. I have ports forwarded properly. If I run a dns lookup for the subdomain.domain I see my public IP, but I'm getting this error in the log: Failed authorization procedure. subdomain.domain (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://subdomain.domain/.well-known/acme-challenge/o9FHDJfbOQWeotQxma9kLk-AT5iRiBRyXXNKHn5zvgQ: Timeout, subdomain.domain (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://subdomain.domain/.well-known/acme-challenge/mKVzhGyDzD0_QHj3YQ0fA4VW9tykyzkvdees4r9nTWw: Timeout, subdomain.domain (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://subdomain.domain/.well-known/acme-challenge/jtizzEhlv4utMnBqMCauCIrR48_gkzx7kuak5JaWZH0: TimeoutIMPORTANT NOTES:- The following errors were reported by the server:Domain: subdomain.domainType: connectionDetail: Fetchinghttp://subdomain.domain/.well-known/acme-challenge/o9FHDJfbOQWeotQxma9kLk-AT5iRiBRyXXNKHn5zvgQ:TimeoutDomain: subdomain.domainType: connectionDetail: Fetchinghttp://subdomain.domain/.well-known/acme-challenge/mKVzhGyDzD0_QHj3YQ0fA4VW9tykyzkvdees4r9nTWw:TimeoutDomain: subdomain.domainType: connectionDetail: Fetchinghttp://subdomain.domain/.well-known/acme-challenge/jtizzEhlv4utMnBqMCauCIrR48_gkzx7kuak5JaWZH0:TimeoutTo fix these errors, please make sure that your domain name wasentered correctly and the DNS A/AAAA record(s) for that domaincontain(s) the right IP address. Additionally, please check thatyour computer has a publicly routable IP address and that nofirewalls are preventing the server from communicating with theclient. If you're using the webroot plugin, you should also verifythat you are serving files from the webroot path you provided.- Your account credentials have been saved in your Certbotconfiguration directory at /etc/letsencrypt. You should make asecure backup of this folder now. This configuration directory willalso contain certificates and private keys obtained by Certbot somaking regular backups of this folder is ideal.ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container On namecheap I have every subdomain as A +Dynamic DNS Record (using their DNS Client to update the ip). I'm really stumped.

I've had to manually add them all, which is annoying.

Not sure what you mean by not allowing VPN website access. Port forwarding is handled automatically if you are using PIA, and then only if you are using one of the gateways that has it enabled. If you are using another VPN provider, you will need to refer to their support to figure out if they even support incoming ports, many VPN providers don't. Meaning when I'm on the trackers site, I'm not connected via VPN, therefore the docker reports whatever VPN I'm connected to (example 10.10.1.10) where my actual IP is 104.104.12.192. The tracker I'm using doesn't show me any stats (no ratio, dl, upld etc).

the only optional port to forward is for the web interface, and thats only if you want to get access to rutorrent whilst out and about. all other ports are talking over the vpn tunnel, so you dont need to worry about opening up an incoming/outgoing port on your router for torrent traffic. None of my private trackers are reporting I'm seeding/leeching. I set the report ip to my actual IP (seeing how they don't allow VPN website access). Is there something I'm doing wrong?

I can't seem to figure out what ports to forward, I'm using the default setup, anyone mind helping?

Tried that didn't work. I made 1 edit to external_url (added the http://192.168.1.2:45300), but I'm getting "404 File not found", if I check the logs I see "401 unauthorized while accessing".

Ya I tried for an hour, constantly hitting IP:Port but nothing changed. Need to keep digging I guess.

Looks like mine. Other users experienced that error aswell. (https://gitlab.com/gitlab-org/omnibus-gitlab/issues/721) Could you try to delete the docker, wipe /mnt/cache/appdata/gitlab-ce and try to install it from stracth? Ok did what you suggested, but I get either "Site can't be reached" or it changes the IP address of my unRAID box to chars. Example: IP is 192.168.1.2 (Gitlab is point to port 45300), opening the webui it takes me to the site but then redirects to http://5a2ef303db9f/users/sign_in. Here's the log http://pastebin.com/L7p6N7Zg. It looks like its the SHA2 key (root@5a2ef303db9f). Any ideas? Use a direct link (like i suggested in a previous post). In Your case http://192.168.1.2:45300/users/sign_in I have yet to figure out why it's changing the ip address to these chars. It started on that 2 days ago when they pushed the last update. The direct link takes me to: http://5a2ef303db9f/users/password/edit?reset_password_token=3yaDdMTpS3DKxbydzfdJ. :o Whenever it inserts those magic chars just replace it with the correct IP/Port. Eventually it will work after all has been setup. Remember to use the root user for the intial login. I will try to figure out why the IP gets replaced with those chars. Nope, what do you mean by "setup"?

I believe this has something to do with config.yml under gitlab-ce/data/gitlab-shell

Looks like mine. Other users experienced that error aswell. (https://gitlab.com/gitlab-org/omnibus-gitlab/issues/721) Could you try to delete the docker, wipe /mnt/cache/appdata/gitlab-ce and try to install it from stracth? Ok did what you suggested, but I get either "Site can't be reached" or it changes the IP address of my unRAID box to chars. Example: IP is 192.168.1.2 (Gitlab is point to port 45300), opening the webui it takes me to the site but then redirects to http://5a2ef303db9f/users/sign_in. Here's the log http://pastebin.com/L7p6N7Zg. It looks like its the SHA2 key (root@5a2ef303db9f). Any ideas? Use a direct link (like i suggested in a previous post). In Your case http://192.168.1.2:45300/users/sign_in I have yet to figure out why it's changing the ip address to these chars. It started on that 2 days ago when they pushed the last update. The direct link takes me to: http://5a2ef303db9f/users/password/edit?reset_password_token=3yaDdMTpS3DKxbydzfdJ. :o

Looks like mine. Other users experienced that error aswell. (https://gitlab.com/gitlab-org/omnibus-gitlab/issues/721) Could you try to delete the docker, wipe /mnt/cache/appdata/gitlab-ce and try to install it from stracth? Ok did what you suggested, but I get either "Site can't be reached" or it changes the IP address of my unRAID box to chars. Example: IP is 192.168.1.2 (Gitlab is point to port 45300), opening the webui it takes me to the site but then redirects to http://5a2ef303db9f/users/sign_in. Here's the log http://pastebin.com/L7p6N7Zg. It looks like its the SHA2 key (root@5a2ef303db9f). Any ideas?

http://i.imgur.com/gMZ6vhX.png The config.