Notices by Sarreq Teryx (sarreq@social.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"

@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

@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?

@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.

@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.