Opened 9 years ago

Last modified 7 years ago

#816 accepted defect

I2P error - proxy authentication required

Reported by: DISABLED Owned by: zzz
Priority: minor Milestone:
Component: apps/i2ptunnel Version: 0.9.4
Keywords: review Cc:
Parent Tickets: Sensitive: no


OS: windows xp sp 3
Browser: firefox 17


Attachments (1)

log-router-0.txt (2.7 KB) - added by DISABLED 9 years ago.

Download all attachments as: .zip

Change History (9)

Changed 9 years ago by DISABLED

Attachment: log-router-0.txt added

comment:1 Changed 9 years ago by DISABLED

Today I started i2p router as usual, but got the "I2P error - proxy authentication required" form, rendering browsing eepsites impossible. I have never had such an issue before, nor did I mess with any of the settings (I use default).

comment:2 Changed 9 years ago by zzz

Component: router/generalapps/i2ptunnel

You may have set authentication up long ago and then forgot about it? Or perhaps the migration code that I wrote (0.9.4 switches from plaintext to digest method for proxy authorization) is buggy and it somehow got enabled for you.

Go to and scroll down to 'Local Authorization'. I assume it will be enabled. Uncheck it and save. That should fix it. At the bottom, under 'custom options', you can see the MD5 digests for each of the users who is authorized to use the proxy.

Please report results. Thanks.

comment:3 Changed 9 years ago by zzz

And the publicSigning.key errors in the attachment are completely unrelated - perhaps a permisions problem or something?

comment:4 Changed 9 years ago by zzz

Отказано в доступе = Access Denied

comment:5 Changed 9 years ago by DISABLED

Thankyou for you timely response. I have followed the steps you described by unchecking the "Local Authorisation" checkbox (which was, in fact, enabled), which has resolved the issue, allowing access to eepsites.

Also, I do run i2p under non-admin user with restricted access rights, which might be the cause of confusion with the logs.

However, there were no md5 digests under the Custom options field, as shown on the screenshot below.

Thankyou again for your assistance.

comment:6 Changed 9 years ago by zzz

Owner: set to zzz
Status: newaccepted

ok thanks. Leaving ticket open for now, it's a mystery how authorization got enabled. I'll review the migration code.

comment:7 Changed 8 years ago by str4d

Keywords: review added
Milestone: 0.9.5

comment:8 Changed 7 years ago by str4d

I encountered this problem when I installed the Orchid plugin a few days ago - suddenly requests to *.i2p sites were blocked by proxy auth screens. Checking my HTTP tunnel (which has existed largely untouched for years apart from occasional outproxy changes), the "Local Authorization" box was checked.

Prior to installing Orchid, I had experienced no problems (so I assume the box was not checked then); the only change I made was that after I installed Orchid, I edited the tunnel to remove the listed outproxies. Once I discovered the problem, I edited the tunnel again to uncheck the box, and the problem ceased.

Note: See TracTickets for help on using tickets.