Absolutely. The easiest way would be either to run
iofog-agent status on the RPI with Agent installed. It will tell you if Connection to Controller is either:
ok, broken certificate(The Agent doesn’t trust it’s controller), and not provisioned if not connected.
If you see either broken certificate or not provisioned, ensure that both iofog-controller is started, the agent is pointed to it
iofog-agent config -a http://<IP-Address of Controller>:<Port Assigned>/api/v3/)
You may also attempt to add a microservice to the agent, through one of our provided interfaces(like REST API, our ProductDemo Previews) or through CLI. If you add this and start the flow, you may run
cat /etc/iofog-agent/microservices.json which will become populated with a Json describing the microservices you have deployed. You can also check /var/log/iofog-agent/iofog-agent.0.log.
If you are unsure of the port when you run
iofog-controller start it Will tell you which port to expect.
[info] Starting iofog-controller...
==> 🌎 Listening on port 54421. Open up http://localhost:54421/ in your browser.
ioFog-Controller has started at pid: 46997
I hope this answered your question, or cleared up some confusion. Please tell me if you’re still confused