Jump to content

strike

Members
  • Content Count

    502
  • Joined

  • Last visited

Community Reputation

56 Good

About strike

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Don't worry about the port forwarding if you're using PIA, all you need to do is use one of the endpoints that support it. But as PIA is doing network changes I understand that some endpoints don't work right now, which possibly results in heavy load on the few that works.
  2. Then I'm out of ideas. Check the itconfig plugin as mentioned, might help. That's because I'm using the thin client on windows not the webui
  3. I'm fairly certain it has nothing to do with your container settings but here is my docker run command, you can see my settings from that: My template is old tho, so it may differ from yours. The important settings in deluge related to speed are these: Just the incoming port. And peer exchange,dht and lsd should be enabled. Then cap the upoad speed under bandwith. And the test active port in the network settings gives you a check mark I assume? It should when the airvpn port check says it works
  4. Weird.. You can maybe try the itconfig plugin. I've seen others had success with it when everything else has failed. I've never used it as I always get max speed. But search for itconfig in this thread and you should be able to find the correct settings for it. Use google's "site" option, it's much better then the forum search. I don't know if the plugin is updated to work with version 2 tho..
  5. First of all, if you haven't done it already, put a cap on the global upload speed to about 80% of what your connection can handle. This in done in the deluge settings. Not doing so will actually slow down your download and your hole network. This is because torrenting constantly have hundreds of connections open. Second, download a new ovpn file with only servers in the Netherlands, use port 443 udp which is default I think. Did that help? And of course, be sure to set the correct incoming port in deluge
  6. Make sure to only use characters A-Z,a-z,0-9 in your username/pw. Special characters can cause authentication issues. Also make sure you're within your providers device limit. Usually they allow 1-x devices and anything over that will fail to authenticate.
  7. I'm using this config with a subdomain: # make sure that your dns has a cname set for whoogle and that your whoogle container is not using a base url # if whoogle is running in bridge mode and the container is named "whoogle", the below config should work as is # if not, replace the line "set $upstream_app whoogle;" with "set $upstream_app <containername>;" # or "set $upstream_app <HOSTIP>;" for host mode, HOSTIP being the IP address of whoogle server { listen 443 ssl; listen [::]:443 ssl; server_name whoogle.*; include /config/nginx/strong-ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app whoogle-search; set $upstream_port 5000; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; Note that "strong-ssl.conf;" is specific to my setup. Yours should be just include /config/nginx/ssl.conf; Just paste the above in a file and call it whoogle.subdomain.conf and place it in /letsencrypt/nginx/proxy-confs (assuming you're using LSIO's letsencrypt container) Still having some issues in chrome, gets a 522. Works fine in firefox tho, will have to look into that.
  8. Could use some help here. Started using cloudflare dns validation 3 months ago, and now my cert is due for renewal but it fails. Looking at the log it seems like the process never fully completes. It just stops, or at least the logging stopped. For about 10-15 days now all that's in the log is this: cronjob running on Mon Jun 29 02:08:00 CEST 2020 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/mydomain.com.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert is due for renewal, auto-renewing... Non-interactive renewal: random delay of 87.04891948754788 seconds Plugins selected: Authenticator dns-cloudflare, Installer None Renewing an existing certificate Performing the following challenges: dns-01 challenge for emby.mydomain.com dns-01 challenge for mydomain.com dns-01 challenge for ombi.mydomain.com Unsafe permissions on credentials configuration file: /config/dns-conf/cloudflare.ini Cleaning up challenges <-------------------------------------------------> Then finally 2 days ago it got a little further and actually produces an error: cronjob running on Tue Jun 30 02:08:00 CEST 2020 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/mydomain.com.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert is due for renewal, auto-renewing... Non-interactive renewal: random delay of 326.6042396698244 seconds Plugins selected: Authenticator dns-cloudflare, Installer None Renewing an existing certificate Performing the following challenges: dns-01 challenge for emby.mydomain.com dns-01 challenge for mydomain.com dns-01 challenge for ombi.mydomain.com Unsafe permissions on credentials configuration file: /config/dns-conf/cloudflare.ini Cleaning up challenges Attempting to renew cert (mydomain.com) from /etc/letsencrypt/renewal/mydomain.com.conf produced an unexpected error: Unable to determine zone_id for ombi.mydomain.com using zone names: ['ombi.mydomain.com', 'mydomain.com', 'tv']. Please confirm that the domain name has been entered correctly and is already associated with the supplied Cloudflare account. The error from Cloudflare was: 0 connection failed.. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/mydomain.com/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/mydomain.com/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Running post-hook command: if ps aux | grep [n]ginx: > /dev/null; then s6-svc -h /var/run/s6/services/nginx; fi; cd /config/keys/letsencrypt && openssl pkcs12 -export -out privkey.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem -passout pass: && sleep 1 && cat privkey.pem fullchain.pem > priv-fullchain-bundle.pem 1 renew failure(s), 0 parse failure(s) <-------------------------------------------------> How do I solve this? I've checked my cloudflare account and I have created a CNAME for both my subdomains to my duckdns domain. But I see I have 2 TXT records for my emby subdomain and none for my ombi subdomain. Maybe that's the issue? Because the log only mention that it fails for my ombi subdomain? Edit: Solved.. It was my firewall blocking cloudflare
  9. This container does not support br0 at this time. Switch to bridge. Or use the deluge desktop/thin client to get access over br0, that might work. See the faq for how to connect with the deamon.
  10. I see you have PIA as your provider. The port forwarding is done automatically for PIA in this container and the log shows that you have got an incoming port so you should be able to upload. Unless you changed the port in deluge yourself, which you shouldn't be doing for PIA.
  11. Does your vpn provider support port forwarding? If not, that's why your unable to upload anything. If it does support it you need to open up an incoming port and set that port in deluge.
  12. Really? Well, at least then it's working. But are you sure they were finished downloads and not in the process of being downloaded? Didn't really see anything special in the log. What does the log say? And please remove that last screenshot, don't show what you're downloading unless it's completely legal.
  13. @SpaceInvaderOne has some great youtube videos about vm performance/setting up a vm I think. There are also some forum posts discussing performance but I don't have the links.
  14. The docker run command is the command that starts/creates the container and shows all your mappings/ports. But a screenshot works just as good If someone ask you to post your docker run command you can get it by editing the container, change one setting and change it back then hit apply. Then a window will pop up with the docker run command. All your volume mappings looks good btw But you don't use deluge to download torrents? You only use the privoxy part? I see you have 37 torrents there but none of them have labels. You really need to use labels, if you don't use them all your movies and shows will all end up in the complete folder. Then sonarr/radarr will have a headache trying to figure out what is a movie and what is a show (since they all end up in the same place) and your log will be filled with errors. I see you have created 2 labels in deluge, so you should set them up in sonarr/radarr under the downloader section so they pass the label to deluge. Then right click the label in deluge and go to the location tab and apply the location settings and put in the correct path. Should be /data/completed/rararr and /data/completed/tv-sonarr. If done correctly deluge should put all the completed movies in a folder called radarr and all the completed shows in tv-sonarr on the complete folder. I don't use sab, but it seems like it has the same thing, but it's called categories? If so they should be named the same as the labels. When you have done all that it should theoretically work. If not take a look at the log in sonarr/radarr to see what the issue is. That being said it should theoretically work the way you have set it up now too, but as I said sonarr/radarr might be fighting a headache trying to find out whats what since everything now ends up in the same place.