# Installed AWX 19 though Docker Compose for Development. but unable to connect AWX GUI

**URL:** <https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [April 22, 2021, 10:42am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036 "2021-04-22T10:42:42Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [April 22, 2021, 10:42am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/1 "2021-04-22T10:42:42Z")

</div>

Dear All,

Installed AWX 19 though Docker Compose for Development. but unable to connect AWX GUI

I have used ports mentioned in the compose file (using http and https)

Could you please assist here

# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
7e031188c1d6 [Quay](http://quay.io/awx/awx_devel:devel) “/entrypoint.sh laun…” 3 hours ago Up 23 minutes 0.0.0.0:6899-\>6899/tcp, :::6899-\>6899/tcp, 0.0.0.0:7899-7999-\>7899-7999/tcp, :::7899-7999-\>7899-7999/tcp, 0.0.0.0:8013-\>8013/tcp, :::8013-\>8013/tcp, 0.0.0.0:8043-\>8043/tcp, :::8043-\>8043/tcp, 0.0.0.0:8080-\>8080/tcp, :::8080-\>8080/tcp, 22/tcp, 0.0.0.0:8888-\>8888/tcp, :::8888-\>8888/tcp tools\_awx\_1  
a625cab19122 postgres:12 “docker-entrypoint.s…” 3 hours ago Up 23 minutes 5432/tcp tools\_postgres\_1  
549bc0bda402 redis:latest “redis-server /usr/l…” 4 hours ago Up 23 minutes 6379/tcp tools\_redis\_1

---

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [April 27, 2021, 8:55am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/2 "2021-04-27T08:55:06Z")

</div>

Team please assist here

Thanks

---

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [May 6, 2021, 9:03am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/3 "2021-05-06T09:03:44Z")

</div>

any help?

---

<div class="post-metadata">

**Author:** ![The\_Vandyy\_Vines](https://avatars.discourse-cdn.com/v4/letter/t/7993a0/32.png) [@The\_Vandyy\_Vines](https://forum.ansible.com/u/The_Vandyy_Vines)\
**Post date:** [May 6, 2021, 10:04am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/4 "2021-05-06T10:04:22Z")

</div>

Can you telnet the port on the local server so as the port might be blocked…  
Also can curl the address on local server

---

<div class="post-metadata">

**Author:** ![Ted\_Killmeyer](https://avatars.discourse-cdn.com/v4/letter/t/85f322/32.png) [@Ted\_Killmeyer](https://forum.ansible.com/u/Ted_Killmeyer)\
**Post date:** [May 6, 2021, 12:11pm UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/5 "2021-05-06T12:11:28Z")

</div>

Nc is a better option to test connectivity, and I have found in 99% of my cases… the firewall (or iptables) was to blame

---

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [May 6, 2021, 1:50pm UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/6 "2021-05-06T13:50:14Z")

</div>

I have already disabled firewall

Clean and Build UI stopped @ make[1]: Leaving directory ‘/awx\_devel’.

[root@awxui ~]# docker exec tools\_awx\_1 make clean-ui ui-devel  
rm -rf node\_modules  
rm -rf awx/ui\_next/node\_modules  
rm -rf awx/ui\_next/build  
rm -rf awx/ui\_next/src/locales/\_build  
rm -rf awx/ui\_next/.ui-built  
npm --prefix awx/ui\_next --loglevel warn --ignore-scripts install  
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node\_modules/webpack-dev-server/node\_modules/fsevents):  
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})  
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node\_modules/watchpack-chokidar2/node\_modules/fsevents):  
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})  
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node\_modules/jest-haste-map/node\_modules/fsevents):  
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})  
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node\_modules/fsevents):  
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

added 2048 packages from 889 contributors and audited 2056 packages in 34.135s

108 packages are looking for funding  
run `npm fund` for details

found 7 vulnerabilities (6 moderate, 1 high)  
run `npm audit fix` to fix them, or `npm audit` for details  
make[1]: Entering directory ‘/awx\_devel’  
npm --prefix awx/ui\_next --loglevel warn run compile-strings

> ui\_next@0.1.0 compile-strings /awx\_devel/awx/ui\_next  
> lingui compile

Compiling message catalogs…  
Done!  
npm --prefix awx/ui\_next --loglevel warn run build

> ui\_next@0.1.0 build /awx\_devel/awx/ui\_next  
> INLINE\_RUNTIME\_CHUNK=false react-scripts build

Creating an optimized production build…  
Compiled successfully.

File sizes after gzip:

593 KB build/static/js/2.9a495b89.chunk.js  
290.08 KB build/static/js/main.3be14996.chunk.js  
61.94 KB build/static/css/2.14fc25a3.chunk.css  
770 B build/static/js/runtime-main.a1234c1a.js

The project was built assuming it is hosted at /.  
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.  
You may serve it with a static server:

npm install -g serve  
serve -s build

Find out more about deployment here:

bit.ly/CRA-deploy

mkdir -p awx/public/static/css  
mkdir -p awx/public/static/js  
mkdir -p awx/public/static/media  
cp -r awx/ui\_next/build/static/css/\* awx/public/static/css  
cp -r awx/ui\_next/build/static/js/\* awx/public/static/js  
cp -r awx/ui\_next/build/static/media/\* awx/public/static/media  
touch awx/ui\_next/.ui-built  
make[1]: Leaving directory ‘/awx\_devel’

---

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [May 6, 2021, 2:11pm UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/7 "2021-05-06T14:11:12Z")

</div>

could you please assist?

---

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [May 7, 2021, 6:42am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/8 "2021-05-07T06:42:01Z")

</div>

team any assistance?

---

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [May 7, 2021, 3:46pm UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/9 "2021-05-07T15:46:45Z")

</div>

could anyone assist why UI stops here?

docker exec tools\_awx\_1 make clean-ui ui-devel

mkdir -p awx/public/static/css  
mkdir -p awx/public/static/js  
mkdir -p awx/public/static/media  
cp -r awx/ui\_next/build/static/css/\* awx/public/static/css  
cp -r awx/ui\_next/build/static/js/\* awx/public/static/js  
cp -r awx/ui\_next/build/static/media/\* awx/public/static/media  
touch awx/ui\_next/.ui-built  
make[1]: Leaving directory ‘/awx\_devel’

---

<div class="post-metadata">

**Author:** ![Bill\_Nottingham1](https://avatars.discourse-cdn.com/v4/letter/b/58f4c7/32.png) [@Bill\_Nottingham1](https://forum.ansible.com/u/Bill_Nottingham1)\
**Post date:** [May 7, 2021, 4:56pm UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/10 "2021-05-07T16:56:41Z")

</div>

Siva S (writetosivas@gmail.com) said:

> could anyone assist why UI stops here?
> 
> docker exec tools\_awx\_1 make clean-ui ui-devel
> 
> mkdir -p awx/public/static/css  
> mkdir -p awx/public/static/js  
> mkdir -p awx/public/static/media  
> cp -r awx/ui\_next/build/static/css/\* awx/public/static/css  
> cp -r awx/ui\_next/build/static/js/\* awx/public/static/js  
> cp -r awx/ui\_next/build/static/media/\* awx/public/static/media  
> touch awx/ui\_next/.ui-built  
> make[1]: Leaving directory '/awx\_devel'

That's normal - the UI is built, and then the build process exits.

The UI is served by the containers run with `make docker-compose`,  
or by the containers when installed in kubernetes.

Bill

---

<div class="post-metadata">

**Author:** ![sivas](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sivas](https://forum.ansible.com/u/sivas)\
**Post date:** [May 11, 2021, 6:53am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/11 "2021-05-11T06:53:15Z")

</div>

Thanks for your response Bill.  
But I’m unable to connect AWX UI through browser

I tried different browser with localhost and external IP. But no hope.

---

<div class="post-metadata">

**Author:** ![Jens\_Heinitz](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@Jens\_Heinitz](https://forum.ansible.com/u/Jens_Heinitz)\
**Post date:** [June 3, 2021, 3:52pm UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/12 "2021-06-03T15:52:32Z")

</div>

Hi,

I just came across this issue. How do you try to access the AWX UI? You need to use either one of the two following URLs:

HTTP through port 8013:  
http://:8013

HTTPS through port 8043:  
https://:8043

Maybe you get a warning that the certificate is invalid when you access the UI through https. You may want to install your own certificate or mount the one from the docker host into your container.

Best regards

Jens

---

<div class="post-metadata">

**Author:** ![Wladyslaw\_Borysow](https://avatars.discourse-cdn.com/v4/letter/w/ea5d25/32.png) [@Wladyslaw\_Borysow](https://forum.ansible.com/u/Wladyslaw_Borysow)\
**Post date:** [June 17, 2021, 7:25am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/13 "2021-06-17T07:25:49Z")

</div>

Hello,  
we have got the same issue:(

Ports 8013 and 8043 were added to firewall exceptions, but are not reachable locally and from other machines:

firewall-cmd --zone=public --add-port=8013/tcp --permanent  
firewall-cmd --reload

auto:~$ sudo docker ps  
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
5ea3e6d3ea50 [quay.io/awx/awx\_devel:HEAD](http://quay.io/awx/awx_devel:HEAD) “/entrypoint.sh laun…” 23 hours ago Up 22 hours 0.0.0.0:6899-\>6899/tcp, :::6899-\>6899/tcp, 0.0.0.0:7899-7999-\>7899-7999/tcp, :::7899-7999-\>7899-7999/tcp, 0.0.0.0:8013-\>8013/tcp, :::8013-\>8013/tcp, 0.0.0.0:8043-\>8043/tcp, :::8043-\>8043/tcp, 0.0.0.0:8080-\>8080/tcp, :::8080-\>8080/tcp, 22/tcp, 0.0.0.0:8888-\>8888/tcp, :::8888-\>8888/tcp tools\_awx\_1  
ab6cd576e3c3 redis:latest “redis-server /usr/l…” 23 hours ago Up 22 hours 6379/tcp tools\_redis\_1  
1932076eab57 postgres:12 “docker-entrypoint.s…” 23 hours ago Up 22 hours 5432/tcp

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![ProstoNikita](https://avatars.discourse-cdn.com/v4/letter/p/dc4da7/32.png) [@ProstoNikita](https://forum.ansible.com/u/ProstoNikita)\
**Post date:** [July 13, 2021, 12:18pm UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/14 "2021-07-13T12:18:38Z")

</div>

Hello, I’ve got the same problem. Every time, when I’m trying open UI, I get certificate error:

 ![111.png](https://us1.discourse-cdn.com/ansible/original/2X/0/01e743524b6ad7463f74e690654e5c994dec9cb3.png)

Ubuntu 20.04, everything is fine except this. Please help!

Dne čtvrtek 17. června 2021 v 9:25:50 UTC+2 uživatel [wladysla...@gmail.com](mailto:wladysla...@gmail.com) napsal:

---

<div class="post-metadata">

**Author:** ![Kaleb\_S](https://avatars.discourse-cdn.com/v4/letter/k/a6a055/32.png) [@Kaleb\_S](https://forum.ansible.com/u/Kaleb_S)\
**Post date:** [July 28, 2021, 12:34am UTC](https://forum.ansible.com/t/installed-awx-19-though-docker-compose-for-development-but-unable-to-connect-awx-gui/35036/15 "2021-07-28T00:34:34Z")

</div>

Unless you installed a valid certificate trying to use curl will fail unless you add the -k flag.  
curl -kv [https://localhost:](https://localhost:8013)8043 should work better if your container is running and accessible.

> **(attachments)**
>
> ![111.png](https://us1.discourse-cdn.com/ansible/original/2X/0/01e743524b6ad7463f74e690654e5c994dec9cb3.png)
