# After deploy, ui login does not work **URL:** \ **Category:** AWX Project\ **Tags:** rhel, awx, kubernetes\ **Created:** [May 25, 2021, 10:39pm UTC](https://forum.ansible.com/t/after-deploy-ui-login-does-not-work/35226 "2021-05-25T22:39:57Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Bob\_Dole](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@Bob\_Dole](https://forum.ansible.com/u/Bob_Dole)\ **Post date:** [May 25, 2021, 10:39pm UTC](https://forum.ansible.com/t/after-deploy-ui-login-does-not-work/35226/1 "2021-05-25T22:39:57Z")
After I deploy awx using minikube I am unable to log into the UI. I checked selinux, verifying the user exists etc… I still get “There was a problem signing in. Please try again.”. I think the admin account exists, at least it tells me it does. I run this and get the password: minikube kubectl – get secret awx-admin-password -o jsonpath=‘{.data.password}’ | base64 --decode I tried to create superuser just in case but it states super user admin already exists, so I created another dummy account and that still doesn’t work. Hey at least the web page looks shiny :). This is a RHeL 8.3 server Below is a bit of what I did to deploy. wget [https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86\_64.rpm](https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86_64.rpm) –2021-05-25 17:45:40-- [https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86\_64.rpm](https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86_64.rpm) Resolving [github.com](http://github.com) ([github.com](http://github.com))… 140.82.112.3 Connecting to [github.com](http://github.com) ([github.com](http://github.com))|140.82.112.3|:443… connected. HTTP request sent, awaiting response… 302 Found Location: [https://github-releases.githubusercontent.com/56353740/d7369b80-7ce4-11eb-9690-bbd4b776a344?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210525%2Fus-east-1%2Fs3%2Faws4\_request&X-Amz-Date=20210525T214541Z&X-Amz-Expires=300&X-Amz-Signature=583793329787419a56b29eba3d16cfec4164d2a294ac4b26ffa153d21c9d768e&X-Amz-SignedHeaders=host&actor\_id=0&key\_id=0&repo\_id=56353740&response-content-disposition=attachment%3B%20filename%3Dminikube-1.18.1-0.x86\_64.rpm&response-content-type=application%2Foctet-stream](https://github-releases.githubusercontent.com/56353740/d7369b80-7ce4-11eb-9690-bbd4b776a344?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210525%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210525T214541Z&X-Amz-Expires=300&X-Amz-Signature=583793329787419a56b29eba3d16cfec4164d2a294ac4b26ffa153d21c9d768e&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=56353740&response-content-disposition=attachment%3B%20filename%3Dminikube-1.18.1-0.x86_64.rpm&response-content-type=application%2Foctet-stream) [following] –2021-05-25 17:45:41-- [https://github-releases.githubusercontent.com/56353740/d7369b80-7ce4-11eb-9690-bbd4b776a344?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210525%2Fus-east-1%2Fs3%2Faws4\_request&X-Amz-Date=20210525T214541Z&X-Amz-Expires=300&X-Amz-Signature=583793329787419a56b29eba3d16cfec4164d2a294ac4b26ffa153d21c9d768e&X-Amz-SignedHeaders=host&actor\_id=0&key\_id=0&repo\_id=56353740&response-content-disposition=attachment%3B%20filename%3Dminikube-1.18.1-0.x86\_64.rpm&response-content-type=application%2Foctet-stream](https://github-releases.githubusercontent.com/56353740/d7369b80-7ce4-11eb-9690-bbd4b776a344?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210525%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210525T214541Z&X-Amz-Expires=300&X-Amz-Signature=583793329787419a56b29eba3d16cfec4164d2a294ac4b26ffa153d21c9d768e&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=56353740&response-content-disposition=attachment%3B%20filename%3Dminikube-1.18.1-0.x86_64.rpm&response-content-type=application%2Foctet-stream) Resolving [github-releases.githubusercontent.com](http://github-releases.githubusercontent.com) ([github-releases.githubusercontent.com](http://github-releases.githubusercontent.com))… 185.199.108.154, 185.199.109.154, 185.199.110.154, … Connecting to [github-releases.githubusercontent.com](http://github-releases.githubusercontent.com) ([github-releases.githubusercontent.com](http://github-releases.githubusercontent.com))|185.199.108.154|:443… connected. HTTP request sent, awaiting response… 200 OK Length: 14329512 (14M) [application/octet-stream] Saving to: ‘minikube-1.18.1-0.x86\_64.rpm’ minikube-1.18.1-0.x86\_64.rpm 100%[========================================================================================================================================\>] 13.67M 10.4MB/s in 1.3s [null@server01 awx]$ sudo rpm -Uvh minikube-1.18.1-0.x86\_64.rpm [null@server01 awx]$ minikube start --driver=podman --container-runtime=cri-o --cpus=4 --memory=8g --addons=ingress - minikube v1.18.1 on Redhat 8.3 - Using the podman driver based on user configuration - minikube 1.20.0 is available! Download it: [https://github.com/kubernetes/minikube/releases/tag/v1.20.0](https://github.com/kubernetes/minikube/releases/tag/v1.20.0) - To disable this notice, run: ‘minikube config set WantUpdateNotification false’ ! Your cgroup does not allow setting memory. - More information: [https://docs.doInfo.com/engine/install/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities](https://docs.doInfo.com/engine/install/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities) - Starting control plane node minikube in cluster minikube - Downloading Kubernetes v1.20.2 preload … > preloaded-images-k8s-v9-v1…: 560.29 MiB / 560.29 MiB 100.00% 6.62 MiB - Creating podman container (CPUs=4, Memory=8192MB) … - Preparing Kubernetes v1.20.2 on CRI-O 1.20.0 … - Generating certificates and keys … - Booting up control plane … - Configuring RBAC rules … - Configuring CNI (Container Networking Interface) … - Verifying Kubernetes components… - Using image [gcr.io/k8s-minikube/storage-provisioner:v4](http://gcr.io/k8s-minikube/storage-provisioner:v4) - Using image [us.gcr.io/k8s-artifacts-prod/ingress-nginx/controller:v0.40.2](http://us.gcr.io/k8s-artifacts-prod/ingress-nginx/controller:v0.40.2) - Using image jettech/kube-webhook-certgen:v1.2.2 - Using image jettech/kube-webhook-certgen:v1.3.0 - Verifying ingress addon… - Enabled addons: storage-provisioner, default-storageclass, ingress - kubectl not found. If you need it, try: ‘minikube kubectl – get pods -A’ - Done! kubectl is now configured to use “minikube” cluster and “default” namespace by default [null@server01 awx]$ minikube kubectl – apply -f [https://raw.githubusercontent.com/ansible/awx-operator/0.9.0/deploy/awx-operator.yaml](https://raw.githubusercontent.com/ansible/awx-operator/0.9.0/deploy/awx-operator.yaml) > kubectl.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s > kubectl: 38.37 MiB / 38.37 MiB [---------------] 100.00% 1.37 MiB p/s 28s > [customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com](http://customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com) created > [clusterrole.rbac.authorization.k8s.io/awx-operator](http://clusterrole.rbac.authorization.k8s.io/awx-operator) created > [clusterrolebinding.rbac.authorization.k8s.io/awx-operator](http://clusterrolebinding.rbac.authorization.k8s.io/awx-operator) created > serviceaccount/awx-operator created > deployment.apps/awx-operator created > [null@server01 awx]$ minikube kubectl apply – -f myawx.yml > [awx.awx.ansible.com/awx](http://awx.awx.ansible.com/awx) created > [null@server01 awx]$ watch minikube kubectl – get pods -A > [null@server01 awx]$ minikube service list > -------------|------------------------------------|--------------|---------------------------| > > | NAMESPACE | NAME | TARGET PORT | URL | > | --- | --- | --- | --- | > | default | awx-operator-metrics | No node port | | > | default | awx-postgres | No node port | | > | default | awx-service | http/80 | [http://192.168.49.2:31377](http://192.168.49.2:31377) | > | default | kubernetes | No node port | | > | kube-system | ingress-nginx-controller-admission | No node port | | > | kube-system | kube-dns | No node port | | > | ------------- | ------------------------------------ | -------------- | --------------------------- | [null@server01 awx]$ minikube service awx-service --url [http://192.168.49.2:31377](http://192.168.49.2:31377) ---
**Author:** ![ffirg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ffirg/32/10029_2.png) [@ffirg](https://forum.ansible.com/u/ffirg)\ **Post date:** [May 26, 2021, 9:35am UTC](https://forum.ansible.com/t/after-deploy-ui-login-does-not-work/35226/2 "2021-05-26T09:35:10Z")
The lack of some ingress controllers not running properly is worrying: minikube service list > ---------------|------------------------------------|--------------|---------------------------| > > | NAMESPACE | NAME | TARGET PORT | URL | > | --- | --- | --- | --- | > | default | awx-operator-metrics | No node port | | > | default | awx-postgres | No node port | | > | default | awx-service | http/80 | [http://192.168.49.2:30898](http://192.168.49.2:30898) | > | default | kubernetes | No node port | | > | ingress-nginx | ingress-nginx-controller | http/80 | [http://192.168.49.2:32715](http://192.168.49.2:32715) | > > > > https/443 | [http://192.168.49.2:31074](http://192.168.49.2:31074) | > > > ingress-nginx | ingress-nginx-controller-admission | No node port | > > > kube-system | kube-dns | No node port | > > > ---------------|------------------------------------|--------------|---------------------------| Try using the latest minikube which is currently 1.20. 1.18 looks like it could be quite out of date as lots of images etc were updated and pulled down in 1.20 curl -LO [https://storage.googleapis.com/minikube/releases/latest/minikube-latest.x86\_64.rpm](https://storage.googleapis.com/minikube/releases/latest/minikube-latest.x86_64.rpm) sudo rpm -Uvh minikube-latest.x86\_64.rpm ---
**Author:** ![Bob\_Dole](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@Bob\_Dole](https://forum.ansible.com/u/Bob_Dole)\ **Post date:** [May 26, 2021, 12:51pm UTC](https://forum.ansible.com/t/after-deploy-ui-login-does-not-work/35226/3 "2021-05-26T12:51:04Z")
That’s what I originally did, I ran into the same issue. I then reread here [https://github.com/ansible/awx/blob/devel/INSTALL.md#installing-awx](https://github.com/ansible/awx/blob/devel/INSTALL.md#installing-awx) and it states to use version 1.18.1. My original route to install minikube: wget [https://storage.googleapis.com/minikube/releases/latest/minikube-latest.x86\_64.rpm](https://storage.googleapis.com/minikube/releases/latest/minikube-latest.x86_64.rpm) rpm -Uvh minikube-latest.x86\_64.rpm After Reading the “Note”: wget [https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86\_64.rpm](https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86_64.rpm) rpm -Uvh [minikube-1.18.1-0.x86\_64.rpm](https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86_64.rpm) Note from Link above: ⚠ NOTE If you’re about to install minikube or have already installed it, please be sure you’re using [Minikube v1.18.1](https://github.com/kubernetes/minikube/releases/tag/v1.18.1). There’s a [bug](https://github.com/ansible/awx-operator/issues/205) right now that will not allow you to run it using Minikube v1.19.x. ---
**Author:** ![ffirg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ffirg/32/10029_2.png) [@ffirg](https://forum.ansible.com/u/ffirg)\ **Post date:** [May 27, 2021, 8:58am UTC](https://forum.ansible.com/t/after-deploy-ui-login-does-not-work/35226/4 "2021-05-27T08:58:35Z")
The docs might be out of date, as minikube is now on 1.20 and they only talk about 1.19. I’m using 1.20 with AWX 19.0 and it’s working fine and the minikube service list matches what I posted before. The ingress controller is your problem. I suspect everything else is running fine. pip3 install awxkit awx --conf.host [http://192.168.49.2:31099](http://192.168.49.2:31099) --conf.username admin --conf.password pcvYqZY4jd29pTkUHftkLsa4UzVBFIbRp login awx --conf.host [http://192.168.49.2:31099](http://192.168.49.2:31099) --conf.username admin --conf.password pcvYqZY4jd29pTkUHftkLsa4UzVBFIbRp me just to prove it (that’ll hit the API) ---
**Author:** ![Dennis\_McCarthy1](https://avatars.discourse-cdn.com/v4/letter/d/34f0e0/32.png) [@Dennis\_McCarthy1](https://forum.ansible.com/u/Dennis_McCarthy1)\ **Post date:** [June 7, 2021, 12:17pm UTC](https://forum.ansible.com/t/after-deploy-ui-login-does-not-work/35226/5 "2021-06-07T12:17:17Z")
This might help if you’re using minikube: [https://youtu.be/AYfqkTbCDAw](https://youtu.be/AYfqkTbCDAw)