mrfrogydog

Members
  • Posts

    6
  • Joined

  • Last visited

mrfrogydog's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Reckon it is within the docker image itself. Check in the docker console if it is in /home/nobody/downloads/ or something to that affect. Make sure you know what folder you are passing to the docker image.
  2. OK so I have an update to the issue I've been having... To be clear as well, the VPN itself works fine, just privoxy/web connections are where I'm having problems. So within the container itself, I can't curl properly to most sites. Let me explain, I can curl the url google.com, which responds with a 301. I can't however, curl www.google.com (different IP). I can't curl example.com. I can curl unraid.net (responds with 301). I can't curl https://unraid.net... It gets as far as trying to establish the TLS handshake and will eventually timeout. So that's weird right? I've checked the iptables, these requests are not being blocked by those rules. Interestingly, if I remove the rules, I can make any request over the eth0 interface. So only when trying to connect over the vpn tunnel will it not work. I'm running out of ideas EDIT: SO I've fixed the problem. If I use TCP openvpn configs, the problem disappears... That's really odd and I can't explain it. I wonder if my ISP or router is doing something funky with my packets. I will have to investigate, but maybe this will be useful to someone else. EDIT 2: After further investigations, it does appear to be a problem somewhere in my ISPs infrastructure. If I connect to the VPN using UDP from within my network using on my phone, it doesn't work; if I connect through TCP it does. UDP works on 4G though, so problem either with router or ISP. Hey-ho, at least I can get it to work.
  3. Huh that is interesting, it's actually something I hadn't noticed. So if I try to connect to the proxy from another docker on the same subnet image (in this case the binhex-jackett one) then I actually get a successful connection to the proxy. Shown below: curl -vvv --proxy 10.0.0.200:8118 https://www.google.co.uk * Trying 10.0.0.200:8118... * TCP_NODELAY set * Connected to 10.0.0.200 (10.0.0.200) port 8118 (#0) * allocate connect buffer! * Establish HTTP proxy tunnel to www.google.co.uk:443 > CONNECT www.google.co.uk:443 HTTP/1.1 > Host: www.google.co.uk:443 > User-Agent: curl/7.66.0 > Proxy-Connection: Keep-Alive > < HTTP/1.1 200 Connection established < * Proxy replied 200 to CONNECT request * CONNECT phase completed! * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CONNECT phase completed! * CONNECT phase completed! ^C I don't actually get a response though, which is unusual. I would expect it to give me the html or whatever, but in this case I have to manually close the program with ctrl-c. I'm quite puzzled; I wonder if there is a problem with the iptables config. Not sure yet.
  4. Probably a useful message shown below: ~# curl -vvv --proxy 10.0.0.200:8118 https://www.google.co.uk * Trying 10.0.0.200:8118... * TCP_NODELAY set * Connected to 10.0.0.200 (10.0.0.200) port 8118 (#0) * allocate connect buffer! * Establish HTTP proxy tunnel to www.google.co.uk:443 > CONNECT www.google.co.uk:443 HTTP/1.1 > Host: www.google.co.uk:443 > User-Agent: curl/7.65.3 > Proxy-Connection: Keep-Alive > * Recv failure: Connection reset by peer * Received HTTP code 0 from proxy after CONNECT * CONNECT phase completed! curl: (56) Recv failure: Connection reset by peer So I try to get the page at google.co.uk (via HTTPS) using curl, through the proxy (at 10.0.0.200:8118) which is the one running on my delugevpn container. It feels like there's a simple config problem with the privoxy, or it's not running properly for some reason. The rest of the container itself is accesible, as is the proxy, however the proxy isn't properly dealing with requests. Worth mentioning also, I have remade the container, tried several versions, completely deleted the config (from appdata), but still have the same problem unfortunately. Appreciate any further help if you have the chance. Many thanks.
  5. Sorry I should have been clearer. Yes I mean a custom docker bridge, not macvlan. Cheers
  6. Hi folks, I'm currently having issues with the privoxy included in this container. When I use the the privoxy in other containers, they won't connect. I used firefox in order to test it, I get a message to the effect of "connection was reset" when I try to connect to any website. Deluge itself works fine, and it is connected to the vpn. I can verify that I can actually connect to the proxy itself, it just seems to bin off any site I send through it. You can view the log from the container here: https://paste.dimdev.org/uboluyutab.coffeescript I couldn't find anything particularly relevant in the log. Any help would be much appreciated, thanks in advanced. Edit: To add a bit more info, the docker is running inside a custom docker network (configured as per our lord and saviors SpaceInvaderOne letsencrypt docker video), and I'm trying to access the proxy through the Unraid server's IP (10.0.0.200:8118).