I have been pinged by @SLong-WMF about @TBurmeister having issue opening Phabricator tasks while working at a specific coworking space:
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T84 Make sure anti-vandalism features are up to snuff | |||
| Restricted Task | |||||
| Resolved | ABran-WMF | T398156 429 on Phabricator while working at a coworking space | |||
| Resolved | Jelto | T398316 Update Phabricator 429 message |
Event Timeline
@TBurmeister could you please tell us which IP address is used by your coworking space?
Here is a text file with the request and response headers (copied from my slack convo with Arnaud last Friday b/c I'm not at the coworking space now...). I'm not sure if the relevant IP address is in there somewhere? name": "x-client-ip", "value": "3.139.223.34" ?
thanks @TBurmeister for the log extraction, you can confirm that on location with websites like https://whatismyipaddress.com/ to have a visual confirmation.
The x-client-ip you extracted belongs to AWS. If you discover that your coworking space is using this IP address as an exit point, I recommend temporarily switching to another connection (such as a mobile hotspot from your smartphone) while we sort this out.
@TBurmeister you can grab your IP address here: https://whatismyipaddress.com/
This should be re-opened as the issue is ongoing.
The task is still open but no update was provided. @TBurmeister do you still have the issue with 429s?
Also additional safeguards were implemented which should prevent 429s in T401003 .
I will no longer be working from that co-working space, so this is now a non-issue. Marking as resolved. Thanks!
