Searching the web, this seems to be a common problem when using ngrok 
with ASP.NET Core. Thankfully, among the many suggestions listed in that 
StackOverflow issue, there is a correct solution.
Stop ngrok and run it again with the following parameters:

ngrok http https://localhost:5001 -host-header="localhost:5001"