61–70 of 82 posts
We're experiencing the same issue here. Reports from multiple clients over the last few days. Surely enough checking the logs yields an invalid_credentials error. Trouble is, we can't faithfully reproduce the issue from our network, but clients are reporting failures to authenticate every time they try! Have contacted Instagram for an update. Anyone else still experiencing the issue?
We started having same issue since last Friday (Dec. 15, 2016) after working fine for months. Same user can login via oauth on one wifi, but not on the other, or even on mobile cellular network. And even when it worked on that wifi at one point, it does not work at other times. We have not found a workaround to fix this, reported to Instagram 24 hours ago, waiting...I tried to login to my account on instagram.com fir…
Update: as of now, All of our accounts are magically working. I did asked my facebook friends to pass the issue's urgency to Instagram team.
Here's my fork for the omniauth-instagram Ruby gem, which is now allowing me to consistently log in: https://github.com/stefl/omniauth-instagram/blob/master/lib/...
I've managed to work around this by changing the API host name from 'api.instagram.com' to 'www.instagram.com' for the Oauth authentication flow. Here's my fork for the omniauth-instagram Ruby gem, which is now allowing me to consistently log in: https://github.com/stefl/omniauth-instagram/blob/master/lib/...
I've managed to work around this by changing the API host name from 'api.instagram.com' to 'www.instagram.com' for the Oauth authentication flow. Here's my fork for the omniauth-instagram Ruby gem, which is now allowing me to consistently log in: https://github.com/stefl/omniauth-instagram/blob/master/lib/...
For me it doesn't works. I changed from 'api.instagram.com' to 'www.instagram.com' for the Oauth - have one "302 redirect" back to my site with "error 400". Strange...
Earlier quoted context omitted.
For me it doesn't works. I changed from 'api.instagram.com' to 'www.instagram.com' for the Oauth - have one "302 redirect" back to my site with "error 400". Strange...
Ditto here, it comes and it goes, but I can see this switch doesn't help our overall fail rate.
Earlier quoted context omitted.
Ditto here, it comes and it goes, but I can see this switch doesn't help our overall fail rate.
Okay, thought I'd mention it because it's had such a significant effect for me. So that possibly means that in my case the Auth0 Instagram connection is something to investigate further.
Earlier quoted context omitted.
Ditto here, it comes and it goes, but I can see this switch doesn't help our overall fail rate.
Okay, thought I'd mention it because it's had such a significant effect for me. So that possibly means that in my case the Auth0 Instagram connection is something to investigate further.
I have just tried different environments we have with different users that were consistently failing last week (even this morning) and I have been able to get an access token using the server approach. Can anybody else test with their apps if the problem is fixed for you? Fingers crossed.