Rss-bridge: InstagramBridge error 500 "Unable to find username in search result" got unexpected answer from server

Created on 18 Mar 2020 · 14Comments · Source: RSS-Bridge/rss-bridge

I run into the same error message described in #1419 with version: dev.2020-02-26 today and the patch I pulled manually from 7b63da522fa728811349081a0921f84bb1fa6f19 does not fix my case. I also get Error message: Unable to find username in search result.

Suspecting that it's some sort of blocking since the provided examples in this very issue do also not work while my intended request works fine on the installation by @Legalien

I run the example with wget --header='Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8' --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36" "https://www.instagram.com/donniedhillon/" and this is the response I got:

{"errors": {"error": ["Sorry, there was a problem with your request."]}, "status": "ok", "error_type": "generic_request_error"}

Requesting the index page / works fine so they didn't block my IP per se. No idea what's going on. Mayhap it's some sort of greylisting and it starts working tomorrow.

Bug-Report

Source

bekopharm

👍1

All 14 comments

Can confirm donniedhillon username leads to an error on my local machine, with the latest master.

XML Parsing Error: prefix not bound to a namespace
Location: http://localhost:8000/?action=display&bridge=Instagram&context=Username&u=donniedhillon&media_type=all&format=Atom
Line Number 79, Column 3:
        <media:thumbnail url="https://www.instagram.com/p/B6ArQxnD1xm/media?size=l"/>
----------------^

Works OK with Html, I think this is a weird XML bug on some PHP library.

somini on 19 Mar 2020

Actually, it's weird. Last night a few hours before this thread was started I received an email about an error in my feed. But I checked the feed now and it seems to work fine.

Maybe Instagram bugged out last night for a few hours and now it's back to normal.

Everything seems to work fine on my end as far as I can see.

Legalien on 19 Mar 2020

Can confirm the error I reported remains, only for that particular username. All other usernames I'm subscribing to are OK.

somini on 23 Mar 2020

Well, 6 days later and it's still the same. Error persists. The output format doesn't matter in my case.

bekopharm on 24 Mar 2020

Same for the user pyro.keys.

xtaran on 31 Mar 2020

Same for the user pyro.keys.

Can confirm.

Warning: Invalid argument supplied for foreach() in bridges/InstagramBridge.php on line 94

somini on 1 Apr 2020

Can confirm #1531 fixes this, per #1511

somini on 12 Apr 2020

❤1

@somini Sadly it doesn't fix this issue for me. I applied the patch manually but I'm not getting an Atom feed error but IG errors on the lookup already. There is no stream to be created for Atom/HTML/Json/Mrss/Plaintext at all.

bekopharm on 13 Apr 2020

@somini wrote:

Can confirm #1531 fixes this, per #1511

I don't think that's related to #1499, either. You fixed something in the output format, but #1499 is an input issue.

@bekopharm: Thanks for testing!

xtaran on 13 Apr 2020

👍1

I don't think that's related to #1499, either. You fixed something in the output format, but #1499 is an input issue.

On my instance, I was getting a feed with those usernames, but there was a XML error. #1531 fixes it, so I can subscribe to the users mentioned above. Works on my machine...

somini on 18 Apr 2020