strike

Members
  • Posts

    771
  • Joined

  • Last visited

Everything posted by strike

  1. There is none in the unraid community but there is one on dockerhub you could try that. Just enable CA to search dockerhub and you should find it. Here is the duckhub link: https://hub.docker.com/r/andymeful/privoxy-openvpn/
  2. I don't understand your question. OpenVPN AS and DelugeVPN are used for completely different purposes. OpenVPN AS is for connecting a vpn tunnel between a remote location to your home network, so you can access your network securely. DelugeVPN is torent client with built-in vpn for creating a vpn tunnel from your home network to a (usually paid) vpn subscription for hiding you real IP adress. Which are you trying to accomplish? Edit: I think I understand now after reading your post again. You just want to use the privoxy feature to be able to route an app through the vpn tunnel? Then no, I don't think there is a "lighter way". The easiest way is to use one of binhex's vpn containers to do that.
  3. From what I can see from your config /downloads isn't mapped to anything. So how can deluge move anything from /downloads when it isn't mapped in your config? Edit: or it's: completed for headphones in your config? I can't see the container mapping so I don't know
  4. Don't think so. Just run both vpn containers, but enable privoxy one just one of them
  5. I think this is the issue. But please post the entire supervisord.log file with debug enabled. Be sure to remove your vpn user/pass
  6. If your router's IP is 192.168.1.1 your Lan_network should be 192.168.1.0/24
  7. @repentharlequin Your LAN_Network is wrong, think it should be 192.168.0.0/24
  8. I think you need to post a new log after you've let the container run for a few min. From the log you posted the container was running just a few seconds.
  9. strike

    Secure SSH

    fail2ban is included in the let's encrypt docker. So I guess you could use that and just create a jail for unraid log, create a voulme mapping to the unraid syslog and put the logpath in the jail config. Should work. There's probably several fail2ban dockers on dockerhub too. But I agree key based login is still the way to go IMO. If you want to use fail2ban you still have to configure it, set up jails etc, which means editing config files. And people who can figure out how to do that can probably set up key based login too if they put their mind to it.
  10. Please enable debug logging by setting the debug variable to true, delete the supervisord.log file, restart the container and let it run for a few min. then post a new log. BUT I strongly suggest you try another VPN provider (AirVPN or PIA are good ones) as you'll get really low speed due to the fact that NordVPN does not support port forwarding.
  11. Have you tried to change the host port to 80 in the docker template like I suggested earlier? In your screenshot it still says 81. I get that it's on its own IP and you have port forwarded 80->80 on that IP but that won't do you any good if the host port in the docker template is still 81. Unless the container ignores that completely when it's on its own IP?
  12. Looks like it's not getting a valid IP from the tunnel. It fails a bunch of times then it's able to get a valid IP one time from what I can see, then it "thinks" it's getting a valid IP but it's really the IP from the tun adapter (I think). Anyway if you were able to get a valid IP from the tunnel it won't do you any good, as private trackers won't work at all and with public trackers you'll get slow speed due to the fact that tigervpn doesn't support port forwarding. As far as I can tell anyway. You'd be better off trying AirVPN or PIA.
  13. You'll also need to change the host port on the container to 80, right now it's 81, if you didn't change it already.
  14. So I finally got around to updating this container. I've been following this thread and expected the container to throw errors and not start until I added the HTTPVAL variable. But it didn't, it started fine with no errors. But maybe this is because my cert is not yet due for renewal? It says so in the log anyway. Or am I missing something here? ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d subdomain.domain.com E-mail address entered: [email protected] <-------------------------------------------------> <-------------------------------------------------> cronjob running on Sun Jan 21 04:48:45 CET 2018 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log ------------------------------------------------------------------------------- Processing /etc/letsencrypt/renewal/subdomain.domain.com.conf ------------------------------------------------------------------------------- Cert not yet due for renewal ------------------------------------------------------------------------------- The following certs are not due for renewal yet: /etc/letsencrypt/live/subdomain.domain.com/fullchain.pem (skipped) No renewals were attempted. No hooks were run. ------------------------------------------------------------------------------- [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Server ready
  15. I just set up my deluge docker with it's own IP and it's working great. It's not on an different NIC tho.. But I don't see why that would make a difference, it's just br0 vs br1. But then again I'm not a network guru of any kind.. I did have problems connecting to radarr and medusa at first, but then I remembered they where configured to use privoxy on the old IP. Once I updated the IP it was all good.
  16. If 192.168.0.11 is your unraid IP, then your Lan_Network in the delugevpn container setting is wrong. You have 1.0/24 at the end you have redacted the rest. So you shound't even be able to get to the webui. But maybe you have changed that after, clearly you must have since you say you can get to the webui.
  17. You have redacted the part I wanted to see... What do you have as the hostname? And it never says in the log that you have tried to connect to 8118. If 192.168.0.11 is your unraid IP address, then that is what the hostname should say. Do not include http(s) or anything else. If you have a working vpn tunnel then all you need to do in radarr is to enable the proxy and put in the correct hostname /port and of course configure radarr to connect with deluge. I also suggest that you move this to the sonarr / radarr thread as this is not a delugevpn issue but sonarr / radarr configuration issue. I have radarr working fine with privoxy .
  18. So what does the log say with 8118 instead of 8113? Radarr I have, could you post a sreenshot of the proxy settings in the general tab in radarr?
  19. First of all just run one of the containers at least until you get everything to work. And do I understand you correctly that it is just privoxy you have have problems with? You have a working tunnel on the delugevpn container and are able to reach the webui with the vpn enabled? You didn't answer my question why your sonarr logs say it tries to connect to port 8113? It should be 8118, are you sure you have set up the proxy in sonarr correctly? Screenshot?
  20. I don't use sonarr so I don't know if I can help, but are you using sabnzbdvpn and delugevpn at the same time? If so, are privoxy enabled on both? Why does it say it tries to connect to port 8113 in the logs? Privoxy runs on 8118 by default
  21. Have you checked the sonarr log, what does it say? I doubt anyone can help without logs.
  22. Last update of this container was 6 days ago, the medusa devs issued a new release on the 26th 3 days ago and linuxserver.io updates all their containers once a week on Fridays IIRC. So there you have it.
  23. This container includes privoxy, with that you can route your browser through the vpn tunnel. Just enable privoxy in the container settings and point your browser's proxy settings to "unraidIP:8118"
  24. Sickrage is basically dead. Have been pretty much since most of the devs went to another fork. Medusa, this a fork of Sickrage and is being actively maintained. Another alternative is Sonarr