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

834 views
Skip to first unread message

Siva S

unread,
Apr 22, 2021, 6:42:42 AM4/22/21
to AWX Project
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.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

Siva S

unread,
Apr 27, 2021, 4:55:07 AM4/27/21
to AWX Project
Team please assist here


Thanks

Siva S

unread,
May 6, 2021, 5:03:44 AM5/6/21
to AWX Project
any help?

The Vandyy Vines

unread,
May 6, 2021, 6:04:36 AM5/6/21
to Siva S, AWX Project
Can you telnet the port on the local server so as the port might be blocked.. 
Also can curl the address on local server

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/1ce3f36a-0e13-4c85-bc64-1845789c2b6cn%40googlegroups.com.

Ted Killmeyer

unread,
May 6, 2021, 8:11:31 AM5/6/21
to The Vandyy Vines, Siva S, AWX Project

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

Siva S

unread,
May 6, 2021, 9:50:14 AM5/6/21
to AWX Project
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: fsev...@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsev...@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsev...@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsev...@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsev...@1.2.13 (node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsev...@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsev...@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsev...@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_...@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_...@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:


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'


Siva S

unread,
May 6, 2021, 10:11:12 AM5/6/21
to AWX Project
could you please assist?

Siva S

unread,
May 7, 2021, 2:42:01 AM5/7/21
to AWX Project
team any assistance?

Siva S

unread,
May 7, 2021, 11:46:45 AM5/7/21
to AWX Project
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'

Bill Nottingham

unread,
May 7, 2021, 12:56:49 PM5/7/21
to Siva S, AWX Project
Siva S (writet...@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

Siva S

unread,
May 11, 2021, 2:53:15 AM5/11/21
to AWX Project
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.

Jens Heinitz

unread,
Jun 3, 2021, 11:52:32 AM6/3/21
to AWX Project
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://<your ip>:8013

HTTPS through port 8043:
https://<your ip>: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

Władysław Borysow

unread,
Jun 17, 2021, 3:25:50 AM6/17/21
to AWX Project
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   "/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!

ProstoNikita

unread,
Jul 13, 2021, 8:18:38 AM7/13/21
to AWX Project
Hello, I've got the same problem. Every time, when I'm trying open UI, I get certificate error: 
111.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 napsal:

Kaleb S

unread,
Jul 27, 2021, 8:34:50 PM7/27/21
to ProstoNikita, AWX Project
Unless you installed a valid certificate trying to use curl will fail unless you add the -k flag. 
curl -kv https://localhost:8043 should work better if your container is running and accessible. 


--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages