~stemy


#64 Not a single instance works 4 months ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

Hello,

Is there a change to instagram that prevents bibliogram to work ? Because since some days, i'm totally unable to see anything with the instance mentioned in the doc. On all instances tested, i have: -1 quota reached -4 blocked -4 HTTP 504 errors -1 secured connection failed -2 HTTP 502 error

One or two instances are blocked during a short time, but all instance blocked for so long, the problem comes certainly from the instances themselves, but when not a single instance is working for a so long time, it make me suspicious of a problem coming directly from instagram itself.

#52 Pictures not visible 7 months ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

Hello,

Sometimes, a random number of pictures are replaced by gray squares on my instance.

#50 [Enhancement] One-click instance switching 9 months ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

A link to another random instance would be useful in case of blocking.

#49 Userscript unblocking does nothing 9 months ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

I installed the userscript mentioned on the HTTP 503 error page, but i didn't saw any change.

#28 Profiles are only partial 1 year, 10 months ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

Hello,

I can't see all the contents of instagram users. I see only a small amount of posts, with this error message at the bottom:

◸―――――――――――――――――――――――――――――――――――――◹ ···< | 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 /var/www/bibliogram/src/lib/collectors.js:284:18 at runMicrotasks () at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Timeline.fetchUpToPage (/var/www/bibliogram/src/lib/structures/Timeline.js:58:19) at async Object.code (/var/www/bibliogram/src/site/api/routes.js:202:24)

#23 graphql fetch error: unexpected end of JSON input 2 years ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

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)

#21 EAI_AGAIN persists for more than 60 minutes 2 years ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

Hello,

I already had this error previously, and you answered to wait for 60 seconds then it will fix itself. After having some connectivity problems, the error appeared again, but it was 2 hours ago and it still there. Is there a way to fix it manually ?

Thanks

Just in case, the exact message here below:

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

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

FetchError: request to https://www.instagram.com/graphql/query/? query_hash=e769aa130647d2354c40ea6a439bfc08&variables=%7B%22id%22%3A%22201872236%22%2C%22first%22%3A12%2C%22after%22%3A%22%22%7D failed, reason: getaddrinfo EAI_AGAIN www.instagram.com at ClientRequest. (/var/www/bibliogram/node_modules/node-fetch/ lib/index.js:1455:11) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:428:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21)

#15 EAI_AGAIN error 2 years ago

Comment by ~stemy on ~cadence/bibliogram-issues

It happened again. I waited 2 hours without any self fixing. Is there a way to do it manually (for example with CLI) ?

RESOLVED WONT_FIX REPORTED

#15 EAI_AGAIN error 2 years ago

Ticket created by ~stemy on ~cadence/bibliogram-issues

Hello,

I tried to load a specific account (la_carologie) and it gave me 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: request to https://www.instagram.com/graphql/query/?
query_hash=e769aa130647d2354c40ea6a439bfc08&variables=%7B%22id%22%3A%222212071769%22%2C%22first%22%3A12%2C%22after%22%3A%22%22%7D 
failed, reason: getaddrinfo EAI_AGAIN www.instagram.com
    at ClientRequest.<anonymous> (/var/www/bibliogram/node_modules/node-fetch/
lib/index.js:1455:11)
    at ClientRequest.emit (events.js:315:20)
    at TLSSocket.socketErrorListener (_http_client.js:426:9)
    at TLSSocket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)

Strangely, the other accounts i tried are working fine, so i don't get why this particular account is returning an HTTP 500 error.

#12 How to write privacy policy ? 2 years ago

Comment by ~stemy on ~cadence/bibliogram-issues

I'm on Yunohost, i installed it with the internal packaging system (https://github.com/YunoHost-Apps/bibliogram_ynh).