Opened 6 years ago

Closed 6 years ago

#1083 closed defect (not a bug)

I2P Start not running after upgrade Avast Internet Security to v9

Reported by: Bisounours Owned by:
Priority: critical Milestone: 0.9.9
Component: apps/jetty Version: 0.9.8.1
Keywords: win 8.1, I2P start Cc:
Parent Tickets: Sensitive: no

Description

I did upgrade last week from win 8 to win 8.1.
Since that time it is impossible to get a start from I2P
I was told on forum to put here some log.
Here attached is the content of I2P start window (hope what is here is enough….)

Subtickets

Attachments (1)

Log I2P Start.txt (15.4 KB) - added by Bisounours 6 years ago.

Download all attachments as: .zip

Change History (7)

Changed 6 years ago by Bisounours

Attachment: Log I2P Start.txt added

comment:1 Changed 6 years ago by killyourtv

Hmm.

jvm 1    | 2013-10-24 14:34:38.573:WARN:oejuc.AbstractLifeCycle:FAILED org.eclip
se.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager@55165e0c: ja
va.io.IOException: Unable to establish loopback connection
jvm 1    | java.io.IOException: Unable to establish loopback connection
jvm 1    |      at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source)
jvm 1    |      at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source)
jvm 1    |      at java.security.AccessController.doPrivileged(Native Method)
jvm 1    |      at sun.nio.ch.PipeImpl.<init>(Unknown Source)
jvm 1    |      at sun.nio.ch.SelectorProviderImpl.openPipe(Unknown Source)
jvm 1    |      at java.nio.channels.Pipe.open(Unknown Source)
jvm 1    |      at sun.nio.ch.WindowsSelectorImpl.<init>(Unknown Source)
jvm 1    |      at sun.nio.ch.WindowsSelectorProvider.openSelector(Unknown Sourc
e)
jvm 1    |      at java.nio.channels.Selector.open(Unknown Source)

This is the problem: Unable to establish loopback connection.

Do you have a firewall enabled (or any other security software) that might be blocking connections to/from the loopback interface? If you have a firewall enabled, try disabling it. If I2P works you'll need to configure your firewall to work with I2P.

I don't have access to Windows 8.1 so I cannot try reproducing this, but we've had reports of successful upgrades to Windows 8.1 and I2P still functioning.

comment:2 Changed 6 years ago by killyourtv

Component: unspecifiedapps/jetty

comment:3 Changed 6 years ago by str4d

Status: newinfoneeded_new

comment:4 Changed 6 years ago by Bisounours

Thanks for answer.

So it doesn't come from windows 8.1 but from Avast Internet Security Firewall.
I2P starts only with firewall disabled.
I enabled full connections for JWrapper without success.
So I don't know what to enable out of Java.

comment:5 in reply to:  4 Changed 6 years ago by killyourtv

Status: infoneeded_newnew

Replying to Bisounours:

Thanks for answer.

So it doesn't come from windows 8.1 but from Avast Internet Security Firewall.
I2P starts only with firewall disabled.
I enabled full connections for JWrapper without success.
So I don't know what to enable out of Java.

I was able to reproduce this in a Windows 7 virtual machine using the Avast Internet Security Firewall trial. I also didn't have any success with the firewall enabled. I didn't see any settings for 127.0.0.1/8. The wrapper and Java were set to unrestricted and the failure persisted.

It's strange that there's nothing blocked according to the firewall logs (but it is obviously blocking I2P). Unfortunately I don't have any ideas to make it work short of disabling the F.W.

If you're a paying Avast customer I think I'd contact them for advice or filing a bug since as I see it it's blocking software from communicating even when it's given unrestricted permissions.

comment:6 Changed 6 years ago by Bisounours

Resolution: not a bug
Status: newclosed
Summary: I2P Start not running after upgrade win 8 to win 8.1I2P Start not running after upgrade Avast Internet Security to v9

I will contact Avast.
Thank for your help.
This is not a I2P bug and I propose to close this ticket.

Note: See TracTickets for help on using tickets.