The official setup.sh from indi-allsky is functionally comprehensive and installs the entire runtime environment including the web server configuration. This behavior is useful for typical installations, but leads to problems if custom Apache settings are used – especially with Let’s-Encrypt certificates, user-defined VirtualHosts or specific redirect rules.
Practical operation showed that setup.sh regenerates the /etc/apache2/sites-available/indi-allsky.conf file each time it is run. As a result:
- a self-signed SSL certificate is created,
- individual SSL path and server name settings are lost,
- Listener conflicts arise (ports 80/443 are used multiple times),
- the Apache restart fails at the end of the setup process.
*** This post was updated with a new routine on Dezember 12th, 2025. ***
After updating indi-allsky, it often happens that the local self-signed certificate (e.g. allsky.local) is suddenly used again, although a valid Let’s Encrypt certificate was previously set up. I will explain how to do this 
indi-allsky can retrieve weather data such as temperature, humidity or cloud cover directly from the OpenWeather API and integrate it into the image caption. This requires a valid API key and the coordinates of the location. The setup is done in the web interface under Sensors, where OpenWeather is selected as the source and the API key is entered. In addition, the longitude and latitude of the camera’s location must be set under “Location”.
I wanted to add additional information to my all-sky images: Aircraft data directly in the image, including callsign, altitude and direction. Since I didn’t want to run my own ADS-B setup, I used the Open Data API from 