this seems to have returned since version 27.1.2 for me. Had it resolved for 27.0.2 earlier.
edit: when upgrading to 27.1.2 I had to revert the fix described above: “Not properly set up to resolve “/ocm-provider/” and “/ocs-provider/” on NGINX server - #8 by trendzetter