Just in case somebody else finds this question, the problem turned out to be with ngrok, as ngrok did not start correctly when invoked from the npm process.
There are two possible workarounds. First one would be to start ngrok from the command line after the local server was started by npm. The other workaround would be to use directly the localhost URL served by the local process, as explained in this question about the same problem.