# Unable to launch AWX UI using Load Balancer **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [June 21, 2022, 7:00pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763 "2022-06-21T19:00:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [June 21, 2022, 7:00pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/1 "2022-06-21T19:00:55Z")
I’m unable to launch the AWX ui using **http://:30102.** I have the pods successfully deployed though - NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE awx-operator-awx-service LoadBalancer 10.100.197.40 **xx.xx.xx.xx** **80:30102** /TCP 80m awx-operator-controller-manager-metrics-service ClusterIP 10.100.206.47 8443/TCP 81m Any advise? ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [June 22, 2022, 7:26pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/2 "2022-06-22T19:26:41Z")
Hi, what errors are you getting / seeing when attempting to access that address? AWX Team ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 11, 2022, 7:42pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/3 "2022-07-11T19:42:39Z")
The url just keeps loading without any error for a long time and then gets timed out. **awx-web** container logs: [wait-for-migrations] Waiting for database migrations… [wait-for-migrations] Attempt 1 of 30 [wait-for-migrations] Waiting 0.5 seconds before next attempt [wait-for-migrations] Attempt 2 of 30 [wait-for-migrations] Waiting 1 seconds before next attempt [wait-for-migrations] Attempt 3 of 30 [wait-for-migrations] Waiting 2 seconds before next attempt [wait-for-migrations] Attempt 4 of 30 [wait-for-migrations] Waiting 4 seconds before next attempt **awx-task** container logs: [wait-for-migrations] Waiting for database migrations… [wait-for-migrations] Attempt 1 of 30 [wait-for-migrations] Waiting 0.5 seconds before next attempt [wait-for-migrations] Attempt 2 of 30 [wait-for-migrations] Waiting 1 seconds before next attempt [wait-for-migrations] Attempt 3 of 30 [wait-for-migrations] Waiting 2 seconds before next attempt [wait-for-migrations] Attempt 4 of 30 [wait-for-migrations] Waiting 4 seconds before next attempt **Redis** container logs: 1:C 22 Jun 2022 15:06:49.121 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 22 Jun 2022 15:06:49.121 # Redis version=7.0.0, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 22 Jun 2022 15:06:49.121 # Configuration loaded 1:M 22 Jun 2022 15:06:49.122 \* monotonic clock: POSIX clock\_gettime 1:M 22 Jun 2022 15:06:49.122 \* Running mode=standalone, port=0. 1:M 22 Jun 2022 15:06:49.122 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. 1:M 22 Jun 2022 15:06:49.122 # Server initialized 1:M 22 Jun 2022 15:06:49.123 \* The AOF directory appendonlydir doesn’t exist 1:M 22 Jun 2022 15:06:49.123 \* The server is now ready to accept connections at /var/run/redis/redis.sock **awx-ee** container logs: DEBUG 2022/07/11 18:02:22 Sending service advertisement: &{awx-7d5bd6b6d-rnp7b control 2022-07-11 18:02:22.849520469 +0000 UTC m=+1652132.737023817 1 map[type:Control Service] [{local false} {kubernetes-runtime-auth false} {kubernetes-incluster-auth false}]} DEBUG 2022/07/11 18:03:22 Sending service advertisement: &{awx-7d5bd6b6d-rnp7b control 2022-07-11 18:03:22.852138837 +0000 UTC m=+1652192.739642185 1 map[type:Control Service] [{local false} {kubernetes-runtime-auth false} {kubernetes-incluster-auth false}]} DEBUG 2022/07/11 18:04:22 Sending service advertisement: &{awx-7d5bd6b6d-rnp7b control 2022-07-11 18:04:22.854355392 +0000 UTC m=+1652252.741858745 1 map[type:Control Service] [{local false} {kubernetes-runtime-auth false} {kubernetes-incluster-auth false}]} ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [July 13, 2022, 7:38pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/4 "2022-07-13T19:38:35Z")
according to your logs, it looks like the migrations never ran to completion. It does take a while to run them; does the app eventually start after 30 minutes or so? what is the status of your postgres pod? any error messages there? AWX Team ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 13, 2022, 8:54pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/5 "2022-07-13T20:54:26Z")
I’m using an external postgres instance. The database migration has already been completed. Even then, the AWX containers still show this error of “Waiting for database migrations…”. Is it because this AWX pod isn’t able to access the externally hosted postgres instance? ---
**Author:** ![mani3887](https://avatars.discourse-cdn.com/v4/letter/m/9f8e36/32.png) [@mani3887](https://forum.ansible.com/u/mani3887)\ **Post date:** [July 14, 2022, 2:14am UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/6 "2022-07-14T02:14:22Z")
I have seen a similar issue. For me, it happened because the pod was not able to connect to Postgres DB. Can you please check whether pod is able to communicate with Postgres DB. If not, please check for your connectivity, firewall rules. ---
**Author:** ![Z\_M](https://avatars.discourse-cdn.com/v4/letter/z/b782af/32.png) [@Z\_M](https://forum.ansible.com/u/Z_M)\ **Post date:** [July 14, 2022, 1:19pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/7 "2022-07-14T13:19:21Z")
Can you advise how best to check if the pod is able to connect to the DB? ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 19, 2022, 2:24pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/8 "2022-07-19T14:24:56Z")
I have checked the AWX pod connectivity to the external postgres instance and that works fine. Firewall has been whitelisted. Still get the database migrations pending logs… ---
**Author:** ![Z\_M](https://avatars.discourse-cdn.com/v4/letter/z/b782af/32.png) [@Z\_M](https://forum.ansible.com/u/Z_M)\ **Post date:** [July 19, 2022, 3:13pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/9 "2022-07-19T15:13:07Z")
This recently tripped me up when I was using an older version of AWX that was connecting to postgres11. As soon as I started a newer instance running postgres12, this worked fine with the latest operator. Can you confirm which version of a Db you’re running? Find the post that is not the pod/awx-operator, should pod/awx-\*\*\*\*\*\*\*-\*\*\*\*\* Can you run the following commands: kubectl -n yournamespace get awx,all,ingress,secrets kubectl logs pod/awx-\*\*\*\*\*\*\* -n yournamespace -c redis kubectl logs pod/awx-\*\*\*\*\*\*\* -n yournamespace -c awx-task kubectl logs pod/awx-\*\*\*\*\*\*\* -n yournamespace -c awx-ee ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 19, 2022, 10:25pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/10 "2022-07-19T22:25:10Z")
I’m currently using **awx-operator 0.23.0** and **postgres14.** I recently upgraded the postgres instance to v14. But was facing the same issue with v12 previously as well. [user@hostname ~]$ **_kubectl -n ansible-awx get awx,all,ingress,secrets_** NAME AGE [awx.awx.ansible.com/awx](http://awx.awx.ansible.com/awx) 6d1h NAME READY STATUS RESTARTS AGE pod/awx-7d5bd6b6d-xgfn2 4/4 Running 1336 (6m19s ago) 6d1h pod/controller-manager-dc95b975b-l4lzq 2/2 Running 0 6d1h NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/awx-service LoadBalancer 10.100.199.20 x.x.x.x 443:30784/TCP 6d1h service/controller-manager-metrics-service ClusterIP 10.100.193.189 8443/TCP 6d1h NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/awx 1/1 1 1 6d1h deployment.apps/controller-manager 1/1 1 1 6d1h NAME DESIRED CURRENT READY AGE replicaset.apps/awx-7d5bd6b6d 1 1 1 6d1h replicaset.apps/controller-manager-dc95b975b 1 1 1 6d1h NAME CLASS HOSTS ADDRESS PORTS AGE [ingress.networking.k8s.io/awx-ingress](http://ingress.networking.k8s.io/awx-ingress)[awx-dev.blackrock.com](http://awx-dev.blackrock.com) x.x.x.x 80 6d1h NAME TYPE DATA AGE secret/awx-admin-password Opaque 1 6d1h secret/awx-app-credentials Opaque 3 6d1h secret/awx-broadcast-websocket Opaque 1 6d1h secret/awx-postgres-configuration Opaque 7 6d1h secret/awx-secret-key Opaque 1 6d1h secret/awx-token-c4mbf [kubernetes.io/service-account-token](http://kubernetes.io/service-account-token) 3 6d1h secret/controller-manager-token-4djz7 [kubernetes.io/service-account-token](http://kubernetes.io/service-account-token) 3 6d1h secret/default-token-tbz2s [kubernetes.io/service-account-token](http://kubernetes.io/service-account-token) 3 6d1h I had posted all the container logs in my previous comments. ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [July 20, 2022, 7:26pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/11 "2022-07-20T19:26:21Z")
> I’m using an external postgres instance. The database migration has already been completed. How are you verifying that the migration is complete? What does “awx-manage showmigrations” in the awx-task container show, or “awx-manage check\_db” ? Note that postgres 14 _may_ work, but it is currently unsupported (we don’t test it explicitly) AWX Team ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 21, 2022, 6:04pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/12 "2022-07-21T18:04:08Z")
Below are the awx-task container logs for “awx-manage showmigrations”. I get the same error for check\_db as well - [user@hostname ~]$ **kubectl exec awx-7d5bd6b6d-kj4c6 -c awx-task -n ansible-awx awx-manage showmigrations** kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] – [COMMAND] instead. 2022-07-21 17:45:26,492 ERROR [-] awx.main.utils.encryption Failed to decrypt `Setting(pk=20).value`; if you’ve recently restored from a database backup or are running in a clustered environment, check that your `SECRET_KEY` value is correct Traceback (most recent call last): File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 120, in \_verify\_signature h.verify(data[-32:]) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/hazmat/primitives/hmac.py”, line 69, in verify ctx.verify(signature) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/hazmat/backends/openssl/hmac.py”, line 76, in verify raise InvalidSignature(“Signature did not match digest.”) cryptography.exceptions.InvalidSignature: Signature did not match digest. During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/utils/encryption.py”, line 159, in decrypt\_field return smart\_str(decrypt\_value(key, value)) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/utils/encryption.py”, line 136, in decrypt\_value value = f.decrypt(encrypted) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 81, in decrypt return self.\_decrypt\_data(data, timestamp, time\_info) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 138, in \_decrypt\_data self.\_verify\_signature(data) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 122, in \_verify\_signature raise InvalidToken cryptography.fernet.InvalidToken Traceback (most recent call last): File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 120, in \_verify\_signature h.verify(data[-32:]) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/hazmat/primitives/hmac.py”, line 69, in verify ctx.verify(signature) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/hazmat/backends/openssl/hmac.py”, line 76, in verify **_raise InvalidSignature(“Signature did not match digest.”)_** **_cryptography.exceptions.InvalidSignature: Signature did not match digest._** During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/usr/bin/awx-manage”, line 8, in sys.exit(manage()) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/ **init**.py”, line 170, in manage execute\_from\_command\_line(sys.argv) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/management/ **init**.py”, line 419, in execute\_from\_command\_line utility.execute() File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/management/ **init**.py”, line 413, in execute self.fetch\_command(subcommand).run\_from\_argv(self.argv) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/management/base.py”, line 354, in run\_from\_argv self.execute(\*args, \*\*cmd\_options) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/management/base.py”, line 393, in execute self.check() File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/management/base.py”, line 419, in check all\_issues = checks.run\_checks( File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/checks/registry.py”, line 76, in run\_checks new\_errors = check(app\_configs=app\_configs, databases=databases) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/checks/urls.py”, line 13, in check\_url\_config return check\_resolver(resolver) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/core/checks/urls.py”, line 23, in check\_resolver return check\_method() File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/urls/resolvers.py”, line 416, in check for pattern in self.url\_patterns: File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/utils/functional.py”, line 48, in **get** res = instance. **dict** [self.name] = self.func(instance) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/urls/resolvers.py”, line 602, in url\_patterns patterns = getattr(self.urlconf\_module, “urlpatterns”, self.urlconf\_module) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/utils/functional.py”, line 48, in **get** res = instance. **dict** [self.name] = self.func(instance) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/urls/resolvers.py”, line 595, in urlconf\_module return import\_module(self.urlconf\_name) File “/usr/lib64/python3.9/importlib/ **init**.py”, line 127, in import\_module return \_bootstrap.\_gcd\_import(name[level:], package, level) File “”, line 1030, in \_gcd\_import File “”, line 1007, in \_find\_and\_load File “”, line 986, in \_find\_and\_load\_unlocked File “”, line 680, in \_load\_unlocked File “”, line 850, in exec\_module File “”, line 228, in \_call\_with\_frames\_removed File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/urls.py”, line 12, in re\_path(r’^api/', include(‘awx.api.urls’, namespace=‘api’)), File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/urls/conf.py”, line 34, in include urlconf\_module = import\_module(urlconf\_module) File “/usr/lib64/python3.9/importlib/ **init**.py”, line 127, in import\_module return \_bootstrap.\_gcd\_import(name[level:], package, level) File “”, line 1030, in \_gcd\_import File “”, line 1007, in \_find\_and\_load File “”, line 986, in \_find\_and\_load\_unlocked File “”, line 680, in \_load\_unlocked File “”, line 850, in exec\_module File “”, line 228, in \_call\_with\_frames\_removed File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/api/urls/ **init**.py”, line 5, in from .urls import urlpatterns File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/api/urls/urls.py”, line 71, in from .oauth2\_root import urls as oauth2\_root\_urls File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/api/urls/oauth2\_root.py”, line 10, in from oauth2\_provider import views File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/oauth2\_provider/views/ **init**.py”, line 2, in from .base import AuthorizationView, TokenView, RevokeTokenView # isort:skip File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/oauth2\_provider/views/base.py”, line 69, in class AuthorizationView(BaseAuthorizationView, FormView): File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/oauth2\_provider/views/base.py”, line 93, in AuthorizationView server\_class = oauth2\_settings.OAUTH2\_SERVER\_CLASS File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/ **init**.py”, line 89, in oauth2\_getattribute val = settings.OAUTH2\_PROVIDER.get(attr) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/conf/settings.py”, line 489, in **getattr\_without\_cache** return getattr(self.\_wrapped, name) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cachetools/decorators.py”, line 22, in wrapper v = func(\*args, \*\*kwargs) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/conf/settings.py”, line 404, in **getattr** value = self.\_get\_local(name) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/conf/settings.py”, line 326, in \_get\_local self.\_preload\_cache() File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/conf/settings.py”, line 300, in \_preload\_cache value = decrypt\_field(setting, ‘value’) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/utils/encryption.py”, line 159, in decrypt\_field return smart\_str(decrypt\_value(key, value)) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/utils/encryption.py”, line 136, in decrypt\_value value = f.decrypt(encrypted) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 81, in decrypt return self.\_decrypt\_data(data, timestamp, time\_info) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 138, in \_decrypt\_data self.\_verify\_signature(data) File “/var/lib/awx/venv/awx/lib64/python3.9/site-packages/cryptography/fernet.py”, line 122, in \_verify\_signature raise InvalidToken **_cryptography.fernet.InvalidToken_** **_command terminated with exit code 1_** ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [July 25, 2022, 12:02pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/13 "2022-07-25T12:02:33Z")
The error above suggests that your secret key is bad: `awx.main.utils.encryption Failed to decrypt `Setting(pk=20).value`; if you've recently restored from a database backup or are running in a clustered environment, check that your `SECRET\_KEY` value is correct`. Did you happen to point a new pod to an existing database without specifying the secret\_key? There are encrypted values stored in the database and the secret\_key held by the pod is used to decrypt them. See: [https://github.com/ansible/awx-operator#secret-key-configuration](https://github.com/ansible/awx-operator#secret-key-configuration) There has been other threads on this group where others had this issue. i.e. [https://groups.google.com/g/awx-project/c/qugKoMu4CHY/m/v3PnO\_kDAgAJ](https://groups.google.com/g/awx-project/c/qugKoMu4CHY/m/v3PnO_kDAgAJ) -The AWX Team ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 26, 2022, 2:05am UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/14 "2022-07-26T02:05:57Z")
Where can I get the value of this secret\_key from in order to specify it in the AWX spec ? The database? ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [July 27, 2022, 11:44am UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/15 "2022-07-27T11:44:39Z")
The key is not stored in the database. It would be defined in the original name space you initially deployed AWX into as a secret. Per the docs ([https://github.com/ansible/awx-operator#secret-key-configuration](https://github.com/ansible/awx-operator#secret-key-configuration)) the default name would be “-secret-key”. Optionally it would also be in a backup created by the backup role ([https://github.com/ansible/awx-operator/tree/devel/roles/backup](https://github.com/ansible/awx-operator/tree/devel/roles/backup)). -The AWX Team ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 27, 2022, 7:36pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/16 "2022-07-27T19:36:22Z")
I have implemented the suggested changes for awx-secret-key in the spec and secret\_key.yaml.j2 but the execution still fails with the same error mentioned above. Do I need to rebuild my database? Please note that the data stored in my database isn’t encrypted. Do I still need this secret to decrypt the values stored in the DB? ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [July 27, 2022, 8:11pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/17 "2022-07-27T20:11:39Z")
According to this thread, if you are comfortable with DBs, you may be able to recover the non encrypted data [https://groups.google.com/g/awx-project/c/qugKoMu4CHY/m/v3PnO\_kDAgAJ](https://groups.google.com/g/awx-project/c/qugKoMu4CHY/m/v3PnO_kDAgAJ) Otherwise you’ll need to rebuild the DB AWX Team ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 29, 2022, 1:54pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/18 "2022-07-29T13:54:53Z")
I was able to rebuild the database use the awx-secret-key in the spec. The error is resolved now, however I’m still not able to access the UI - [user@hostname~]$ **kubectl exec awx-7d5bd6b6d-pz9bd -c awx-task -n ansible-awx _awx-manage check\_db_** kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] – [COMMAND] instead. Database Version: PostgreSQL 12.10 on x86\_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit [user@hostname~]$ **kubectl exec awx-7d5bd6b6d-pz9bd -c awx-task -n ansible-awx _awx-manage showmigrations_** kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] – [COMMAND] instead. auth 0001\_initial 0002\_alter\_permission\_name\_max\_length 0003\_alter\_user\_email\_max\_length 0004\_alter\_user\_username\_opts 0005\_alter\_user\_last\_login\_null 0006\_require\_contenttypes\_0002 0007\_alter\_validators\_add\_error\_messages 0008\_alter\_user\_username\_max\_length 0009\_alter\_user\_last\_name\_max\_length 0010\_alter\_group\_name\_max\_length 0011\_update\_proxy\_permissions 0012\_alter\_user\_first\_name\_max\_length conf 0001\_initial 0002\_v310\_copy\_tower\_settings 0003\_v310\_JSONField\_changes 0004\_v320\_reencrypt 0005\_v330\_rename\_two\_session\_settings 0006\_v331\_ldap\_group\_type 0007\_v380\_rename\_more\_settings 0008\_subscriptions 0009\_rename\_proot\_settings contenttypes 0001\_initial 0002\_remove\_content\_type\_name main 0001\_initial 0002\_squashed\_v300\_release (18 squashed migrations) 0003\_squashed\_v300\_v303\_updates (9 squashed migrations) 0004\_squashed\_v310\_release (6 squashed migrations) 0005\_squashed\_v310\_v313\_updates (3 squashed migrations) 0006\_v320\_release 0007\_v320\_data\_migrations 0008\_v320\_drop\_v1\_credential\_fields 0009\_v322\_add\_setting\_field\_for\_activity\_stream 0010\_v322\_add\_ovirt4\_tower\_inventory 0011\_v322\_encrypt\_survey\_passwords 0012\_v322\_update\_cred\_types 0013\_v330\_multi\_credential 0014\_v330\_saved\_launchtime\_configs 0015\_v330\_blank\_start\_args 0016\_v330\_non\_blank\_workflow 0017\_v330\_move\_deprecated\_stdout 0018\_v330\_add\_additional\_stdout\_events 0019\_v330\_custom\_virtualenv 0020\_v330\_instancegroup\_policies 0021\_v330\_declare\_new\_rbac\_roles 0022\_v330\_create\_new\_rbac\_roles 0023\_v330\_inventory\_multicred 0024\_v330\_create\_user\_session\_membership 0025\_v330\_add\_oauth\_activity\_stream\_registrar 0026\_v330\_delete\_authtoken 0027\_v330\_emitted\_events 0028\_v330\_add\_tower\_verify 0030\_v330\_modify\_application 0031\_v330\_encrypt\_oauth2\_secret 0032\_v330\_polymorphic\_delete 0033\_v330\_oauth\_help\_text 0034\_v330\_delete\_user\_role 0035\_v330\_more\_oauth2\_help\_text 0036\_v330\_credtype\_remove\_become\_methods 0037\_v330\_remove\_legacy\_fact\_cleanup 0038\_v330\_add\_deleted\_activitystream\_actor 0039\_v330\_custom\_venv\_help\_text 0040\_v330\_unifiedjob\_controller\_node 0041\_v330\_update\_oauth\_refreshtoken 0042\_v330\_org\_member\_role\_deparent 0043\_v330\_oauth2accesstoken\_modified 0044\_v330\_add\_inventory\_update\_inventory 0045\_v330\_instance\_managed\_by\_policy 0046\_v330\_remove\_client\_credentials\_grant 0047\_v330\_activitystream\_instance 0048\_v330\_django\_created\_modified\_by\_model\_name 0049\_v330\_validate\_instance\_capacity\_adjustment 0050\_v340\_drop\_celery\_tables 0051\_v340\_job\_slicing 0052\_v340\_remove\_project\_scm\_delete\_on\_next\_update 0053\_v340\_workflow\_inventory 0054\_v340\_workflow\_convergence 0055\_v340\_add\_grafana\_notification 0056\_v350\_custom\_venv\_history 0057\_v350\_remove\_become\_method\_type 0058\_v350\_remove\_limit\_limit 0059\_v350\_remove\_adhoc\_limit 0060\_v350\_update\_schedule\_uniqueness\_constraint 0061\_v350\_track\_native\_credentialtype\_source 0062\_v350\_new\_playbook\_stats 0063\_v350\_org\_host\_limits 0064\_v350\_analytics\_state 0065\_v350\_index\_job\_status 0066\_v350\_inventorysource\_custom\_virtualenv 0067\_v350\_credential\_plugins 0068\_v350\_index\_event\_created 0069\_v350\_generate\_unique\_install\_uuid 0070\_v350\_gce\_instance\_id 0071\_v350\_remove\_system\_tracking 0072\_v350\_deprecate\_fields 0073\_v360\_create\_instance\_group\_m2m 0074\_v360\_migrate\_instance\_group\_relations 0075\_v360\_remove\_old\_instance\_group\_relations 0076\_v360\_add\_new\_instance\_group\_relations 0077\_v360\_add\_default\_orderings 0078\_v360\_clear\_sessions\_tokens\_jt 0079\_v360\_rm\_implicit\_oauth2\_apps 0080\_v360\_replace\_job\_origin 0081\_v360\_notify\_on\_start 0082\_v360\_webhook\_http\_method 0083\_v360\_job\_branch\_override 0084\_v360\_token\_description 0085\_v360\_add\_notificationtemplate\_messages 0086\_v360\_workflow\_approval 0087\_v360\_update\_credential\_injector\_help\_text 0088\_v360\_dashboard\_optimizations 0089\_v360\_new\_job\_event\_types 0090\_v360\_WFJT\_prompts 0091\_v360\_approval\_node\_notifications 0092\_v360\_webhook\_mixin 0093\_v360\_personal\_access\_tokens 0094\_v360\_webhook\_mixin2 0095\_v360\_increase\_instance\_version\_length 0096\_v360\_container\_groups 0097\_v360\_workflowapproval\_approved\_or\_denied\_by 0098\_v360\_rename\_cyberark\_aim\_credential\_type 0099\_v361\_license\_cleanup 0100\_v370\_projectupdate\_job\_tags 0101\_v370\_generate\_new\_uuids\_for\_iso\_nodes 0102\_v370\_unifiedjob\_canceled 0103\_v370\_remove\_computed\_fields 0104\_v370\_cleanup\_old\_scan\_jts 0105\_v370\_remove\_jobevent\_parent\_and\_hosts 0106\_v370\_remove\_inventory\_groups\_with\_active\_failures 0107\_v370\_workflow\_convergence\_api\_toggle 0108\_v370\_unifiedjob\_dependencies\_processed 0109\_v370\_job\_template\_organization\_field 0110\_v370\_instance\_ip\_address 0111\_v370\_delete\_channelgroup 0112\_v370\_workflow\_node\_identifier 0113\_v370\_event\_bigint 0114\_v370\_remove\_deprecated\_manual\_inventory\_sources 0115\_v370\_schedule\_set\_null 0116\_v400\_remove\_hipchat\_notifications 0117\_v400\_remove\_cloudforms\_inventory 0118\_add\_remote\_archive\_scm\_type 0119\_inventory\_plugins 0120\_galaxy\_credentials 0121\_delete\_toweranalyticsstate 0122\_really\_remove\_cloudforms\_inventory 0123\_drop\_hg\_support 0124\_execution\_environments 0125\_more\_ee\_modeling\_changes 0126\_executionenvironment\_container\_options 0127\_reset\_pod\_spec\_override 0128\_organiaztion\_read\_roles\_ee\_admin 0129\_unifiedjob\_installed\_collections 0130\_ee\_polymorphic\_set\_null 0131\_undo\_org\_polymorphic\_ee 0132\_instancegroup\_is\_container\_group 0133\_centrify\_vault\_credtype 0134\_unifiedjob\_ansible\_version 0135\_schedule\_sort\_fallback\_to\_id 0136\_scm\_track\_submodules 0137\_custom\_inventory\_scripts\_removal\_data 0138\_custom\_inventory\_scripts\_removal 0139\_isolated\_removal 0140\_rename 0141\_remove\_isolated\_instances 0142\_update\_ee\_image\_field\_description 0143\_hostmetric 0144\_event\_partitions 0145\_deregister\_managed\_ee\_objs 0146\_add\_insights\_inventory 0147\_validate\_ee\_image\_field 0148\_unifiedjob\_receptor\_unit\_id 0149\_remove\_inventory\_insights\_credential 0150\_rename\_inv\_sources\_inv\_updates 0151\_rename\_managed\_by\_tower 0152\_instance\_node\_type 0153\_instance\_last\_seen 0154\_set\_default\_uuid 0155\_improved\_health\_check 0156\_capture\_mesh\_topology 0157\_inventory\_labels 0158\_make\_instance\_cpu\_decimal 0159\_deprecate\_inventory\_source\_UoPU\_field oauth2\_provider 0001\_initial 0002\_auto\_20190406\_1805 0003\_auto\_20201211\_1314 sessions 0001\_initial sites 0001\_initial 0002\_alter\_domain\_unique social\_django 0001\_initial (2 squashed migrations) 0002\_add\_related\_name (2 squashed migrations) 0003\_alter\_email\_max\_length (2 squashed migrations) 0004\_auto\_20160423\_0400 (2 squashed migrations) 0005\_auto\_20160727\_2333 (1 squashed migrations) 0006\_partial 0007\_code\_timestamp 0008\_partial\_timestamp 0009\_auto\_20191118\_0520 0010\_uid\_db\_index sso 0001\_initial 0002\_expand\_provider\_options taggit 0001\_initial 0002\_auto\_20150616\_2121 0003\_taggeditem\_add\_unique\_index 0004\_alter\_taggeditem\_content\_type\_alter\_taggeditem\_tag ---
**Author:** ![Kaushik\_R](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@Kaushik\_R](https://forum.ansible.com/u/Kaushik_R)\ **Post date:** [July 29, 2022, 5:49pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/19 "2022-07-29T17:49:32Z")
I get the below error when trying to access AWX UI - “The connection for this site is not secure” ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [August 1, 2022, 12:48pm UTC](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763/20 "2022-08-01T12:48:39Z")
That is a basic SSL security issue. Did you specify a cert during the installation? if not a self signed cert would have been generated and applied to the server. Most browsers have a way to accept a self signed cert. You should also be able to get a signed cert and tell the operator to install that cert see [https://github.com/ansible/awx-operator#ingress-type](https://github.com/ansible/awx-operator#ingress-type) - The AWX Team [Next page](https://forum.ansible.com/t/unable-to-launch-awx-ui-using-load-balancer/36763.md?page=2)