Alrighty, I found out what was causing this. Since I had only been developing locally, I had not had this problem before (nor when I deployed to Azure), but apparently running in a local context such as mine, requires "Private Networks (server & client)" capability to work. Of course it would be nicer to get an error corresponding the problem, but at least it's settled now.
Any idea why this capability is separated from the "internet" capability ?