This page lists common errors and the steps needed to troubleshoot them.

502 Bad Gateway

502 errors indicate that Echo’s user-interface, or other parts, are failing to reach their HTTP(s) destination due to service unavailability or due to a routing related issue.

Routing issue

In cases where services terminate and then restart, they may obtain a new IP address from the Docker engine. This may lead to the previous IP address being cached by the router service and ending with a 502 error, because the router does not point to the newly obtained IP address of the service.

  • SSH into the host running echo-router
  • Execute the following command
$ docker kill -s HUP echo_router_1
  • This command will instruct the router to reload its configuration without causing any service interrpution.
  • Try accessing the service again

Service unavailability

In case the service you tried to access is down, 502 errors may appear. To restart the service, please follow the target component documentation. Here’s an example for restarting the echo-ui service.

  • SSH into the host running echo-ui
  • Execute the following command
$ docker restart echo_ui_1
  • This command will restart the UI service
  • Try accessing the service again

Fork development mode

When running in development mode without the use of Docker, please follow the target component documentation. Here’s an example for restarting the echo-ui service when running in development mode.

  • SSH into the host running echo-ui
  • Execute the following commands
$ cd /opt/joola/echo/src/echo-ui-<NAME-OF-FORK>/
$ pm2 start -x --interpreter sh --name echo run.sh
  • This command will start UI services
  • Try accessing the service again
  • In order to persist reboots and failures, please run the following command and follow its instructions
$ pm2 startup