In addition to my original question of why starting the Web Manager fails the first time, could someone please explain why the Web Manager is needed? If I change my profile to not use the web server, Ekos always fails to connect to the INDI server on my remote Rpi4.

The docs say this:

INDI Web Manager is a simple Web Application to manage INDI server. It supports multiple driver profiles along with optional custom remote drivers. It can be used to start INDI server locally, and also to connect or chain to remote INDI servers. It is especially useful to install on remote Raspberry PIs installations where you can easily startup INDI server without needing to SSH into the device. Furthermore, the Web Manager provides a RESTful API where you can issue simple calls to start and stop INDI services over the network.

This implies the Web Manger needs to be used to start the INDI server on the remote device. Isn't there some way to have the INDI server automatically startup when the RPi boots? That would eliminate the need for it in most cases.

Read More...