Conversation

Notices

1. John Mastodon :verified: (sam@froth.zone)'s status on Wednesday, 15-Feb-2023 01:42:01 JST John Mastodon :verified:
   adding privoxy to the list of things that have shit documentation
   •  (mint@ryona.agency)'s status on Wednesday, 15-Feb-2023 01:42:00 JST 

     in reply to
     @sam It should be like that by default, I haven't done any changes aside from adding forwards on mine.
   •  (mint@ryona.agency)'s status on Wednesday, 15-Feb-2023 01:45:19 JST 

     in reply to

     • 
     @sam Recheck the config, the dot after the upstream proxy address is apparently important.
     forward-socks5t .onion 127.0.0.1:9050 .
   • John Mastodon :verified: (sam@froth.zone)'s status on Wednesday, 15-Feb-2023 02:48:51 JST John Mastodon :verified:

     in reply to

     • 

     @mint here is the entire config I am using

     user-manual /usr/share/doc/privoxy/user-manual confdir /etc/privoxy listen-address 127.0.0.1:8118 toggle 1 enable-remote-toggle 0 enable-edit-actions 0 enable-remote-http-toggle 0 max-client-connections 65535 buffer-limit 4096 forward / . forward-socks5t .onion 127.0.0.1:9050 . forward-socks5t .i2p 127.0.0.1:4447 .

     the rest of the directory /etc/privoxy is whatever Debian defaults it to :retard: so I am thinking it is probably an Akkoma problem

     the only proxy config option I have is setting the HTTP proxy so who knows

      likes this.
   •  (mint@ryona.agency)'s status on Wednesday, 15-Feb-2023 02:53:52 JST 

     in reply to
     @sam Yeah, mine is exactly the same, so it's likely an Akkoma moment, paired with universally abysmal quality of HTTP adapters supported in Tesla. I remember that they removed bindings for all the adapters except Finch, and it looks like this Finch has trouble with proxying plain HTTP (as messages from froth failed to deliver to my clearnet HTTP-only instance as well).
     https://akkoma.dev/AkkomaGang/akkoma/commit/364b6969eb7c79e57ed02345ddff4f48519e6b0a
   •  (mint@ryona.agency)'s status on Wednesday, 15-Feb-2023 02:57:38 JST 

     in reply to

     • 
     @sam One would have to either restore support for other adapters (Hackney is rather stable, but can't follow redirects with proxy enabled, that's what I'm stuck at since everything else is just worse) or maybe set up system-wide access to hidden webservers.
     https://gitgud.io/CrunkLord420/socks-nginx-module
     If I'm correct about my assumption what it does, it should be possible to set up nginx to proxy everything from Tor with wildcard server_name, bind it to local address and set up local DNS server to resolve *.onion to that address.