Activities of "pstgi"

Thanks, that actually was the cause for the log (don't know how that happened) and the DB connection string was only working when manually starting the Migrator.

The connection string is the same in the Migrator appsettings and in the application's appsettings.

And as I wrote, logs.txt has no error or any other new entry.

The DB is set up correctly (ran Migrator) and Swagger is displaying correctly. However when I try Authorize, it returns a 500 Internal Server Error with this content:

{"result":null,"targetUrl":null,"success":false,"error":{"code":0,"message":"InternalServerError","details":null,"validationErrors":null},"unAuthorizedRequest":false,"__abp":true}

Likewise, when running the application, files are loading up to the call to GetAll http://mydomain.com/AbpUserConfiguration/GetAll?d=1551706554324 same JSON response as above.

What is strange is that logs.txt doesn't have any new entry (only older) related to this error, and server's event log doesn't have any error either.

Where can I look further to debug this?

Sorry I didn't get your answers, maybe as I changed the account email.

I did reproduce it actually, it's currently in my browser and no error is shown in the console. The freeze-ui layer is covering the change password screen.

Is anything I can do to help debug this?

No errors. I'm not sure I can reproduct that, maybe start with a new database?

I created a new application based on .Net Core and Angular, v6.7.0 in separate solutions. I started the API in Visual Studio 17 and the client in VS Code.

The login screen appears correctls, I created a "default" tenant as in your instructions then logged in as "admin". At that moment I got the spinning icon indefinitely. The Chrome debug tools were open and I didn't see any pending API call.

After refreshing the page, I got the change password screen, which is I suppose the one I should have seen after logging in.

So basically it is working but an average user would be stuck. Is this something linked to my setup or is this a known issue?