Username:password WaziCloud Website

Hi, I finally installed wazicloud on a computer. Primarily two things are to ask:

  • When I try to connect via a remote host, the redirection to the authentication page fails, because the redirected address is localhost:8080 instead of waziupcloudhostname:3000.

  • I do not find the default credentials for the dashboard. What are they?

There are some remarks to the full installation process that may help other users. I add them below:
==== Install WaziCloud ====

=== Prerequisites ===

  • Server with sudo user (I use a debian buster linux)
  • Internet connection
  • git installed $ sudo apt update
    $ sudo apt upgrade
    $ sudo apt install git

=== Installation ===

I am following the official installation description by Waziup at [[https://github.com/Waziup/WaziCloud/blob/master/README.md]].

  • Update os (in my case:)$ sudo apt update
    $ sudo apt upgrade
  • Install docker-compose $ sudo apt install docker-compose
  • Add user to docker group $ sudo usermod -aG docker $USER
    $ logout

Login

  • Clone WaziupCloud $ git clone https://github.com/Waziup/Platform
  • Change to Platform directory$ cd Platform
  • Change user rights on data/* $ sudo chmod 777 data/* -R
  • Run docker-compose pull (this lasts a longer time)$ docker-compose pullThe following modules are downloaded:
    • mongo (a nosql database)
    • orion (?)
    • mqtt (an mqtt broker like mosquito)
    • mysql (sql database)
    • keycloak (?)
    • waziup-api (rest-api for waziup)
    • dashboard (the dashboard of the waziup-cloud)
  • The first time run docker-compose once like docker-compose -f docker-compose.yml -f docker-compose-first-run.yml up
  • Afterwards run it like docker-compose up
  • In a browser go to the WaziCloud site ‘‘http://<ip_address>:3000]]’’
1 Like

Hi @christian, very happy to hear that!

To access from a remote host, you need to change the various environment variable in the docker-compose.yml file:


Change all mentions of “localhost” to “waziupcloudhostname”.

There is no default credentials for the dashboard. You need to create a new user:

You should try also to connect to Keycloak for administration of users: http://localhost:8080/auth
login/password is admin/admin.
You can create users manually in Keycloak.

Thanks a lot for the notes on the README file! That’s very useful. I will integrate them in the file.

Hi cdupont1,
Thank you for your help. I do not manage to get the right site. May you help me by picking in the docker-compose.yml the places where I have to change the urls:

version: ‘3’

services:

Broker

mongo:
image: mongo:3.4
hostname: mongo
ports:
- “27017:27017”
volumes:
- ./data/mongo:/data/db
healthcheck:
test: echo ‘db.stats().ok’ | mongo localhost:27017/local --quiet
interval: 5s
timeout: 5s
retries: 12
command: mongod

orion:
image: fiware/orion:2.2.0
hostname: orion
ports:
- “1026:1026”
entrypoint: [“sh”, “-c”, “rm /tmp/contextBroker.pid; /usr/bin/contextBroker -fg -multiservice -dbhost mongo -logLevel DEBUG”]
restart: always
depends_on:
- “mongo”

waziup-api:
build: ./waziup-api
image: waziup/waziup-api
ports:
- “800:800”
- “3883:3883”
environment:
- HTTP_PORT=800
- MQTT_PORT=3883
- HTTP_URL=http://waziup-cloud:800
- KEYCLOAK_URL=http://waziup-cloud:8080/auth
- ORION_URL=http://orion:1026
- MONGODB_URL=mongo
- LOG_LEVEL=debug
- MOSQ_URL=mqtt
- MOSQ_PORT=6883
- TWITTER_CONSUMER_KEY=$TWITTER_CONSUMER_KEY
- TWITTER_CONSUMER_SECRET=$TWITTER_CONSUMER_SECRET
- TWITTER_ACCESS_TOKEN=$TWITTER_ACCESS_TOKEN
- TWITTER_ACCESS_TOKEN_SECRET=$TWITTER_ACCESS_TOKEN_SECRET
- PLIVO_ID=$PLIVO_ID
- PLIVO_TOKEN=$PLIVO_TOKEN
network_mode: host
restart: always
extra_hosts:
- “orion:127.0.0.1”
- “mongo:127.0.0.1”
- “mqtt:127.0.0.1”
depends_on:
- orion
- keycloak
- mongo
- mqtt

mqtt:
image: eclipse-mosquitto
ports:
- “6883:6883”
entrypoint: “/usr/sbin/mosquitto -p 6883”

Users identification & authorization

keycloak:
build: ./keycloak
image: waziup/keycloak
ports:
- “8080:8080”
environment:
- DB_VENDOR=mysql
- KEYCLOAK_USER=admin
- KEYCLOAK_PASSWORD=${WAZIUP_ADMIN_PASS}
- KEYCLOAK_LOGLEVEL=DEBUG
- MYSQL_PORT_3306_TCP_ADDR=mysql
- MYSQL_PORT_3306_TCP_PORT=3306
volumes:
- ./data/keycloak:/opt/jboss/keycloak/standalone/data/
# If the realm “waziup” doesn’t exists, create it from file
#entrypoint: “/opt/jboss/tools/docker-entrypoint.sh -b 0.0.0.0 -Dkeycloak.migration.action=import -Dkeycloak.migration.provider=dir -Dkeycloak.migration.strategy=IGNORE_EXISTING -Dkeycloak.migration.dir=/opt/jboss/keycloak/imports”
depends_on:
- mysql

mysql:
image: mysql:5.7
hostname: mysql
#ports:
# - “3306:3306”
volumes:
- ./data/mysql:/var/lib/mysql/
environment:
- MYSQL_DATABASE=keycloak
- MYSQL_USER=keycloak
- MYSQL_PASSWORD=password
- MYSQL_ROOT_PASSWORD=root_password

Dashboard

dashboard:
# Specific images should be built for each environment (local, staging, production).
image: waziup/dashboard:2.0-localhost
build:
context: ./dashboard
args:
- SERVER_PORT=3000
- SERVER_URL=http://waziup-cloud:3000
- KEYCLOAK_URL=http://waziup-cloud:8080/auth
- API_SERVER_URL=http://waziup-cloud:800/api
ports:
- “3000:3000”

Thank you!
Christian

Hi,
I still have problems to login into the locally installed waziup-cloud. I first call http://ip-address:3000.
I am then redirected to http://localhost:8080/auth/realms/waziup/protocol/openid-connect/auth?client_id=dashboard&redirect_uri=http%3A%2F%2F192.168.1.37%3A3000%2F&state=261007ca-0b2f-4c7c-8cdf-85c358b0d29e&response_mode=fragment&response_type=code&scope=openid&nonce=34a7e826-1764-4fc1-ad44-d3888e0a07ca
I then have to replace localhost with the hosts ip-address in the address line of the browser. Then I can login. The browser redirects back to port 3000, but the page is empty, having the dark color of waziup.
I replaced any localhost to waziup-cloud (the hostname of the waziup-cloud host) in docker-compose.yml but without luck. Any hints?
Thanks and regards Christian

Hi Christian,

On which computer You installed local version of Waziup Cloud?

I am trying to install it on raspberry Pi 3 , without success.

Regards,

Dejan

Hi Dejan
I have installed it on a Debian buster server running as a virtual box guest. I also tried on raspberry without luck, don’t know why.
Regards Christian

Hi CHristian,

Thanks for Your information. I will try it in virtual box as well.