That must have been the issue as it’s working now that I’ve re-checked this.
The root cause of this problem (502 from nginx) has been identified and a fix is underway: