~cadence/bibliogram-issues#23: 
graphql fetch error: unexpected end of JSON input

Hello,

I can't access to any account, all of them return the following error.

       ◸―――――――――――――――――――――――――――――――――――――◹
 ···<  |        500. That's an error.        |  >···
       ◺―――――――――――――――――――――――――――――――――――――◿


╱ Are you visiting this website? Not sure what's going on? ╲ ╲ You might want to come back later. ╱

FetchError: invalid json response body at https://www.instagram.com/graphql/ query/? query_hash=e769aa130647d2354c40ea6a439bfc08&variables=%7B%22id%22%3A%226273389985%22%2C%22first%22%3A12%2C%22after%22%3A%22%22%7D reason: Unexpected end of JSON input at /var/www/bibliogram/node_modules/node-fetch/lib/index.js:272:32 at runMicrotasks () at processTicksAndRejections (internal/process/task_queues.js:97:5) at async /var/www/bibliogram/src/lib/collectors.js:258:38 at async Object.code (/var/www/bibliogram/src/site/api/routes.js:104:31)

Status
REPORTED
Submitter
~stemy
Assigned to
No-one
Submitted
7 days ago
Updated
5 days ago
Labels
No labels applied.

~cadence 7 days ago

Instagram changed stuff.

Try updating and running npm install.

~potassium 6 days ago

Have the same issues. Runned the script via run.fish (which should do upgrading I guess?) but still the same error.

How can I check the version of the installed bibliogram script?

~cadence 6 days ago

Please stop bibliogram and try this:

  • cd /path/to/bibliogram-updater
  • cd bibliogram
  • git pull
  • npm install
  • npm run start

See if anything improves.

~potassium 6 days ago

It does indeed. Many thanks! However, if I have a look at the profile of a user there is still in the bottom part a error 500 message.

You have the same at https://bibliogram.art/u/instagram

◸―――――――――――――――――――――――――――――――――――――◹ ···< | 500. That's an error. | >··· ◺―――――――――――――――――――――――――――――――――――――◿ ╱ Are you visiting this website? Not sure what's going on? ╲ ╲ You might want to come back later. ╱ TypeError: Cannot read property 'json' of undefined at /home/cloud/bupdate/bibliogram/src/lib/collectors.js:284:18 at runMicrotasks () at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Timeline.fetchUpToPage (/home/cloud/bupdate/bibliogram/src/lib/structures/Timeline.js:58:19) at async Object.code (/home/cloud/bupdate/bibliogram/src/site/api/routes.js:202:24)

~cadence 6 days ago

No solution for loading more pages yet.

~potassium 5 days ago

Oh I see. Am I right that IG is currently changing something so that it is as hard as possible to fetch data from their site without an account?

~cadence 5 days ago

Yes. Seems like they're completely blocking cloud server addresses, though I'm not 100% sure what's going on at this time.

~potassium 5 days ago

So it should only be related to your instance of bibliogram, right?

~cadence 5 days ago

It is related to all instances that Instagram thinks are hosted somewhere in the cloud.

~potassium 5 days ago

Unrelated: Have you thought about a GET token that could be supplied with a newsfeed so that one could access the page without the basic auth but not for the broad public?

~cadence 5 days ago

Please open a new todo, or start a discussion on the mailing list, for unrelated subjects.

Register here or Log in to comment, or comment via email.