aaronpk / OwnYourGram

📷 Save your Instagram photos to your own website!
94 stars 14 forks source link

Not working with Known 0.9.9-a #79

Closed davidmead closed 3 years ago

davidmead commented 5 years ago

Using the latest Known build 0.9.9-a I can log in to OwnYourGram, authorize, and see photos in it, but nothing is being sent to my blog.

I logged out, as well as revoking the existing token within Known, logged back in but still nothing.

On the 'Indieweb' tab, within Known, I can see it's connected

screen shot 2019-01-05 at 10 05 05 am

and it seems to be all okay on the OwnYourGram dashboard, even being able to detect the Twitter syndication available.

But nothing comes through and when I hit the 'post' button I get an error.

screen shot 2019-01-05 at 9 58 56 am
funwhilelost commented 5 years ago

One small gotcha: did you log in to OwnYourGram with the full https:// and your URL? I had issues in the past by putting in "funwhilelost.com" and signing into http okay, then failing to post because of a weird https issue.

davidmead commented 5 years ago

Good thing to check @funwhilelost, but yeah I was logged in using the full URL.

aaronpk commented 5 years ago

The error that OwnYourGram is getting from Known (and isn't showing you, my bad) is this:

{
  "error": "invalid_request",
  "error_description": "Failed uploading photo from https://davidjohnmead.com/file/3b44c043122f278ba9eac3ae7bdb7cc9",
  "messages": []
}
aaronpk commented 5 years ago

@davidmead can you try again? I just pushed a change that might fix this. (It still points to a problem with Known, but this should at least work around it).

davidmead commented 5 years ago

No. Sorry.

I logged in and tried, but the same error message in OYG.

I also revoked access to OYG in Known, logged out of OYG and logged in & authorized again, but still nothing.

davidmead commented 5 years ago

As I mentioned in Slack, I did get 2 photos to go through when I disabled the InstagramShim 0.1 plugin, but then the third and fourth failed.

Must've been when you changed something else.

absolonkent commented 5 years ago

I'm not sure if this is still an open issue, but disabling the Known OAuth2 Server 0.9.9-a plugin seemed to resolve the issue for me.