Any one using the HTTP2 Protocol version on AWS Load Balancer Target Group?

Administration
1

We recently upgraded the Protocol version to HTTP2 in /opt/morpheus/embedded/nginx/conf/sites-available
morpheus-ssl.conf and morpheus.conf.

we also Upgraded the Protocol version from HTTP1 to HTTP2 on Load Balancer Target group, since then Morpheus Agents on the Instances are not reporting the Health, Getting the below error in the agent logs,

anyone runinto any of this error before?

024-10-23_20:50:36.77502 16:50:36.774 [main] INFO com.morpheus.agent.Agent - Initializing Result Publisher...
2024-10-23_20:50:36.78448 16:50:36.784 [main] INFO com.morpheus.agent.Agent - Initializing Stats Collection Job Threads...
2024-10-23_20:50:36.78760 16:50:36.787 [main] INFO com.morpheus.agent.Agent - Initializing Stat Poller...
2024-10-23_20:50:37.06452 16:50:37.064 [nioEventLoopGroup-2-1] INFO com.morpheus.agent.websocket.WebSocketClientHandler - WebSocket Client failed to connect
2024-10-23_20:50:37.06493 16:50:37.064 [main] ERROR com.morpheus.agent.websocket.StompClient - Failed to connect websocket: Invalid handshake response getStatus: 464
2024-10-23_20:50:37.06584 16:50:37.065 [main] INFO com.morpheus.agent.Agent - Agent Online!
2024-10-23_20:50:42.06721 16:50:42.067 [Thread-11] WARN com.morpheus.agent.websocket.StompClient - Stomp client is not currently connected!
2024-10-23_20:50:42.06725 16:50:42.067 [Thread-2] WARN com.morpheus.agent.websocket.StompClient - Stomp client is not currently connected!
2024-10-23_20:50:42.06726 16:50:42.067 [Thread-11] INFO com.morpheus.agent.websocket.StompClient - Attempting to reconnect...
2024-10-23_20:50:42.06726 16:50:42.067 [Thread-2] INFO com.morpheus.agent.websocket.StompClient - Attempting to reconnect...
2024-10-23_20:50:47.10208 16:50:47.101 [nioEventLoopGroup-2-3] INFO com.morpheus.agent.websocket.WebSocketClientHandler - WebSocket Client failed to connect
2024-10-23_20:50:47.10224 16:50:47.102 [nioEventLoopGroup-2-2] ERROR com.morpheus.agent.websocket.StompClient - Failed to connect websocket: Invalid handshake response getStatus: 464```
2

Do you have the option in the load balancer to support both 1.1 and 2? Looks like the agent may need a fallback to 1.1 at this time.

3

@Ollie_Phillips we have to pick Either HTTP1 or HTTP2.

is there any way can change the agent configuration to HTTP2?

image
image624×156 10.6 KB

4

Not all clients support HTTP 2.0 yet so there should be a way to configure it to fall back. Perhaps look at load balancer settings in place of the target group settings If there is nothing obvious I would suggest AWS support may be able to guide you.

5

AWS saying we need to use HTTP2 on the client side, that means, is there any way we can configure the node agent to HTTP2 as needed? that means Morpheus needs to provide node agent to support both HTTP1/2, is that possible?

6

I think you would only want to use HTTP2 on the load balancer target group if you can guarantee what clients will connect to the appliance.

A protocol version of 1.1 looks like it will handle 1.1 and 2 requests (AWS docs)

If that can’t work, you could use a custom IP in the cloud settings and have agents connect to that IP, bypassing the load balancer.