Mender-connect is unable to connect to mender-server

General Discussions
,
21

Hi @peter ,

As requested I disabled IPv6 as you can see in the traefik ports logging below:

CONTAINER ID   IMAGE                                                COMMAND                  CREATED          STATUS                    PORTS                          NAMES
68056ddcbdac   mendersoftware/deployments:mender-3.0.1              "/entrypoint.sh --co…"   22 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-deployments_1
625f9173a903   traefik:v2.4                                         "/entrypoint.sh --ac…"   23 minutes ago   Up 18 minutes             80/tcp, 0.0.0.0:443->443/tcp   menderproduction_mender-api-gateway_1
4770323ed55a   mendersoftware/deviceauth:mender-3.0.1               "/usr/bin/deviceauth…"   23 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-device-auth_1
8632752aea05   mendersoftware/deviceconnect:mender-3.0.1            "/usr/bin/deviceconn…"   23 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-deviceconnect_1
940c5f0e7e4b   mendersoftware/workflows-worker:mender-3.0.1         "/usr/bin/workflows …"   23 minutes ago   Up 18 minutes                                            menderproduction_mender-workflows-worker_1
92027f16fe9c   mendersoftware/inventory:mender-3.0.1                "/usr/bin/inventory …"   23 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-inventory_1
a0a874a9a1e7   mendersoftware/useradm:mender-3.0.1                  "/usr/bin/useradm --…"   23 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-useradm_1
00a43fbaeb28   mendersoftware/deviceconfig:mender-3.0.1             "/usr/bin/deviceconf…"   23 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-deviceconfig_1
fc476030bba7   mendersoftware/workflows:mender-3.0.1                "/usr/bin/workflows …"   23 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-workflows-server_1
2d795dc5db98   mendersoftware/create-artifact-worker:mender-3.0.1   "/usr/bin/workflows …"   23 minutes ago   Up 18 minutes             8080/tcp                       menderproduction_mender-create-artifact-worker_1
61121baae6cc   mongo:4.4                                            "docker-entrypoint.s…"   23 minutes ago   Up 18 minutes             27017/tcp                      menderproduction_mender-mongo_1
5a0d89367cba   nats:2.1.9-alpine3.12                                "docker-entrypoint.s…"   23 minutes ago   Up 18 minutes             4222/tcp, 6222/tcp, 8222/tcp   menderproduction_mender-nats_1
9484948db9d2   mendersoftware/gui:mender-3.0.1                      "/entrypoint.sh nginx"   23 minutes ago   Up 18 minutes (healthy)   80/tcp, 8080/tcp               menderproduction_mender-gui_1
af2b95efa9b8   minio/minio:RELEASE.2019-04-23T23-50-36Z             "/usr/bin/docker-ent…"   23 minutes ago   Up 18 minutes (healthy)   9000/tcp                       menderproduction_minio_1

Unfortunately mender-connect is still not working.

FYI, in front of our server we are running Akamai (WAF) and a reverse proxy. Do we need to configure something special for mender-connect? Or can it use exactly the same config as used for mender-client?

Again thanks for all the support.

22

Hey Dave!

that changes the situation. you have to allow the upgrade to websocket (Enable WebSockets for an EAA application) (I am not sure if that is what you use). What you have to do is similar to the configuration you have to do on, e.g.: nginx: Using NGINX as a WebSocket Proxy

peter

23

Hi @peter

I checked with our IT department and apparently our reverse proxy is not configured to support web sockets. This explains a lot. In case there is an update I will inform you. Thanks for all the support until now.

24

ok great! thanks!

peter

25

Hello,
Just got the same error and thanks to you for the solution.
I was using reverse proxy but websocket support was disabled, that’s now updated and connection is working properly.
Cheers,
Joel

1 Like