issue with postman this week

[Phithue7]

http://tracker2.postman.i2p

I viewed 2-3 pages ok this week,
then I got "I2P Website Unreachable",
then "503 Service unavailable - Ratelimit active. Please wait at least 60 seconds and retry. Do not use scripts or bots on this site!"
I use only my web-browser, no scripts etc. and I wait >60s to retry, but no success.

Anyone else affected ?

[lgillis]

Hi Phithue7!
Web browsers and web proxies have a preset time limit in which the connection must be established, as you may know.
Within I2P, the connection is aborted because the time limit has been exceeded. Now, however, the connection attempt is still within the tunnels you have set up and may be successful without you being informed, precisely because your browser has already terminated the connection. If you now unsuspectingly trigger a new attempt, the block you described may occur (503 => Out of Resources). The tracker is very sensitive. The “60 seconds” waiting time should be treated with caution, in my experience you should first make a cup of coffee and drink it in peace before trying again.
Since I have been using a tiny proxy, I have been blocked much less often.

[anikey]

"I2P Website Unreachable"

That message probably comes from your i2p router.

"503 Service unavailable - Ratelimit active. Please wait at least 60 seconds and retry. Do not use scripts or bots on this site!"

That message comes from the server itself.


I would guess that something like this happens:
- postman's server receives your request, counts it (towards the rate limit), sends a response, but somewhere between your router and postman's router it gets lost, maybe due to some incompatibility. the connection times out and you get the first message.
- you retry that and it fails again, due to that again incompatibility, and postman counts each of your request.
- some time later the incompatibility fixes itself, but you have come over the rate limit, so you get the second message.

An "incompatibility" is something i've observed, but quite rarely. maybe i'm lucky.

that's just a rough guess though.

[Phithue7]

Thanks for the help.

I have since some weeks now a firewall (ufw) and firejail (for i2p/runplain.sh) in place. Maybe here is the root cause...
After a i2p router restart postman was immediately reachable again. I will observe more...

[Phithue7]

some more observation:

the issue starts, when I do one click on postman wishlist "Click here to second that wish".
Where i got the I2P message. Website Unreachable.
2 Minutes waiting:
After that I only get either this message or 503 Service unavailable.

[anikey]

Do you have a postman tracker account? If so, have you tried to file a bug report? (There is a special section for it on patracker).

If you can't even file bugs, then say so - maybe someone else (even me?) can do it for you.

[lgillis]

Have you figured out where the problem is? I would clear the browser cache, alternatively use a different browser, alternatively check with »wget --spider ''Link to URL SecondWish"«.

[Phithue7]

for bothering postman I think it's to early.

browser is Firefox, setting:
"Based on your history settings, Firefox deletes cookies and site data from your session when you close the browser."

Disabling firewall and firejail does not make a difference.
As soon as I hit
http://tracker2.postman.i2p/index.php?a ... ish&id=xyz
I'm blocked by postman's defence until router restart.
Viewing other postman pages or posting here is no problem.

In the past I had this issue not, but I used SecondWish only very rarely.
Can you please for testing also click a SecondWish ? This would be very nice.

[GandalfTheGrey]

As soon as I hit
http://tracker2.postman.i2p/index.php?a ... ish&id=xyz
I'm blocked by postman's defence until router restart.
Viewing other postman pages or posting here is no problem.

In the past I had this issue not, but I used SecondWish only very rarely.
Can you please for testing also click a SecondWish ? This would be very nice.

I hit the 'second wish' with no problem. But when I clicked the link you posted, Postman became inaccessible for an hour or so, until I restarted the router. Could've been coincidence, because it's not unusual for Postman to be inaccessible for a while, but it started & stopped right at those points.

[Phithue7]

Sorry, my link was only an example ending with xyz - a valid number must be put there.
But your test maybe revealed the issue:
seems postman is strictly blocking requests to non-existing pages directly on 1st strike with a long ban.
I used second wish on an already fulfilled one - because it was wrong fulfilled in my opinion. Maybe this is also forbidden by postman.