Cannot install plugins from the Marketplace being rate limited by GitHub

[jordangarrison]

Search first

• I searched and no similar issues were found

What Happened?

I click install on a plugin and receive the following error message:

[Error]<logseq-focus-mode> :release-channel-issue "Github API Failed(403) {\"message\":\"API rate limit exceeded for user ID 1779837.\",\"documentation_url\":\"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting\"}"]

Does not matter which plugin I attempt to install.

Reproduce the Bug

Not sure how to reproduce but I would expect if you install enough plugins it will cause this to occur.

1. Go to the plugins marketplace
2. Click install on a plugin
3. See error

Expected Behavior

I expected to be able to install the plugin without API rate limits.

Screenshots

Desktop or Mobile Platform Information

MacOS 13.4, Desktop, Logseq 0.9.19, Arm

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[Aitozi]

+1 Only installed 5 plugins, then it shows rate limit error. Looking forward to solve this.

[cnrpman]

Related: #9127

[alexppg]

That issue is closed because of this PR #9609. I've take a look at what it does (not that I'm an expert) and it doesn't seem to fix the problem, more like bypass it by being able to enable or disable the auto-updates.

My guess is that until there's the possibility to add our own GitHub users, this will continue to happen randomly, since it has different constraints.

In my experience, there's not really a reliable way to use GH's api without authenticating with a user.

A workaround is usually to force change your public IP, or use Tor and force the change of circuit. But that's not possible for everybody in every situation.

[JohnnyJayJay]

I can't install any plugin anymore because of this issue. It happens regardless of how long I wait, what plugin I try to install and even if I use different networks.
Not sure what GitHub is doing exactly, but this issue makes it impossible for me to install plugins. We definitely need a GitHub OAuth option.

[archae0pteryx]

I have run across this several times now. definitely +1 for the oatuh support. I wanted to chime in and say, I am also not readily finding info about manually installing a plugin. It would be great to have this in the docs. Even heading to the developer docs doesn't provide much info about this. I know for myself I just wanted a dark theme for a fresh install on linux. Short of more documentation or a button to "manually add plugin", maybe a default dark theme?

[Sqwrly]

I'm having this issue also. Brand new logseq user, never downloaded any plugins or themes. First theme I tried to install I got this rate limit error. I'm on my home connection.

[alexppg]

I have run across this several times now. definitely +1 for the oatuh support. I wanted to chime in and say, I am also not readily finding info about manually installing a plugin. It would be great to have this in the docs. Even heading to the developer docs doesn't provide much info about this. I know for myself I just wanted a dark theme for a fresh install on linux. Short of more documentation or a button to "manually add plugin", maybe a default dark theme?

In the plugins repositories they usually talk about how to do it, with more or less details, but still. For example here. https://github.com/QWxleA/log-stats#install-plugin-manually

Still, I think that button would be useful.

[eniseratabay]

I have been using logseq for 2-3 days and installed 6 plugins in total and I started getting the same error.

[github-actions]

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!