# AWX Openshift route not working **URL:** \ **Category:** Get Help\ **Tags:** community, openshift, awx\ **Created:** [October 12, 2023, 4:44pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683 "2023-10-12T16:44:06Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![dkoci](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dkoci/32/815_2.png) [@dkoci](https://forum.ansible.com/u/dkoci)\ **Post date:** [October 12, 2023, 4:44pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/1 "2023-10-12T16:44:06Z")
Hi. I installed AWX with Helm in Openshift. Everything looks fine, all pods are up & running. But i cant access the AWX console. It gives me 503 Service Unavailable error. I cant see any issues in logs. Any idea? Thnak you ---
**Author:** ![ptn](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ptn/32/481_2.png) [@ptn](https://forum.ansible.com/u/ptn)\ **Post date:** [October 12, 2023, 5:30pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/2 "2023-10-12T17:30:07Z")
Hi, 503/HTTP means an issue on backend service, so surely not a routing issue AFAICT. Have you tried [port forwarding](https://docs.openshift.com/container-platform/3.11/dev_guide/port_forwarding.html) directly through your pod ? (or proxy, more or less the same) > I cant see any issues in logs Which logs ? Is there anything else ? Do you have logs on your ingress controller (you mentioned routes so it should be haproxy) ? Some info [here](https://docs.openshift.com/container-platform/3.11/admin_guide/router.html). Could you also post your AWX pod, service and ingress / route configs ? ---
**Author:** ![dkoci](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dkoci/32/815_2.png) [@dkoci](https://forum.ansible.com/u/dkoci)\ **Post date:** [October 12, 2023, 5:41pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/3 "2023-10-12T17:41:41Z")
Service: ![image](https://us1.discourse-cdn.com/ansible/original/2X/d/d73147622457f829f4a75280097a79e7f73a73f1.png) Route type is Edge and uses our default ingress TLS certificates. awx-web pod logs: ```auto 1:C 12 Oct 2023 17:18:27.830 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 12 Oct 2023 17:18:27.830 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 12 Oct 2023 17:18:27.830 * Configuration loaded 1:M 12 Oct 2023 17:18:27.830 * monotonic clock: POSIX clock_gettime 1:M 12 Oct 2023 17:18:27.831 * Running mode=standalone, port=0. 1:M 12 Oct 2023 17:18:27.831 * Server initialized 1:M 12 Oct 2023 17:18:27.831 * Ready to accept connections unix ``` awx-operator-controller-manager pod logs: ```auto Flag --logtostderr has been deprecated, will be removed in a future release, see https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components W1012 17:17:21.682328 1 kube-rbac-proxy.go:152] ==== Deprecation Warning ====================== Insecure listen address will be removed. Using --insecure-listen-address won't be possible! The ability to run kube-rbac-proxy without TLS certificates will be removed. Not using --tls-cert-file and --tls-private-key-file won't be possible! For more information, please go to https://github.com/brancz/kube-rbac-proxy/issues/187 =============================================== I1012 17:17:21.682391 1 kube-rbac-proxy.go:272] Valid token audiences: I1012 17:17:21.682429 1 kube-rbac-proxy.go:363] Generating self signed cert as no cert is provided I1012 17:17:22.452094 1 kube-rbac-proxy.go:414] Starting TCP socket on 0.0.0.0:8443 I1012 17:17:22.452794 1 kube-rbac-proxy.go:421] Listening securely on 0.0.0.0:8443 ``` There are no awx related logs in openshift-ingress pod logs. ---
**Author:** ![dkoci](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dkoci/32/815_2.png) [@dkoci](https://forum.ansible.com/u/dkoci)\ **Post date:** [October 12, 2023, 5:42pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/4 "2023-10-12T17:42:18Z")
Pods: ![image](https://us1.discourse-cdn.com/ansible/original/2X/f/fdbcf67bb06ba2f8f6f12917ac58e667ff1ae69f.png) ---
**Author:** ![ptn](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ptn/32/481_2.png) [@ptn](https://forum.ansible.com/u/ptn)\ **Post date:** [October 13, 2023, 11:36am UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/5 "2023-10-13T11:36:55Z")
Disclaimer: I don’t use AWX and don’t know much about it apart from a functional standpoint. Your service (awx-service) is apparently routing to your pod (awx-web) on port 8052/TCP; is this port listening on pod ? I also suggested earlier testing direct access to your pod so you can rule out any potential upstream routing issue; can you try that and post some `curl -Iv 127.0.0.1:` trace ? awx-web logs are only showing a Redis instance starting but nothing else. I’m not sure what to expect here, but awx API container should be running in this pod; could you run these commands and paste outputs here ?: `kubectl get pod -n awx -o json | jq -c '.spec.containers[] | select( .name == "awx-web")' | jq` and `kubectl get pod -n -o json | jq -c '.status.containerStatuses[] | select( .name == "awx-web")' | jq` You posted the operator logs, though I have no idea on what it does (apart from deploying AWX stack in the first place), and how it works. I see mentions to `kube-rbac-proxy` in logs but I don’t know what it is. I suggest to focus on awx-web pod access issue and leave operator on the side for a while. Also not to scorn you or anything but could you post yaml config of your objects instead of GUI screenshots ? There would be more pertinent information in there, like selectors and status. For now, could you post your route specs ? ---
**Author:** ![dkoci](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dkoci/32/815_2.png) [@dkoci](https://forum.ansible.com/u/dkoci)\ **Post date:** [October 13, 2023, 12:19pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/6 "2023-10-13T12:19:14Z")
I found the issue. The problem was port 80. Openshift uses restricted SCC, which prevents the use of ports \< 1024. The solution was to enable the anyuid SCC for the service account used by the awx-web pod. ---
**Author:** ![TheRealHaoLiu](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/therealhaoliu/32/100_2.png) [@TheRealHaoLiu](https://forum.ansible.com/u/TheRealHaoLiu)\ **Post date:** [October 13, 2023, 5:26pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/7 "2023-10-13T17:26:10Z")
i see your awx-web container have 2 restart can u confirm that its not in a crash loop? ---
**Author:** ![dkoci](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dkoci/32/815_2.png) [@dkoci](https://forum.ansible.com/u/dkoci)\ **Post date:** [October 13, 2023, 5:58pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/8 "2023-10-13T17:58:53Z")
@TheRealHaoLiu I performed a manual restart of the pod. I found a solution, so I will mark this topic as “resolved” 🙂 . ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [November 12, 2023, 5:59pm UTC](https://forum.ansible.com/t/awx-openshift-route-not-working/1683/9 "2023-11-12T17:59:54Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.