User Details
- User Since
- Nov 14 2014, 4:15 PM (435 w, 5 d)
- Availability
- Available
- IRC Nick
- Cyberpower678 or CP678 or Skynet
- LDAP User
- Cyberpower678
- MediaWiki User
- Cyberpower678 [ Global Accounts ]
Mon, Feb 27
Wed, Feb 22
Feb 17 2023
Feb 2 2023
The 503 errors and DB ERRORs you've been getting were unrelated issues.
I'm not aware of any issues that should prevent the bot from doing what it's supposed to do. At this point, this ticket is merely addressing a major performance penalty the bot is currently incurring as a result of the bug regarding data ingesting.
Feb 1 2023
This should be fixed hopefully today.
Jan 30 2023
Jan 29 2023
Jan 27 2023
Jan 25 2023
Jan 11 2023
IABot has been whitelisted on CloudFlare.
You get that error when you refresh the UI on any action request without resubmitting form data. The tool uses tokens and checksum hashes to ensure requests are not accidentally repeated, and that malicious users can't exploit any CSRF vulnerabilities. In short, they're security features meant to keep you safe. All you need to do is click the submit button again when that happens.
Alright, give it a try now.
What's happening here is because the bot is taking longer to work on the article, it's hitting the server-side execution time limit and timing out. Ordinarily large articles are blocked from even running on the tool, where the user is instead directed to running a bot job instead with the desired article(s). I can try to push the time limit a little higher to get around this, but this will only be temporary. The limit exists to prevent rogue processes from indefinitely hanging up a connection resource, that would end up blocking someone else from using the tool.
Jan 10 2023
If you want to follow the progress on getting the underlying issue fixed, you can subscribe to T326609
There we go. It's EOD, Monday. Just as promised. Sorry for the wait. Tool should be working now.
Jan 9 2023
Jan 6 2023
Hey guys, sorry for the silence. I've been trying to get at the root of the issue which is not an easy thing to do since the culprit is being caused by an over-ingested amount of data in the bot's configuration when it comes to handling CS1 templates. Since this has been dragging on for so long, I am instead now putting in a work-around which will be a fail-safe if this root issue happens again. Expect it to be available by EOD, Monday.
Dec 19 2022
Dec 18 2022
Code is being tested.
Dec 4 2022
It is clear that the operators of archive.ph have no interest, or ability, to address the issue with IABot not being able to communicate with their servers. A workaround, that doesn't require users to clean up after the bot, or appease the bot needs to be implemented in the bot code.
Dec 2 2022
Nov 21 2022
Nov 9 2022
Oct 31 2022
Oct 28 2022
Oct 17 2022
This is an issue with archive.today. Please use the long-form versions of archive.today snapshots.
Oct 14 2022
Oct 12 2022
Reverted to Grid engine as Kubernetes appears to return a 503 after some hours.
Oct 11 2022
Actually this level of protection has been successfully broken. Chromium not needed here.
A profile to localize the months in uz already exists in the code.
Oct 5 2022
Turns out while IABot could have used better HTTP/2 handling, this appears to be very very sophisticated CloudFlare protection, that is able to distinguish cURL requests from actual browser requests even if a perfectly imitated browser-generated cURL request is made.
Oct 3 2022
Sep 30 2022
The bot could have archived it, but was prevented from doing so with the new configuration option.