Solved HTTP Error 429 Instagram
-
Thanks @yngve for your understanding
But, when I search how 429 HTTP error happens, I pay attention to "Retry-After" header. But I can't use "View Page Source" because when I clicked it, it takes me back to the error page. If you can't understand me, I will attach the screenshot on example (on other error code) about this. Probably tomorrow morning or afternoon because I must go sleep now. -
Until this error solved, I temporarily limits on accessing Instagram post. For now, 40 seconds every posts.
This is too fast or OK? -
The Retry-After header is probably more useful for automatic software fetching content than for a browser, at the very least unless the site sends its own HTML error page explaining what is going on instead of relying on the browser to produce a default one, as in this case.
If there is such a header in the HTTP response (It would not normally be in the HTML), you can see it in the Developer Tools network analyzer; but you can only see it for requests sent after you open the Dev Tools, not for the current page.
As for why this happens, that is something you will have to ask the web site support about.
I do see a few search results about this error from Instagram (particularly from users using a tool to download content), so you are not the only one. (One conceivable possibility: If there are many users on your local network, exiting through a single firewall IP address, then you might all be considered one user generating a lot of traffic, collectively exceeding the access rate limit.)
-
I'm sorry, recently I reply on this forum because of my busy activities and fear on using Instagram because of HTTP Error 429.
@yngve , I usually download content (photos of course) using tool. I used Developer Tool (especially Inspect) to do that. Not third-party tools. This is OK or not? Or probably it cause Error 429?
For 3 days on, I'm rarely use Instagram because I fear receive Error 429 that will traumatize me using that. -
It could very well be the tool that got your IP address blocklisted.
I have no knowledge about what triggers such a block, but I would think it involves at least how many requests are sent within a given timeframe.
There might be information on their pages about what their expectations of tools are, e.g. request frequency, adherence to the robots.txt file, or some kind of contract that might include a login and API key usage, so that they know the requests are approved.
Normal surfing should not normally trigger a block, but combined with a tool causing a lot of traffic from the same IP address ....
-
For you all, probably you'll asked me "why you use this forum?"
My answer is:
This issue was addressed by me to Instagram's Twitter accounts (Instagramcomms and Instagram), even its founder, Adam Moseri. I was followed them all. This was 2 weeks ago when I aware of HTTP Error 429 issue. But, there was no answer from them, so I using Vivaldi Forum to resolve this together. Even, I followed the Vivaldi's Twitter account and it responded! (Thanks to your team!)@yngve said in HTTP Error 429 Instagram:
It could very well be the tool that got your IP address blocklisted.
The tool that your mean is Vivaldi's Developer Tool (I'm using right-click, then Developer Tool, and then Inspect. Or, I simply press CTRL+Q direct to Inspect window)
-
I assumed, by this
I usually download content (photos of course) using tool.
you meant a separate (non-Vivaldi) tool to download a lot of images; I didn't catch the rest, sorry.
Still, Instagram seems to have some kind of detection method for such downloads (e.g that a resource is requested using a different set of HTTP headers than when loading images for their web view), and adds a temporary block when you cross some limit. I have no idea what that limit is.
-
@yngve said in HTTP Error 429 Instagram:
you meant a separate (non-Vivaldi) tool to download a lot of images
@yngve , not that. I'm using Vivaldi's Developer Tool. Not others.
@yngve said in HTTP Error 429 Instagram:
Still, Instagram seems to have some kind of detection method for such downloads (e.g that a resource is requested using a different set of HTTP headers than when loading images for their web view), and adds a temporary block when you cross some limit. I have no idea what that limit is.
But for this, this forum will open to everyone who see it and can answer/solve my problem, at least have same issue as me. I will wait for next week how this can be solved or -sorry- unsolved.
-
-
Hello, everyone!
It's me again, with Farel
I'm sorry because last week I'm so sick so I not write anything on this thread. I'm now on recovery mode, hoping to get well soon.
Now, I have some question to you (not only from Vivaldi's Team)- There is any website that can see Instagram without account (or for at least -for security reason- using account, but alternative to Instagram)?(This to accomodate me to see Instagram posts when I get HTTP Error 429 that usually last for 24 hours). Usually, I using Picuki (link: picuki.com) before I have my Instagram account.
(Note: Normally I don't access private accounts, so I access open one) - When I get HTTP Error 429 in the future, what I must do? (Usually, I panicked when I get this error code)
- If you access Instagram on Vivaldi, what you do when accessing posts? Using same tab for see posts? Or "Open Link in New Tab" (in new tab)? (Usually I do latter)
I wait for your answer for one week I least, so I can considering when I resuming Instagram surfing using Vivaldi.
Thanks
Regards
Farel
- There is any website that can see Instagram without account (or for at least -for security reason- using account, but alternative to Instagram)?(This to accomodate me to see Instagram posts when I get HTTP Error 429 that usually last for 24 hours). Usually, I using Picuki (link: picuki.com) before I have my Instagram account.
-
-
-
Update:
Start tomorrow (or probably Saturday), I will use Picuki (link: picuki.com) temporarily to surfing on Instagram. I will try using that to try this is better than Instagram or reversely. I will update as soon as possible, at least after I using this.
Thank you for your attention
PS: I will wait for your reply, from Vivaldi team and everyone that read this topic/post. -
Emergency update:
I think picuki.com always return with Error 500. So, I can't use it. How do you think?
Please answer me. The question that last week posted here still unanswered.
For time being, I will temporarily refrain from Instagram, except urgent and needed until a useful solution has reached.
Thank you for your attention. -
@frlvivaldi
PS: I recently used it -
Hello, everyone
There still no answer??!
I will delete this topic in one week if no answer is submitted here
Please, this is important!
In last one week, only I that write on this thread, NO OTHERS!
Thank you for your attention. -
Extra information:
My Vivaldi version is now at Version 5.5.2805.38 -
Everyone that see/view this topic, please answer your question (if you can)... I'm desperate waiting for solution. I'm stressed if I not using Instagram for a long time.
But, I have a extra question:
If this issue is unsolved, how I mark it?
Thank you for your attention -
@frlvivaldi said in HTTP Error 429 Instagram:
If this issue is unsolved, how I mark it?
To mark a thread as Unresolved:
- Edit the first post
- Open the dropdown on the Submit button and click the radio button saying Ask As Question
- Submit the post again
To mark it as Resolved:
- Select the three dot vertical menu of the post that resolves the question
- Select the checkmark saying Mark This Post As The Correct Answer
-
As I think I said earlier, the problem you are experiencing is not caused by Vivaldi; and there is nothing we can do to fix it.
The block you encounter is set up by Instagram, and is very likely triggered by server-side algorithms that are looking for sequences of requests that Instagram's site developers consider undesirable, e.g. a script scraping content, which could have both performance consequences for the site (bandwidth, CPU, disk usage), and be considered potential copyright/license violations of the rights of the content creator whose content is being downloaded. Whether or not that is the intention of the the blocked user won't matter to Instagram.
They have probably set the trigger limit for a fairly low number of such actions before they block, since they want to quickly stop scrapers in their tracks, meaning that downloading the raw content (or whatever they detect) of just a relatively few images (may be 10, 20, I consider 100 unlikely) within a specific period (likely a few hours or a day) is likely to trigger the block.
I have no knowlegde about it, but there may be APIs available for such downloads for approved (read: paying) users.
Again, this is an Instagram policy, and it will trigger for all browsers if the algorithms they use observe requests they are coded to detect, and have nothing to do with Vivaldi.
-
@pesala and @yngve
Thanks for your answer, and is solved! But, if you have a idea, is there any forum or something else that I can ask about it?
This so will solve this problem efficiently.And thank you for all your efforts to help me through this topic. I'll learn from it, so I can use Instagram carefully. And now, I understand how HTTP Error 429 can happen and how to avoid it.
(Edit: Sorry for not checking the first post, I thought was unresolved. But, instead SOLVED! Thanks to Vivaldi Team! I now learn something important to my life!) -
This post is deleted! -
This post is deleted! -