Cannot get Flow/Windmill working - how to get it up?

[leoniscsem]

I am on the latest AIO version (30.0.5) and made sure AppAPI is configured, also webhook_listener is activated. I have not changed the default settings of the AppAPI (AIO Docker Socket Proxy), and both the deployment test as well as "check connection" show no errors.
The deploy config lists nextcloud-aio for network, daemon hosts shows nextcloud-aio-docker-socket-proxy:2375.

Now, when I install the app it shows up under "Your Apps", clicking on details shows no error. The settings shown also look the same as what is configured in AppAPI:

Deploy Daemon
Type: docker-install
Surname: docker_aio
Display Name: AIO Docker Socket Proxy
GPUs support: false
Compute device: CPU

Yet, there is no button in the Nextcloud UI to access Flow's administrative interface. I tried to check the logs, but I did not see anything unusual.

• Do I need to create a separate deploy daemon in the AppAPI settings?
• How can I debug this?
• Is there a certain procedure I must follow in order to activate that?
• Is there maybe an issue with HTTP/3 being active in NGINX? (I just can guess on that matter, as HTTP/3 still is considered to be rather adventerous - anyone has any experience with this?)
• What are the RAM requirements for Flow/Windmill in the context of AIO?
• We are using the Custom Menu App; has anyone noticed issues with this perhaps? I had deactivated once to see if this was the cause, but as I have tried so many different deployments I really can't tell if I had noticed any errors linked to this.

I am a bit clueless, and since the Flow tool would be essential in our company's operation I am very keen on finding out what is going on.

[leoniscsem]

Okay, I have solved the core issue so far by

1. restarting the container manually after deploying the Windmill/Flow container (sudo docker restart nextcloud-aio-nextcloud)
2. disabling the Custom Menu

I guess there is a compatibility problem with the Custom Menu app. I still have no idea how to debug this.

Edit 2:
I just realised that this is a bug with Custom Menu, not related to AIO.