Changing "yadle" account password - effect on microservices

A question that comes up frequently is:

“All of the Yadle services are running, however we are not seeing any thumbnails or tags on indexed files. Why is this?”

The most common reason for this is that the password for the default yadle account was changed after installing the agent and/or server side microservices - depending on if SaaS or Self-Hosted deployment.

The microservices must authenticate with the API server in order to successfully complete POST and PUT API requests for adding thumbnails and tags. When the microservices are installed, you provide the yadle account username and password. If it is changed through the web app, the microservices are not aware of this change.

To update the password for the microservices, you must do the following:

1. Stop agent side microservices.

$ cd /opt/<org>/microservices/agent
$ sudo ./stop_yadle

2. Edit .env file in /opt/<org>/microservices/agent directory. Modify the line YADLE_PASSWORD=<password> with the appropriate value for the yadle account.

3. Stop server side microservices.

$ cd /opt/<org>/microservices/server
$ sudo ./stop_yadle

4. Edit .env file in /opt/<org>/microservices/server directory. Modify the line YADLE_PASSWORD=<password> with the appropriate value for the yadle account.

5. Restart server microservices.

$ cd /opt/<org>/microservices/server
$ sudo ./start_yadle

6. Restart agent microservices.

$ cd /opt/<org>/microservices/agent
$ sudo ./start_yadle
1 Like