~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%acetone
%snex
+Atticfire
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Over
+fa
+marek22k
+onon_
+poriori
+profetikla
+qend-irc2p
+r00tobo
+sexy
+uberius
+uop23ip
Arch
Danny
Irc2PGuest21708
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest99986
RTP_
U1F642
Watson
ahiru
anontor
cims
i2potus
interesting
justaperson
lokzz
luvme3
mahlay
makoto
n2_
nilbog
not_bob_afk
pinotto
r00tobo[2]
rednode
sahil
user_ygg2_
trial_
Y'all thanks for letting me speak <3
trial_
Now I only have one browser launching, good news! thanks a lot
not_bob_afk
I'm glad it's working well for you.
trial_
But bigger issue (see #i2p room so far) : homepage won't load
not_bob_afk
Which page won't load?
trial_
127.0.0.1:7667 -> Unable to connect
not_bob_afk
Oh, your local router page.
trial_
i2p people told me to reach 127.0.0.1:7657/home which works, but default homepage doesn't remember to go there
not_bob_afk
Are you trying to connect from the same machine that I2P is running on?
trial_
yes
trial_
i am
not_bob_afk
OH, so the http version works, not the https version?
not_bob_afk
If that's the case, just use the http version and ignroe the https side.
not_bob_afk
I'm pretty sure HTTPS is enabeld by default. But *shakes head*
not_bob_afk
Though, I'm likely not the person to know the most about that as I tend to run i2pd on most of my instances.
trial_
127.0.0.1:7667 -> unable to connect
trial_
127.0.0.1:7667 -> unable to connect
not_bob_afk
That's very odd.
trial_
127.0.0.1:7657/home -> Secure connection failed
trial_
127.0.0.1:7657/home -> works
trial_
my ~/i2p/clients.config :
not_bob_afk
Ok, just use 127.0.0.1:7657/home and call it a day.
trial_
clientApp.0.args=7657 ::1,127.0.0.1 -s 7667 ::1,127.0.0.1 ./webapps/
not_bob_afk
can you access other things from there like 127.0.0.1:7657/tunnelmanager
trial_
clientApp.1.args=sam.keys 127.0.0.1 7656 i2cp.tcp.host=127.0.0.1 i2cp.tcp.port=7654
trial_
clientApp.4.args=http://127.0.0.1:7657/
trial_
0xpaste.i2p -> doesn't work
not_bob_afk
Can you reach any eepsites?
trial_
zzz.i2p -> works (it's a dev site)
not_bob_afk
Ok
not_bob_afk
In your proxy setup did you exclude 127.0.0.1 from being run through the proxy?
trial_
127.0.0.1:7654 -> The connection was reset
not_bob_afk
Odd
not_bob_afk
I'm not sure what to suggest at this point. It should just work.
trial_
firerox > settings > search "proxy" > settings > No proxy for : 192.168.1.0/24,192.168.42.0/24
trial_
i'm using librewolf
not_bob_afk
I use port 7667 to access my I2P_+ instance.
not_bob_afk
Add in 127.0.0.1
trial_
done,
trial_
127.0.0.1:7667/home -> Unable to connect
not_bob_afk
Try it with https?
trial_
should I restart the browser now that I added another "no proxy for" ?
not_bob_afk
That's the https port.
not_bob_afk
That can't hurt.
trial_
127.0.0.1:7667/home -> Unable to connect
not_bob_afk
And you added 127.0.0.1 for no proxy?
trial_
yes
not_bob_afk
That should not require a restart to take effect, but it can't hurt.
not_bob_afk
Have you tried another browser?
not_bob_afk
Can you telnet to the port directly?
not_bob_afk
To verify that it's actually open?
trial_
Yes, initially smh $ i2prouter start
trial_
was launching both brave and librewolf
not_bob_afk
Does it work in brave?
trial_
brave was indeed fetching the homepage, I think only one digit was differing
not_bob_afk
If that works, then it has to be a config issue with the other browser.
trial_
like, if librewolf default is :7667, then brave was getting it with its default being :7657
trial_
then I uninstalled brave as I don't use it anymore and I wanted only librewolf to fire up
not_bob_afk
*nod*
trial_
but then it used to launch both chromium and librewolf
not_bob_afk
I use more than one browser on my setup.
trial_
which chromium did manage to get to homepage too, on :7657 iirc
not_bob_afk
Each browser for a specific task.
trial_
but librewolf won't get to homepage at fireup :'(
not_bob_afk
Does it work in chromium?
trial_
yes it worked in brave and chromium
not_bob_afk
Then it has to be something with librewolf :(
not_bob_afk
You could just use chromium to access the console, and librewolf for everything else I2P related.
trial_
then someone from here or #i2p helped me to fix these double launches, for me to keep only librewolf
not_bob_afk
Normally you don't need to access the console.
trial_
I see
trial_
can I just put a custom URL to librewolf homepage?
not_bob_afk
I would assume so, it's a firefox fork.
not_bob_afk
But, I've not used it.
trial_
thanks, restarting to see whether it fixes it, brb as it'll reset router for few mins
not_bob_afk
Yeah, give it a good 5 min or so to access I2P sites. But, the console should work right away.
RN
7667 requires https and is default in Plus
dr|z3d
when someone like trial turns up and starts asking about console ports, the _first_ thing you should be asking him is what he's running.
dr|z3d
if I2P, :7657, if I2P+ :7667 .. either way, he shouldn't need to edit anything. at most, he might need to clear his browser cache.
dr|z3d
also relevant is how he's accessing his console. if he's doing it over ssh, then he needs to make sure the correct port is being mapped.. ssh doesn't like redirecting from http to https.
RN
yep, covered the port numbers per flavor, I didn't notice their install method or os etc.. the basics... when I skimmed what was said
RN
but sounds like they followed some youtube 'how to I2P' that included a custom browser profile...
RN
I didn't watch it, rumor was watching youtube gives you cancer or genital warts or anal leakage or some damn side effect
RN
tried tube.i2p but it was in maintenance
dr|z3d
lol
dr|z3d
youtube are battling invidious continually and tube.i2p, which relies on invidious indirectly is a casualty of that. needs some work to integrate with what the current invious workaround is.
cumlord
yeah seems none of the invidious i2p instances are working, watch?v=8Ls-MJRDTs8 was the video
RN
yup
dr|z3d
invidious itself needs to be constantly updated to keep working.
RN
not gonna risk any of the side effects... but I suspect there is a part in the tto that is either wrong or unclear
dr|z3d
tube.i2p isn't invidious, but relies on it for linkage.
RN
gotcha
cumlord
my anus is bleeding profusely now, but setup seemed like it was supposed to start/stop i2p when you open libreworf so it'd work like tor
RN
yeah that part was causing some of their troubles...
RN
and they were starting with cli instead of starting the browser
dr|z3d
any more talk about bleeding anus and I'll add to the bleed with a big fat boot. :)
RN
they kept saying they were doing 'i2prouter start'
RN
heheh, I didn't start it, I just didn't stop it
cumlord
i didn't write the medical books
RN
didn't consult any either. LOL
RN
having the router start with the browser - seemed it clsoes when you close the browser... not a good setup
RN
really want I2P running all the time when possible
dr|z3d
yeah, that's a really bad setup if that's the case.
cumlord
dont need to i got that google md
dr|z3d
you'll do fine then, cumlord. just keep eating your daily allowance of rocks and gluing your ingredients to your pizza.
dr|z3d
ok, more graph refinements in the latest + builds. decimal places removed for graph legends, let me know what you think if you're running a dev build.
dr|z3d
I don't think we lose much, if anything, not rendering the legend values with decimal places. They don't add much value, but do add extra visual noise.
dr|z3d
plenty of places where they don't make much sense, either. fractional tunnel counts etc.
dr|z3d
also, the alternate labels feature isn't working entirely as intended, but it's close enough. again, much less visual noise.