PostgreSQL 13
AWX is exposed via nginx ingress (with domain )
I’ve created a public certificate
I’ve configured azure and AWX according to the documentation.
When I click on the azure button on the connection page, I arrive on the Microsoft part and then I enter my identifiers. Then the page loads for a while and I get a “504 Gateway Time-out error. nginx”.
Is anyone having problems with Azure AD?
Thank you
Best regards,
Wizz
To address the “504 Gateway Time-out error” with Azure AD in AWX, check and adjust the Nginx timeout settings, ensure your Azure AD and AWX configurations match the documentation, inspect network connectivity, and review both AWX and Azure AD logs for errors. This comprehensive approach should help identify and solve the issue.
Yes, I tried to access the nginx settings in the Kubernetes container. But it asks me for a password, I don’t know it. Is there any other way to change the nginx config??
And the file (nginx.conf) is in readonly , i cannot modify
Ok, let me start from the beginning:
1 I created the app on azure AD
2- created a “web” web application (adding the rollback link I found on AWX https://fdqn/sso/complete/azuread-oauth2/)
3-I changed the default name to towerhost on the awx web interface
I work behind a proxy.
I’ve just realised that my traffic does not go through the proxy never use the proxy, even though I’ve added the http_proxy :
1 on awx.yml
2 /etc/systemd/system/k3s.service.env
How did you add proxies on awx.yml? If you have done it by adding AWX_TASK_ENV['HTTP_PROXY'] in extra_settings, I haven’t read the code in detail, but I’m a little unsure if that works for social auth as well.
Can you try adding proxies by task_extra_env and web_extra_env in awx.yaml?