🐛 Bug Report: Failed to parse page JSON data: expected value at line 1 column 1 [RATE LIMITS]

[arch-btw]

Describe the bug

This error is currently being displayed on all instances.

Steps to reproduce the bug

Go to any instance and it will say:

Failed to parse page JSON data: expected value at line 1 column 1 | /r/popular/hot.json?&raw_json=1&geo_filter=GLOBAL

What's the expected behavior?

To display any Reddit page.

Additional context / screenshot

This started happening about 10 minutes ago. The json file itself is still accessible by browser, so maybe the structure changed?

[mirzaakdeniz]

Ahoy mate, I think you updated for Docker, but not the main repo. I installed and running locally, by using:

git clone https://github.com/redlib-org/redlib && cd redlib cargo run

code. Issue is continuing for me.

[sigaloid]

Docker images are generated from the main repo. If you're seeing the rate limit issue still, it's more likely that it's an IP ban like in https://github.com/redlib-org/redlib/issues/217#issuecomment-2358837922. in which case there's not much that can be done

[r7l]

Thanks allot for fixing the issue. Would it be possible to create a new release for those using releases to install Redlib?

[sigaloid]

Yep, once I finish other things on my to do list like the failing tests

[L-Be]

@BugZappa Are you using a VPN by any chance? I had routed my local instance through a VPN using a Gluetun container and I was still getting the error. Once I switched to using the local network there have been no issues. I swapped it back to the VPN to test and got the error again shortly after. I think I was still being rate limited when using the VPN.

[sigaloid]

@BugZappa you're running v0.31.0. Very old.

[BugZappa]

@BugZappa you're running v0.31.0. Very old.

Yeah for some reason Portainers "always pull image" feature sucks ass, so I did it through the CLI and got it now.

Thank you!

[maaaaz]

Hello @sigaloid, thanks for your great work !

Any ETA for the release ?

Maybe release it as "release candidate/alpha/beta" one if you know there are some bugs ?

[maaaaz]

I see that some binaries of the v0.35.1 release (dating back 29th June) were updated 4 days ago: https://github.com/redlib-org/redlib/releases/tag/v0.35.1

Are these binaries fixing this issue?

If so, why is the "redlib" binary of this release still dating back to 29th June ?

[dave0003]

I tried the redlib-x86_64-unknown-linux-musl version (that was updated 4 days ago) and it seems to be working, unlike the old v0.35.1 "redlib" version.

The Git commit in the "instance information" is also the latest commit: 1838fdaea44b6aa25a8cc738341896209972a359

[stag-enterprises]

I'm getting this issue again, using the second-latest commit.

[ButteredCats]

Yep. Both my containers are running into it as well.

[bclouthier]

I'm been getting this issue as well. Sometimes restarting my container gives me one page load.

[sigaloid]

@drewbdoo #301 is the current rate limiting issue, but i can't reproduce it on the latest commit. are you sure you've updated to the latest commit?

[davralin]

fwiw, everything works for me - on the latest commit. Had some hicups yesterday, but all good today.

[drewbdoo]

Thanks all - I was on the latest but from docker hub, not quay. Working now