Hi @ismcagdas,
I have sent you an email with the requested details.
Thanks
Hi @ismcagdas,
I have double-checked the logs in Azure Appservice. Its not throwing any errors.
Hi @ismcagdas
Thanks for the response.
Sorry for my typo, where I missed the *
I have cross checked again and the CorsOrigns stands as you have stated. But still I'm getting the same error.
I got a work-around as follows When I tried to load the host admin portal as http://host.app.xyz.com, it works.
However, I'm, curious to know, how to get the host admin portal working with -> http://app.xyz.com
Hi @ismcagdas
After upgrading to dotnet core 3.1, the error disappeared for me.
Thanks Mahinthan
Hi @maliming, I'm experiencing somewhat similar issue. Here is the diagnosis
For me, on Windows/chrome itself the page is not loading. This is inconsistent too. If I stop the app and start again, it does load, but after about few minutes, the popular loading signal appears forever. When I inspect the network requests from browser, I see the following Two requests are sent. First one responded with 204 and second one always staying at pending state.
Please note, it is a new appeared from yesterday. It was working fine for past few months. If I recall, what I had done yesterday, that would be, I was installing the packages again with npm i and yarn commands
Adding the web.config file to wwwroot resolves the issue.
Suggestion : If the webconfig can be automatically added into the bundle, eliminates the extra manual step
Thank you. Using the lates node version along with above command resolves the problem
Regards Mahi
Thanks @ismcagdas for the idea,
Alternatively, is it possible to dedicate one tenant (tenant X) to store all users and if they try to login to tenant 1, the authentication to be executed against tenant X. It means, whenever a user registers to tenant 1, the user is created in tenant X.
Looking forward your advise
