We managed to resolve this offline, and the trouble turned out to be an nginx proxy_pass directive that was pointed at the wrong place. I wanted to mention that to close the loop, and potentially to offer something to look at for people with a similar configuration and similar error in the future.
4 Likes