Failed to login locally in setup of squidex/ by IIS in windows 10

I have…

  • [X] Checked the logs and have provided the logs if I found something suspicious there

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ ] Bug report
  • [ ] Performance issue
  • [X ] Documentation issue or request

Current behavior

Expected behavior

Minimal reproduction of the problem


  • [ ] Self hosted with docker
  • [X] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: [VERSION]


  • [83.0.4103.97] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge


Btw, I check the logs under the hosting “squidex” folder path:


“logLevel”: “Information”,

“message”: “Showing login: User is not authenticated”,

“app”: {

"name": "Squidex",

"version": "",

"sessionId": "0b012280-8967-473d-abde-48fe8bd82950"


“web”: {

"requestId": "|b9a6e2c3-473e4ac874a3404f.",

"requestPath": "/connect/authorize",

"requestMethod": "GET"


“timestamp”: “2020-06-13T09:56:45Z”,

“category”: “IdentityServer4.ResponseHandling.AuthorizeInteractionResponseGenerator”


Have you seen this:

Yes, strictly follow. Thanks for your prompt reply, Sebestian.

and setup of the env var “ASPNETCORE_ENVIRONMENT” as “Production” is done too.

Just wonder if the username & password isnt needed be registered for real I understand??

You should see it in the logs, when your user has been created.

ok, so is that implied my adopted password is still not complicated enough to pass?
Therefore, I get the “message”: “Showing login: User is not authenticated” in my log.

it works finally when using a more complex password now. Thanks for your tips, Sebastian!

1 Like