Conversation

Notices

1. Sarreq Teryx (sarreq@social.diva.exchange)'s status on Thursday, 10-Oct-2024 22:17:16 JST Sarreq Teryx

   • diva.exchange

   @social #i2p how do I connect to my docker i2p if it's not on the local machine. I was assuming changing localhost to the server's IP addy, but that's not working at all.

   • diva.exchange (social@social.diva.exchange)'s status on Thursday, 10-Oct-2024 22:17:08 JST diva.exchange

     in reply to

     @sarreq can you make an example, please? To which dockerized i2p service do you want to connect from where?

   • Sarreq Teryx (sarreq@social.diva.exchange)'s status on Friday, 11-Oct-2024 02:48:39 JST Sarreq Teryx

     in reply to

     • diva.exchange

     @social divax/i2p:current-i2p-tor, from windows or linux. your setup guide says to use the setup script from http://localhost:8080/proxy.pac. I thought changing localhost to the server's address would work, but I get no access at all no matter what I do.

   • diva.exchange (social@social.diva.exchange)'s status on Friday, 11-Oct-2024 15:50:19 JST diva.exchange

     in reply to

     @sarreq Thanks!

     Example: the attached mage shows the proxy settings of Firefox related to a locally running docker container divax/i2p:current-i2p-tor. Works AFAIK in all environments.

     I do not understand: what do you mean with "server address"? The divax docker container is designed to run on the same system (aka "host") on which you want to use the proxy services for i2p and tor.

     Please also check the state of your locally running divax docker container (command line: "docker ps -a").

   • Sarreq Teryx (sarreq@social.diva.exchange)'s status on Friday, 11-Oct-2024 23:33:59 JST Sarreq Teryx

     in reply to

     • diva.exchange

     @social I run my docker server on a NAS, and connect a few clients (PCs, tablets, etc) to it for various services. example: my server address is 172.167.2.45, and would like to access this from my various PCs. are you telling me this is for some strange not an option with the divax container? like http://172.167.2.45:8080/proxy.pac is implicitly not a possibility?

   • diva.exchange (social@social.diva.exchange)'s status on Saturday, 12-Oct-2024 02:32:20 JST diva.exchange

     in reply to

     @sarreq Got it. This should work fine. I do something similiar. Now, the proxy.pac is s regular file (it is a small javascript file). So you can download it from any device (like using any browser) within your 172 network and look at it using a text editor. If the download is not working, then the docker container is either not running on your NAS or the docker network on the NAS is restricted. How do you start the container on the NAS?

   • Sarreq Teryx (sarreq@social.diva.exchange)'s status on Saturday, 12-Oct-2024 14:49:35 JST Sarreq Teryx

     in reply to

     • diva.exchange

     @social automatically, or through portainer if it stops itself (hasn't happened yet). the pac file downloads normally through my browser.
     the initial config was done using the "docker run --env PORT_TOR=9950 --env PORT_HTTP_PROXY=4544 --env ENABLE_HTTPPROXY=1 -p 7170:7070 -p 4544:4444 -p 9950:9050 -p 8080:8080 -d --name i2p-tor divax/i2p:current-i2p-tor" command shown on both the github page and the diva.exchange "introduction to i2p" page

   • diva.exchange (social@social.diva.exchange)'s status on Monday, 14-Oct-2024 18:43:23 JST diva.exchange

     in reply to

     @sarreq THANK YOU very much - you spotted a bug in the proxy pac file (which I never saw, because my setup is slightly different). I will fix the bug within the proxy pac and commit a bug fix to github and also to docker.

   • Sarreq Teryx (sarreq@social.diva.exchange)'s status on Monday, 14-Oct-2024 18:43:24 JST Sarreq Teryx

     in reply to

     • diva.exchange

     @social docker ps-a shows: "[containeridhiddenbyme] divax/i2p:current-i2p-tor "/entrypoint.sh" 45 hours ago Up 97 hours 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 0.0.0.0:4544->4444/tcp, :::4544->4444/tcp, 0.0.0.0:7170->7070/tcp, :::7170->7070/tcp, 0.0.0.0:9950->9050/tcp, :::9950->9050/tcp i2p-tor"

   • diva.exchange (social@social.diva.exchange)'s status on Monday, 14-Oct-2024 18:45:26 JST diva.exchange

     in reply to

     @sarreq In a nutshell, the bug within the proxy pac file:

     "
     if ( shExpMatch(host, "*.i2p$") ) {
     return "PROXY localhost:$PORT_HTTP_PROXY"
     }
     return "SOCKS localhost:$PORT_TOR";
     "

     localhost is wrong in this context (in an environment like yours it must be indeed the "server" address, like a NAS).

   • diva.exchange (social@social.diva.exchange)'s status on Tuesday, 15-Oct-2024 01:03:39 JST diva.exchange

     in reply to

     @sarreq The bug is fixed and it is live on docker hub, here: https://hub.docker.com/r/divax/i2p

     The README got updated to reflect the changes regarding "IP_HOST".

     In your specific environment (docker container and hence the i2p/tor proxy running on 172.167.2.45), you start the container like this:

     docker run --env IP_HOST=172.167.2.45 --env PORT_TOR=9950 --env PORT_HTTP_PROXY=4544 --env ENABLE_HTTPPROXY=1 -p 7170:7070 -p 4544:4444 -p 9950:9050 -p 8080:8080 -d --name i2p-tor divax/i2p:current-i2p-tor