Hi everyone,
First, thanks to the whole Mender team for a great product! I am currently evaluating it but from what I see in terms of ease of use, code repositories and documentation, Mender is very pleasing to work with. Great job 
!
I am writing because I am attempting to deploy the demo server. It comes up but I cannot login: the screen stays on the login page and the debugger shows me one of the XHR failed with a 400/Bad Gateway error at the openresty level:
This is the 2.3.0 integration tag, as described by the docs but I get the same behavior when I pick up the integration repo HEAD (which I have at 196d744bab2c52e23926506171ef6a3c1151cdae).
I am running inside an Ubuntu bionic VM managed using Vagrant (VirtualBox provider) to match the suggested OS version. I have Docker version 19.03.9, build 9d988398e7 and docker-compose version 1.25.5, build 8a1c60f6.
All containers appear to look fine:
vagrant@ubuntu-bionic:~/integration-2.3.0$ ./demo ps
Name Command State Ports
----------------------------------------------------------------------------------------------------------------------
integration230_mender-api-gateway_1 /entrypoint.sh Up 0.0.0.0:443->443/tcp, 80/tcp
integration230_mender-conductor_1 /srv/start_conductor.sh Up (healthy) 0.0.0.0:8080->8080/tcp, 8090/tcp
integration230_mender-create- /usr/bin/workflows --confi ... Up 8080/tcp
artifact-worker_1
integration230_mender-deployments_1 /entrypoint.sh --config /e ... Up 8080/tcp
integration230_mender-device-auth_1 /usr/bin/deviceauth --conf ... Up 8080/tcp
integration230_mender- /usr/local/bin/docker-entr ... Up 9200/tcp, 9300/tcp
elasticsearch_1
integration230_mender-gui_1 /entrypoint.sh nginx Up 80/tcp
integration230_mender-inventory_1 /usr/bin/inventory --confi ... Up 8080/tcp
integration230_mender-mongo_1 docker-entrypoint.sh mongod Up 27017/tcp
integration230_mender-redis_1 /redis/entrypoint.sh Up 6379/tcp
integration230_mender-useradm_1 /usr/bin/useradm --config ... Up 8080/tcp
integration230_mender-workflows- /usr/bin/workflows --confi ... Up 8080/tcp
server_1
integration230_minio_1 /usr/bin/docker-entrypoint ... Up (healthy) 9000/tcp
integration230_storage-proxy_1 /usr/local/openresty/bin/o ... Up 0.0.0.0:9000->9000/tcp
I have the required entries in /etc/hosts:
vagrant@ubuntu-bionic:~/integration-2.3.0$ cat /etc/hosts
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.1.1 ubuntu-bionic ubuntu-bionic
127.0.0.1 s3.docker.mender.io
127.0.0.1 docker.mender.io
And I don’t see any error messages when everything comes up:
vagrant@ubuntu-bionic:~/integration-2.3.0$ ./demo up
Starting the Mender demo environment...
Creating network "integration230_mender" with the default driver
Creating integration230_mender-redis_1 ... done
Creating integration230_mender-gui_1 ... done
Creating integration230_mender-elasticsearch_1 ... done
Creating integration230_mender-mongo_1 ... done
Creating integration230_minio_1 ... done
Creating integration230_mender-workflows-server_1 ... done
Creating integration230_mender-useradm_1 ... done
Creating integration230_mender-create-artifact-worker_1 ... done
Creating integration230_mender-inventory_1 ... done
Creating integration230_mender-conductor_1 ... done
Creating integration230_mender-device-auth_1 ... done
Creating integration230_storage-proxy_1 ... done
Creating integration230_mender-deployments_1 ... done
Creating integration230_mender-api-gateway_1 ... done
Creating a new user...
****************************************
Username: mender-demo@example.com
Login password: <redacted>
****************************************
Please keep the password available, it will not be cached by the login script.
Mender demo server ready and running in the background. Copy credentials above and log in at https://localhost
Press Enter to show the logs.
Press Ctrl-C to stop the backend and quit.
I can provide more logs on request (I have the full output of ./demo logs but this is hits the body limit of 32k characters).
I have looked on the forum for help, esp. on this thread but nothing matched my issue. In particular, I can run openresty fine manually and I don’t see any 132 error code.
One thing which might be worth mentioning: I am redirecting port 443 in the VM to 4343 on the host. This means that when I reach https://localhost:4343, I first get an error as I am redirected to https://localhost/ui/login. I have to manually edit my URL to be https://localhost:4343/ui/#/login to reach the login page (and, subsequently, the Bad Request error).
Would someone know what is causing this error? I can provide more information if needed.
Thanks much for your time!
Edit: added missing screen captures
