ui won't connect

[peterclemenko]

after the recent commits for nginx support, the ui returns connection refused on trying to connect to localhost on 8080

[adpham95]

Are you connecting via https? e.g.: https://localhost:8080

I'll make sure to update the documentation for that.

[peterclemenko]

Yes, I have tried HTTPS with no luck

[peterclemenko]

Update, works on Brave on Windows 10 with a cert error, I was having breakage on Linux, let me test again.

[peterclemenko]

Confirmed, it's broken on my linux laptop but not the windows boot. There are no changes to the files on Linux and other dockerized apps work fine.

[adpham95]

Could you attach the output of docker service logs -f walkoff_nginx after a failed attempt to conenct? I'm wondering if there might be an issue with the volume mounts.

[peterclemenko]

Ok, so it's broken on my windows boot now too. The docker service logs command just blank outputs

[peterclemenko]

Confirmed on a third machine. That's 3 machines where it can't connect to the UI. 2 windows 1 linux. This all started when you guys moved to nginx, maybe there's a missing config in the repo?

[peterclemenko]

So on the 3rd machine I was able to get a output saying that there is no such task or service "walkoff_nginx"

" docker service logs -f walkoff_nginx
no such task or service: walkoff_nginx"

[peterclemenko]

Debugged on desktop. It appears that 8080 was in use on the desktop. Moving to 8081 seemed to work.

walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a |
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | Welcome to the Bitnami nginx container
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-nginx
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-nginx/issues
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | Send us your feedback at [email protected]
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a |
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | INFO ==> ** Starting NGINX setup **
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | INFO ==> Validating settings in NGINX_* env vars...
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | INFO ==> Initializing NGINX...
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | INFO ==> ** NGINX setup finished! **
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a |
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | INFO ==> ** Starting NGINX **
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | 2019/07/14 13:48:10 [warn] 1#0: conflicting server name "" on 0.0.0.0:8080, ignored
walkoff_nginx.1.vmcdq3c9zdce@linuxkit-00155d63f80a | nginx: [warn] conflicting server name "" on 0.0.0.0:8080, ignored

[peterclemenko]

I would suggest moving the port from 8080 as everything seems to use that port

[adpham95]

Ah, that would do it, I should have thought of that earlier as we had a similar issue on another laptop. I'll add that to the checks for the new startup process we're building.

[peterclemenko]

Seems to have broken on reboot. 8081 isn't working anymore. service logs won't show anything

[peterclemenko]

output seems interesting
docker service ls
ID NAME MODE REPLICAS IMAGE PORTS
x9y4kgvxib3l walkoff_api_gateway replicated 1/1 127.0.0.1:5000/api_gateway:latest
fj4sj5xkytjk walkoff_nginx replicated 0/1 bitnami/nginx:latest *:8080-8081->8080-8081/tcp
m1yenhng2kgc walkoff_portainer replicated 1/1 portainer/portainer:latest
z2hnxblh7x87 walkoff_postgres replicated 1/1 postgres:latest
7yzefg610kbv walkoff_registry replicated 0/1 registry:2 *:5000->5000/tcp
rq8t4v6yg6c6 walkoff_umpire replicated 0/1 127.0.0.1:5000/umpire:latest
r1ukxl8rln6w walkoff_walkoff_redis replicated 1/1 redis:latest

[peterclemenko]

Correction, seems to be spotty still.

[peterclemenko]

It seems that sometimes it will spawn the nginx container and make a replica, sometimes it won't.

[peterclemenko]

So the bootloader appears to have fixed this under linux. Windows is still spotty though.

[peterclemenko]

linux is screwed again. Closed the laptop lid and now it times out on trying to connect. here's output

aoighost@nomad:~/walkoff-motoko$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4b06026faf8f portainer/portainer:latest "/portainer" 3 minutes ago Up 2 minutes 9000/tcp walkoff_resource_portainer.1.fko98j4hpmvzjw50ru1mz56i0
c897a4c5d2ee bitnami/nginx:latest "/entrypoint.sh /run…" 6 minutes ago Up 6 minutes 8080/tcp, 8443/tcp walkoff_resource_nginx.1.sifdkhxqttfjx2k0qvjm15a3w
79907d841883 127.0.0.1:5000/api_gateway:latest "/bin/sh -c 'gunicor…" 6 minutes ago Up 6 minutes walkoff_core_api_gateway.1.1x11s9100qijzfduluev878nb
c4726ea51cd4 127.0.0.1:5000/umpire:latest "python -m umpire.um…" 6 minutes ago Up 6 minutes walkoff_core_umpire.1.xy902aqmsdll6jnsroff8j2nw
ee14e0946736 postgres:latest "docker-entrypoint.s…" 12 minutes ago Up 12 minutes 5432/tcp walkoff_resource_postgres.1.j9z9m1y67pr98vgbrncgayicr
1e550d42a950 redis:latest "docker-entrypoint.s…" 12 minutes ago Up 12 minutes 6379/tcp walkoff_resource_redis.1.0ls2i6jjm3e7nvpsu24dqufq3
5d439f526590 minio/minio:latest "/usr/bin/docker-ent…" 13 minutes ago Up 13 minutes (healthy) 9000/tcp walkoff_resource_minio.1.v58wjvn72iq9vtdo2gw2ghcvy
ab42d5a6d566 registry:2 "/entrypoint.sh /etc…" 13 minutes ago Up 13 minutes 5000/tcp walkoff_resource_registry.1.5y3zdna9ov05shhablgy4veas
8d9a9e20e59a registry:2 "/entrypoint.sh /etc…" 3 weeks ago Up 15 minutes 0.0.0.0:5000->5000/tcp walkoff-motoko_registry_1

[peterclemenko]

nevermind about linux. It seems for some reason brave doesn't like it. Firefox works just fine though.

[peterclemenko]

OK it works on Windows now, but only on firefox. Chrome and Brave don't work for some reason

[adpham95]

The last two comments are referring to browsers timing out when connecting? Or UI bugs?

[peterclemenko]

browsers timing out while connecting