I have a web app that I'm using for internal purposes running on AWS so that it can be accessed from outside the office and such. It's a spring boot app with autoconfiguration, and for security I'm using Spring Security and encrypting at the load balancer for the production environment (there's a balancer to backend encryption using a self-signed cert as well). I set up an Apache proxy for https redirection (the app runs using Tomcat, and as far as I'm aware you can't configure the connectors), and the stable version is working as expected.
However, when I try to push my latest version, I am getting an error after trying to log in (the login page loads fine, but it gives me 500 errors instead of going to the homepage as it should do). Reverting to the previous version corrects the problem, so I know that the cause has to do with the recent changes I implemented. In particular, the new version has two security filter chains instead of 1, but the one that applies to most requests is exactly the same. The second one is meant to be used only for stateless requests to RESTful calls to the app's functionality, but the 500 error is occurring on requests to the landing page.
The updated version works just fine locally -- the main difference is the direct use of Tomcat for SSL. Even more frustratingly, I can't get anything to show up in the logs, even when I put a catch-all error handler controller that's meant to take any error and log it (as well as return a specific error message, instead of the fallback error page I am seeing). I am getting normal log outputs from my app, so I know the logging itself is working, but regardless of what I try the failure is always silent and I can't for the life of me figure out where the error is even occurring much less what it is.
I can't seem to override the tomcat configs, but previous searches indicate that it could have to do with the HTTP protocol connector. So my question is: how do I figure out what in the world is going on here?I'm seeing a fallback error page (i.e. the default one from tomcat) instead of the exception handler I configured to apply to any exception in Spring.