MQTT issue connecting with Android agent

[iorfmer]

After configuring correctly docker container, we have performed correctly:

1. User invitation process
2. Device register process using Android agent app

But after registering device correctly, agent is always in "offline" mode, so can not use defined MDM policies to registered devices. We have discussed it with Android agent team, and it seems it was an issue regarding Android agent and Flyve plugin, already fixed in develop branches in both repositories.

At this moment, we have two thoughts:

• Docker environment maybe needs to include Flyve plugin latest fixes

Or:

• We don't have Mosquitto server configured correctly.

In our logs we see Mosquitto configured correctly, receiving PUBLISH from agent, anyway we have opened Mosquitto ports configured in the Docker .env file.

We saw this Php:

Glpi-PHP | 172.18.0.3 - 12/Nov/2018:11:36:14 +0000 "GET /apirest.php" 200
Glpi-PHP | [12-Nov-2018 11:36:14] WARNING: [pool www] child 18 said into stderr: "There was a problem
sending 178 bytes on socket 6: Broken pipe"

We don't know if it is related to this issue.

Many thanks.

[iorfmer]

Hi,
Sorry to answer, but is it possible to know a bug fix release date?
Many thanks.

[DIOHz0r]

Hello,

This docker project is for development uses no for real production environments. When the docker is built the PHP-GLPI container gets the latest version of the development version of FlyveMDM plugin, so it could be normal to get some bugs once in a while because it has different features and fixes from the official release. If you want to update the plugin to the latest version, you would have to pull the changes via "git pull" command in the PHP-GLPI container

The MQTT service is built in a different container with its defaults values (no TLS/SSL security). When the agent gets offline and it can't get back to an online status means that there is a connection problem with the MQTT server and the device.

The error on the log is not quite informative to know what is the problem, but I think that it could be a problem connecting with the broker that will be investigated or with a mail server which it's not included in the docker compose for security reasons.

[iorfmer]

Thanks for your feedback. Appreciate it.