-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
User has exceeded the 'max_user_connections' resource (current value: 15) #69
Comments
Any update on this issue? Starting in September, we are getting the errors using AppSync. It has been working for many months and suddenly broken without any code change. Here is the console.log from AppSync |
trying to login at https://appsync.nativescript.org/login using a web browser results in same error Request URL: https://appsync-server.nativescript.org/auth/login |
I'm having the same issue. Any solutions? |
Looks like NativeScript has moved out of supporting these plugins. What a shame! I wish the team has paid more attention to their own plugins OR at least communicate their support or end of life plans. |
Those who come here for a resolution, Nathanael just replied to my bug report in the main issue tracker under NativeScript, they will be looking at this issue soon. |
@lonemanotzi Great! Hope they will resolve it. Did to you try to get the self hosted option up and running are are you waiting to see if it's fixed? If so, did it go well? |
@argia-andreas |
I get a error when i try do do anything on the cli.
nativescript-app-sync whoami
Produces the following error:
[Error] User 'USER-ID-HERE' has exceeded the 'max_questions' resource (current value: 18000)
I removed the user id from the error message just in case it's sensitive.
It seems intermittent. Starts working after a few minutes, then stops again randomly.
I'm only using appsync with three devices so it seems strange if this would be on my end.
Is this likely to be a issue with appsync and it's server resources or an issue with my usage of appsync?
It seems heroku related after googling.
The text was updated successfully, but these errors were encountered: