When you have a critical situation like yesterday's Cloudflare issue, use blanket communications: put a banner up here and on your site as soon as you've confirmed the issue. Let your customers know what's going on. Then, issue some public statement about the resolution. It's not good enough to read a copied and pasted message with an incomplete explanation in random tickets.
Notice the CloudFlare humanity test stuff today? Looks like they just dropped it all over everything.
Now there's about 15 questions about this, and it's middle of the day Eastern. We'll all survive, and you guys are awesome, but it seems weird not to have a single response with several hours.
You're exactly right. The well-known config is intercepted by cloudflare's humanity check. But even if that turns out not to be so, it's dead.
Yep: Check the docs before asking a question: https://abp.io/docs/latest Yep: Check the samples to see the basic tasks: https://abp.io/docs/latest/samples There are two other questions here about this, so it's a real thing. There are no answers yet, so I'm adding mine: This is a showstopper. The exact solution to your question may have been answered before, and please first use the search on the homepage.
Provide us with the following info:
ABP Framework version: v8.3.2; ABP CLI 0.9.11 (Beta)
UI Type: Blazor Server
Database System: EF Core (PostgreSQL)
Tiered (for MVC) or Auth Server Separated (for Angular): no
Exception message and full stack trace:
abp login [username].com -p [password]
[11:44:27 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
[11:44:27 WRN] 1. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[username] with an error: 403-Forbidden. Waiting 2 secs for the next try...
[11:44:29 WRN] 2. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[username] with an error: 403-Forbidden. Waiting 4 secs for the next try...
[11:44:33 WRN] 3. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[username] with an error: 403-Forbidden. Waiting 7 secs for the next try...
System.Exception: ERROR: Remote server returns 'Forbidden'
at async Task<bool> Volo.Abp.Cli.Auth.AuthService.CheckMultipleOrganizationsAsync(string username)
at async Task<bool> Volo.Abp.Cli.Commands.LoginCommand.spXTXAtpWd(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.spXTXAtpWd(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.IrXAxCPfc(Object )
at Volo.Abp.Studio.Cli.Program.<Main>(String[] args)
zsh: abort abp login [username]] -p [password]
Steps to reproduce the issue:
abp login [username] -p [password]
or dotnet restore
or Start Studio, in which case, the error returned is
Could not retrieve the OpenId Connect discovery document! ErrorType: Http. Error: Error connecting to https://account.abp.io/.well-known/openid-configuration: Forbidden
Chiming in because this is a showstopper if you want to use the Suite workflow that adds a module directly to your project. Stopped working immediately upon upgrade of project, cli, and suite to 8.0.0 from 7.4.x.
Details:
In Suite: Create Blazor Server | EF SQL Server | LeptonX (SQL Server is local Docker image; Redis is local service.)
Build and run; login. Joy, it works.
Create entities in new project in Suite; make sure db is updated. Joy, it works.
In Suite: In the new project, click on Modules | Create New Module
Verify 9 expected applications; build. Joy it works: module created.
In Suite, Add Existing Project; load the newly created module project.
In Suite, in module project, Create Entity of any kind; include Create Backend. No joy, it doesn't work:
System.ArgumentNullException: Value cannot be null. (Parameter 'path1') at System.ArgumentNullException.Throw(String paramName) at System.IO.Path.Combine(String path1, String path2, String path3) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Helpers.IoHelper.CombineNamespacePaths(String rootDirectory, String entityNamespace, String fileName) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.RepositoryCommand.Vk4oNionvi(String , String , Boolean ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.RepositoryCommand.DtJofJ6F8m(String , Boolean , Nullable1 )
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.RepositoryCommand.jdSoICrLHE()
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.RepositoryCommand.ExecuteAsync(CrudPageCommandOptions options)
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options)
at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution, EntityModel masterEntity)
at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity)
at lambda_method2058(Closure, Object)
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
It does, however, create
Uncheck Create Backend: Completes but, obviously, without back end.
Verified that project entries in Suite appsettings.json are complete and correct.
