Replies: 1 comment
-
|
We store a lot of data in the session, so you'll need to ensure the load balancer is using sticky sessions. You may be able to pick up some tricks from https://www.manageiq.org/docs/reference/latest/high_availability_guide/ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Environment Details:
Infrastructure: AWS EC2
Container: IQ Container
Load Balancer: Application Load Balancer (ALB)
DNS: Route 53
Hey Community,
I'm running into a bit of a tricky situation with my ManageIQ setup and could use some expert advice. 🤔
So here's the deal: I've got ManageIQ containerized and running smoothly on an AWS EC2 instance. No problems accessing it directly via IP address - everything works great! 👍
But now I'm trying to level up my setup by:
Putting an Application Load Balancer (ALB) in front of my instance
Configuring Route 53 to point my domain (xxx.com) to the ALB
The catch? When I try accessing via my domain, I'm getting a 400 Bad Request error. 😫
I've already checked the Apache access logs
I suspect the issue lies in the Apache-ManageIQ integration, potentially involving TLS configuration mismatch?
Any insights or troubleshooting steps would be super appreciated! 🙏
Cheers
Beta Was this translation helpful? Give feedback.
All reactions