Opened 4 years ago

Closed 3 years ago

#1748 closed defect (fixed)

'Message expired' on eepsite unreachable page

Reported by: dg Owned by: zzz
Priority: minor Milestone: 0.9.29
Component: apps/i2ptunnel Version: 0.9.23
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

Noticed this in the last few months.
Occurs on 0.9.23 and still on -25-rc.

'Message expired' is given as the reason on the eepsite unreachable page.
It seems to happen more often when the HTTP tunnel was not already built (close-on-idle, etc). Connection usually works [immediately] on refresh.

Observed on zzz.i2p and trac, but zzz pointed out on IRC that this is a local issue - the remote doesn't matter.

Happens once a day at least.
Haven't heard of non-HTTP occurrences but possible.

Subtickets

Change History (7)

comment:1 Changed 4 years ago by dg

Not just busy routers, noticed it not long after startup but not exclusively at that point.

comment:2 Changed 4 years ago by str4d

Status: newopen

comment:3 Changed 3 years ago by zzz

Component: unspecifiedapps/i2ptunnel
Milestone: undecided0.9.27
Owner: set to zzz
Status: openaccepted

comment:4 Changed 3 years ago by zzz

Milestone: 0.9.270.9.29

Is this still happening?

comment:5 in reply to:  4 Changed 3 years ago by dg

Replying to zzz:

Is this still happening?

Yes. Happened on planet, then incidentally on trac whilst trying to reply here.

comment:6 Changed 3 years ago by zzz

Changed this from a hard fail to a soft fail in streaming, so the error won't get back to i2ptunnel.
In 778c27c695ed1a6017cb0cada36d49e55f1cc726 to be 0.9.28-6

comment:7 Changed 3 years ago by zzz

Resolution: fixed
Status: acceptedclosed
Note: See TracTickets for help on using tickets.