You have a USB astro camera which uses indi drivers.

Yes

For the $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR errors, you probably just need to reboot.

That's a question for Aaron Morris. You wont be able to start anything if the compilation failed.
Use an official pi power supply or get a better usb power supply/cable.

For the pyindi-client compile failure, ensure that INDI 1.9.7 is selected if you are using the Astroberry repos. You can manually rebuild pyindi-client using ./misc/rebuild_pyindi-client.sh

Hello Aaron
so I did what you said,
But I still have the following error

meteo@raspberrypi:~ $ systemctl --user start indiserver
Failed to start indiserver.service: Unit indiserver.service not found.
meteo@raspberrypi:~ $

what should I do

Chris

The other error is now gone, so that is good.

The setup.sh script has not yet completed, re-run that script again until it fully completes.

I have a question
what do you answer to the question during the installation and what is the purpose of the "user", "password", "full name" and "email"

Chris

Authentication used to be a simple .htaccess type authentication handled by the web server, but I recently added authentication directly in the indi-allsky web application.

The full name and email do not really matter at the moment, only the username and password are critical.

Ultimately, I am trying to make the web interface fully hardened so that it can be Internet facing.

Hi
so I think it's installed, but how do I check because I can't launch the web page.
How do you do it?

Regards
chris

Find out what the IP address of you pi is (look in your router or set a static one if you know how), then https to it.
eg My pik is at 192.168.1.55 (I put " to stop indi forum mangling web address.
"https://192.168.1.55/indi-allsky/"
Ignore any warning about unsafe (you are not connected to your bank !!). If using chrome browser "proceed to unsafe" and you should
get the login page. Use the username and password you set. It probably wont ask you next time.
Nick

after running indi-allsky successfully for a long time using the old camera stack and indi driver, I decided to migrate to libcamera and the native picamera support. I started with a fresh install of Raspbian Pi OS 11 (64bit) bullseye on my RPi 4 (4GB). Building indi with the supplied script worked without a problem. Setup.sh also run without a problem. But at the end, I did not get a picture. Looking into the log I noticed that rawpy was not available. Switching manually into the venv indi-allsky and running pip install rawpy again did not work. I had to manually install rawpy using:After restarting indi-allsky, it is running well now.

CS, Markus

one motivation for the change was my hope to get rid of the greenish tint. Even using SNCR Maximum Neutral and Auto White Balance, it is still visible and Red/Blue is not brilliant. Using qcam, the pictures look perfectly balanced. qcam is open source, shouldn't it be possible to learn the trick and get similar results?

CS, Markus