Nothing changed with the apache/nginx stuff - over the last couple of days some things have been running on a new server, but that shouldn’t affect anything relating to access as it is just a different internal forwarding on our infrastructure. I can’t really say anything else though without knowing at least what profile and what endpoint is causing issues
I just modified something on the new server relating to Tomcat that might fix the problem if that was actually the issue in the first place (there was a Tomcat version mismatch between the new and the old server and it seems that between those versions Tomcat changed some default behaviour)
No worries - thanks for letting us know else it would have been something we likely wouldn’t have realised until later and then we would be the one with less hair… though to be honest I already have very little!