- ABP Framework version: v8.3.1
- UI Type: MVC
- Database System: EF Core (PostgreSQL)
- Tiered (for MVC) or Auth Server Separated (for Angular): no
- Exception message and full stack trace:
- abp login [user.name] [19:22:37 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli [19:22:37 WRN] 1. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[user.name] with an error: 403-Forbidden. Waiting 2 secs for the next try... [19:22:39 WRN] 2. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[user.name] with an error: 403-Forbidden. Waiting 4 secs for the next try... [19:22:43 WRN] 3. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[user.name] with an error: 403-Forbidden. Waiting 7 secs for the next try... System.Exception: ERROR: Remote server returns 'Forbidden' at async Task Volo.Abp.Cli.Auth.AuthService.CheckMultipleOrganizationsAsync(string username) at async Task Volo.Abp.Cli.Commands.LoginCommand.Hqh5Vq0Ghf(CommandLineArgs , string ) at async Task Volo.Abp.Cli.Commands.LoginCommand.ExecuteAsync(CommandLineArgs commandLineArgs) at async Task Volo.Abp.Studio.Cli.StudioCliService.RunInternalAsync(CommandLineArgs commandLineArgs) at async Task Volo.Abp.Studio.Cli.StudioCliService.RunAsync(string[] args) Unhandled exception. System.Exception: ERROR: Remote server returns 'Forbidden' at Volo.Abp.Cli.Auth.AuthService.CheckMultipleOrganizationsAsync(String username) at Volo.Abp.Cli.Commands.LoginCommand.Hqh5Vq0Ghf(CommandLineArgs , String ) at Volo.Abp.Cli.Commands.LoginCommand.ExecuteAsync(CommandLineArgs commandLineArgs) at Volo.Abp.Studio.Cli.StudioCliService.RunInternalAsync(CommandLineArgs commandLineArgs) at Volo.Abp.Studio.Cli.StudioCliService.RunAsync(String[] args) at Volo.Abp.Studio.Cli.Program.LaxYuWdfb(Object ) at Volo.Abp.Studio.Cli.Program.(String[] args)
Other login command: abp login [user.name] --organization [OrganizationName] [19:24:42 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli Password: [19:24:47 ERR] Could not retrieve the OpenId Connect discovery document! ErrorType: Http. Error: Error connecting to https://account.abp.io/.well-known/openid-configuration: Forbidden
Alternative to Organization name, i have tried with organizationId the result is same, like below:
abp login [user.name] --organization [11111-11111-1111-45a2-39fc9f8a1bd0] -> [OrganizationId from https://abp.io/my-organizations/....................] [19:25:58 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli Password: [19:26:04 ERR] Could not retrieve the OpenId Connect discovery document! ErrorType: Http. Error: Error connecting to https://account.abp.io/.well-known/openid-configuration: Forbidden
I have uninstalled all abp related tools and re-install the Volo.Abp.Studio.Cli latest version and tried again, result is same.
I have tried deleting .-license.bin files, result is same too.
I have not had any problems until today, but today I cannot use my abp commercial account.
- Steps to reproduce the issue: When i am trying to login to abp commercial account, i am getting error.
12 Answer(s)
-
0
I got the same issue
-
0
To add to the conversation, this is what I'm getting just logging in with the abp cli abp login myusername -p mypassword
- HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=rogercprops with an error: 403-Forbidden. Waiting 2 secs for the next try...
- HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=rogercprops with an error: 403-Forbidden. Waiting 4 secs for the next try...
- HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=rogercprops with an error: 403-Forbidden. Waiting 7 secs for the next try... ERROR: Remote server returns 'Forbidden' System.Exception: ERROR: Remote server returns 'Forbidden' at Volo.Abp.Cli.Auth.AuthService.CheckMultipleOrganizationsAsync(String username) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Auth\AuthService.cs:line 140 at Volo.Abp.Cli.Commands.LoginCommand.HasMultipleOrganizationAndThisNotSpecified(CommandLineArgs commandLineArgs, String organization) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\LoginCommand.cs:line 107 at Volo.Abp.Cli.Commands.LoginCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\LoginCommand.cs:line 52 at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 169 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 77
-
0
I am having the same issue.
Reinstalled the CLI, nuked by browser history thinking it had old data.... flushed my local DNS and tried all sorts of things, but I simply can't login via the CLI or suite.
-
2
Same issue, I think the problem is due to the recent migration of ABP portal to Cloudflare.
-
0
I am having the same issue.
-
0
In addition to the other issues I was having above....
After doing a Build/Clean, its also having a bad time with 'Unable to load the service index for source XXXX' Response status code does not indicate Success: 403 (Forbidden) Which sucks, it can't compile if it can't get the packages.
-
0
Notice the CloudFlare humanity test stuff today? Looks like they just dropped it all over everything.
-
1
The same issue is happening over here. I can't download packages anymore.
-
0
i have same issue from today
-
0
same issue...
-
0
-
0
It was an issue about an attack yesterday on abp.io. Our DevOps team increased the security level, and this problem has been fixed. We are aware that it's been a serious problem and affected you. We will take extra action so as not to face this problem again. I appreciate your understanding 🙏