# Isntalling awx operator

**URL:** <https://forum.ansible.com/t/isntalling-awx-operator/41101>\
**Category:** Get Help\
**Tags:** ubuntu, awx\
**Created:** [March 18, 2025, 8:31am UTC](https://forum.ansible.com/t/isntalling-awx-operator/41101 "2025-03-18T08:31:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Saber](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@Saber](https://forum.ansible.com/u/Saber)\
**Post date:** [March 18, 2025, 8:31am UTC](https://forum.ansible.com/t/isntalling-awx-operator/41101/1 "2025-03-18T08:31:39Z")

</div>

I have an issue regarding installation of awx operator, Im using ubuntu vm and this is the link that I follow [https://computingforgeeks.com/how-to-install-ansible-awx-on-ubuntu-linux/](https://computingforgeeks.com/how-to-install-ansible-awx-on-ubuntu-linux/)  
Im confuse on this step, you can check the attachment. Do you know how to fix this? thankyou

 ![image](https://us1.discourse-cdn.com/ansible/original/2X/4/471d77efad21c9ce27a35d1d6b16c2a9efb8d788.png)

---

<div class="post-metadata">

**Author:** ![iwt-cmd](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/iwt-cmd/32/9120_2.png) [@iwt-cmd](https://forum.ansible.com/u/iwt-cmd)\
**Post date:** [March 19, 2025, 12:45pm UTC](https://forum.ansible.com/t/isntalling-awx-operator/41101/2 "2025-03-19T12:45:20Z")

</div>

Hi @Saber,

Can you post the output of the following:

```auto
kubectl get all -n awx

```

Assuming you followed the linked guide, this will show us what port the AWX UI is running on as well as if all the necessary pods and services are started.

Best regards,

Joe

---

<div class="post-metadata">

**Author:** ![Saber](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@Saber](https://forum.ansible.com/u/Saber)\
**Post date:** [March 20, 2025, 3:06am UTC](https://forum.ansible.com/t/isntalling-awx-operator/41101/3 "2025-03-20T03:06:29Z")

</div>

Hi @iwt-cmd this is the output I’m getting. I don’t know what ip address I should use when accessing awx web.

 ![image](https://us1.discourse-cdn.com/ansible/original/2X/a/a7102501a401470e4d09199713e1d958bcc24367.png)

---

<div class="post-metadata">

**Author:** ![ildjarn](https://avatars.discourse-cdn.com/v4/letter/i/8491ac/32.png) [@ildjarn](https://forum.ansible.com/u/ildjarn)\
**Post date:** [March 20, 2025, 8:09am UTC](https://forum.ansible.com/t/isntalling-awx-operator/41101/4 "2025-03-20T08:09:58Z")

</div>

See the part below the commercial in the image that you posted:

http://hostip\_or\_hostname:31742

Best documentation on how to install AWX on k3s that I found is by Kurokobo:

> **[GitHub - kurokobo/awx-on-k3s: An example implementation of AWX on single node...](https://github.com/kurokobo/awx-on-k3s)**
>
> An example implementation of AWX on single node K3s using AWX Operator, with easy-to-use simplified configuration with ownership of data and passwords.

---

<div class="post-metadata">

**Author:** ![iwt-cmd](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/iwt-cmd/32/9120_2.png) [@iwt-cmd](https://forum.ansible.com/u/iwt-cmd)\
**Post date:** [March 20, 2025, 12:56pm UTC](https://forum.ansible.com/t/isntalling-awx-operator/41101/5 "2025-03-20T12:56:03Z")

</div>

100% agree on kurokobo’s guide. It’s what I used to first deploy AWX.

The AWX UI is under the “awx-service” service and, by default, will be exposed internally on port 80 (http). The NodePort service model takes an ephemeral port on the local system (31742 in this case) and forwards that to the port the service is listening on. So to access the AWX login/web UI, you would go to:

http://IP\_of\_K3S\_server:31742

TMK, AWX doesn’t deploy with TLS by default so you will use “http” not “https”. This can and should be changed for long term or non-lab deployments but I would get everything working before you look at layering on the encryption complexity.

 ![image](https://us1.discourse-cdn.com/ansible/original/2X/1/10ba3b4d95ef68e781063660b63755fdceb87e69.png)

The ephemeral port can change if you redeploy the service. If you run into issues loading the UI, check the port again and make sure the firewall on your K3S server is allowing the port or disable the firewall service altogether (similar considerations for security when looking at lab vs long term/prod deployments).

Best regards,

Joe