Signing up for an admin account fails

[Reino Wallin]

I am settings up a minor cluster to learn about Kubernetes and Elastickube. The master as well as the minions are virtual machines with CentOS 7 running under libvirt. The host is a CentOS 7 box. The installation of Elastickube was successful, and the diagnostic page is properly loaded via an nginx reverse proxy running in another VM. Everything seems to be OK on the diagnostic page. However, when signing up for the admin account I have an issue. It seems the sign up process doesn't finalize properly. I then tried to reset my password on the reset-password page, but I got an error: "mail settings not added".

I have set type: NodePort in my Elastickube service file, and in my Nginx conf, among other lines, I have:

upstream cloud {
    ip_hash;
    server xxx.xxx.xxx.xxx;
    server yyy.yyy.yyy.yyy;
    server zzz.zzz.zzz.zzz;
}
    location / {
        if ($scheme = http) {
            return 301 https://$server_name$request_uri;
        }
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $http_x_forwarded_proto;
        proxy_set_header X-Scheme $scheme;
        proxy_pass http://cloud;
    }

How do I debug things? Any hints are welcome.

[David Navarro Estruch]

@reinow
Most of the communications from the UI to the elastickube service is done via secure websockets.

Is this nginx configuration proxying correctly that communication? You can check from your browser developer tools if the wss connection starts correctly.

If the connection to the websockets is working, the next thing for debugging are the logs on the kubernetes side.
The logs from all the containers of the elastickube-server pod are useful to understand what is happening. If you need some help you can post them here and we will try to help.