app_api tries to connect ExApps via localhost about app_api HOT 6 CLOSED

Unfortunately this type of installation is supported either with the workaround that you described, or you will have to use HTTPS and in that case HaProxy(nextcloud-appapi-dsp) will forward requests to LXD localhost and ExApp will listen to that interface(LXD localhost)

Another solution will be to create docker bridge network and make containers in it visible by DNS names from LXC container

from app_api.

Can you describe your setup config a little bit more? Cause it should connect to localhost by design in some situations

Are you using VPN?

from app_api.

Nextcloud is running inside a LXC container with with Apache on Debian 12.
Docker is running on the LXD host on Debian 12 (amd64).

from app_api.

OK, thanks. Sounds both like a useful solution, I will try this on a second system that is setup the same way.
On my current setup I will keep the WA until the other one is working.

from app_api.

Oh... well in the meantime I managed to create a huge mess on my system...

I ran:

occ app_api:app:register context_chat_backend manual_install --json-info \
"{\"appid\":\"context_chat_backend\",\"name\":\"Context Chat Backend\",\"daemon_config_name\":\"docker_install\",\"version\":\"2.0.1\",\"secret\":\"12345\",\"port\":10034,\"scopes\":[],\"system_app\":0}" \
--force-scopes --wait-finish

In my wisdom... I though it would help to rename manual_install to docker_install.

And now I can't unregister it anymore... Even deleting App Api and reinstalling it doesn't help.

I'm currently at work, so I can't access the system to show the stacktrace, but on the top of your head... is there anything I can do to at least fix the registered value docker_install so I can unregister it again?

from app_api.

no, worry.
you can always just manually remove containers and clean oc_ex_apps/oc_ex_apps_daemons table(after cleaning tables reset Redis cache if you have one)

or you can use occ app_api:app:unregister "appid" --force

from app_api.