Difficulty with an desktop management application on EC2 behind an internal Application Load Balancer

Hi all, I have an internal desktop management application hosted on an EC2 instance that I'm trying to put behind an internal ALB. Everything looks fine when I access the web interface of the app, however, when I try to use any of the remote access functionality of the tool (used for remote management such as screensharing, file management, software deployment, etc), these features all time out. I've also tried enabling the X-Forwarded-For header as it appeared to be a problem with how the console sees the administrator who connects to the instance and how to send that traffic back to requester's (the admin initiating the connection) IP address, however, this doesn't appear to have made a difference. There are some threads that seem to indicate some additional configuration required on the application side with regards to Tomcat to be able to capture the X-Forwarded-For header but I've not had any luck yet, I'm also still waiting to hear back from the vendor's support but wanted to make sure I'm not missing any obvious configurations within AWS.

Is this an application that can work behind an ALB? If so, what other configurations would I need to account for?

This is Manage Engine's Endpoint Central application and the following link shows the required ports when configuring this normally. https://www.manageengine.com/products/desktop-central/desktop-central-lan-architecture.html#dcports

For example: