Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation issue #5

Open
skinkie opened this issue Dec 1, 2018 · 3 comments
Open

Installation issue #5

skinkie opened this issue Dec 1, 2018 · 3 comments

Comments

@skinkie
Copy link
Contributor

skinkie commented Dec 1, 2018

I have placed the module in my module path.

ejabberdctl modules_update_specs
ejabberdctl modules_available
ejabberd_auth_jwt Authentication via JWT token
ejabberdctl module_install ejabberd_auth_jwt
[jabber@transdev01 sources]$ ejabberdctl module_install ejabberd_auth_jwt
Error: {429,
With a github error, on "You have triggered an abuse detection mechanism.".

@yokomizor
Copy link
Owner

Based on the error message, it looks like the problem is not with the module itself, but fetching resources from Github instead.

I believe ejabberd fetches github resources via HTTPS (public access / low limit), so when you run modules_update_spects you might be spending a significant part of your github network limit.

Running module_install will trigger the module build using rebar3. This process should not trigger any requests to github afaik, but it could be the case rebar3 is downloading test dependencies from github (dependencies of dependencies).

Unfortunately this is a tough one to debug since I would have to mock/proxy responses from github :/

Github limits are time based, so as a workaround, you can just wait a few minutes and try again.

Please also consider other requests to github from the same network. Since rebar3 and ejabberd use github without authentication, request limits will be shared among other process in the same network/proxy.

@skinkie
Copy link
Contributor Author

skinkie commented Dec 2, 2018

I tried multiple times, same result, from a dedicated server. Then I used the 'old' compiling strategy via modification of the stock ejabberd sources. So you might want to keep this ticket open.

@avelino
Copy link

avelino commented Jan 28, 2024

@yokomizor is spam!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants