I worked out what this was for my environment.
Im running my app on a kubernetes setup using nginx ingress controller. This controller terminates ssl. This would normally be fine, but in front of that I have a load balancer which is set up as a proxy to the ingress controller. The issue is that my hosts load balancer doesnt pass through x-forward headers when in proxy pass though configuration. This is a bit poor.
So my solution to this has been to force the app to https with a little middleware that sets the request scheme.
The app now works on latest chrome.
Hi @tinytownsoftware
Did you work out why chrome was / is doing this?
Im having a similar issue.
Works on Edge, and version of Chrome below v84.
But it will not no matter what I do in terms of cleaning cookies or anything else. It will not log into the latest version of chrome: Version 84.0.4147.89 (Official Build) (64-bit) On Windows 10.
I found the issue in the end.
I am setting the env before starting the app, the issue I had was the migrator app never picked up the connection string from my appsettings.{environment}.json file.
I had to make a small modification to the {Application}MigratorModule.
In the constructor I added:
string environment = Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT");
and amended the call to AppConfigurations.Get to include the environment as per above as the second parameter.
Once this was done the migrator app would use the appsettings files I was expecting / wanting it to use.
Yes it is.
@maliming / @fvdh - I have run into the same issue, can you share here what the underlying issue was or indicate where it was so others (like me) who run into the same issue can fix it and move on?
Thanks.
