My AppAPI deploy daemon connects but doesnt work beyond that

ℹ️ Support
, ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 30.0.5
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu 22.04
  • Web server and version (e.g, Apache 2.4.25):
    • Apache 2.4.29
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • 8.3.14
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • today
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • snap
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

I’m trying to setup a deploy daemon so I can install context chat backend. I installed docker, ran this command to setup a docker socket proxy container:

docker run -e NC_HAPROXY_PASSWORD=“some_secure_password”
-v /var/run/docker.sock:/var/run/docker.sock
–name nextcloud-appapi-dsp -h nextcloud-appapi-dsp
–restart unless-stopped --privileged -d Package nextcloud-appapi-dsp · GitHub

Then in AppAPI’s register daemon box chose docker socket proxy and left all settings as they appear except I changed the HaProxy password to the one I set and changed Daemon host to IP:2375 based off the settings I saw when I inspected the container. This allows the daemon to connect successfully but the test deploy completely fails and says “ExApp failed to register, check the NC logs” there is nothing related in the logs.It’s entirely possible I’m doing something stupid, if there’s an obvious step I didn’t mention, please don’t assume I’m aware of it.

Thank you.

2

@two welcome to the community

please be clear, you’ve installed a reverse proxy (HAProxy via Docker) on the same host running Nextcloud snap?

have you correctly configured the Nextcloud snap ports see HTTP/HTTPS port configuration ?
also see Reverse proxy configuration

3

nextcloud runs as a snap on the same host i have docker installed on and created the reverse proxy container on using the command in my original post from the Nextcloud AppAPI Docker Socket Proxy github. nextcloud can connect to the daemon i created but cant do anything more, i made sure www-data has access to docker.sock, I forgot to say that in my post. It’s the nuclear option but I think I’m just going to migrate to nextcloud AIO, it didn’t exist when I deployed the server several years back and seems nicer and also comes with a working deploy daemon which is nice. not really sure what the issue is, maybe something with snap isolation but i would’ve hoped the reverse proxy container would work around that. I never really liked the snap that much regardless.

4

I am having the same issue with Ubuntu 22 and running NC Snap 30.0.5.

I install the docker socker proxy container. I can connect to it with a curl command. I can use the admin AppAPI panel to test the connection successfully. If I test the deployment using the AppAPI panel, it fails. Further, I get a 403 error when I try to curl the container with the HAProxy password. I’ve checked many times that the HAProxy password is correct in the NC AppAPI registry. I installed HAProxy on the host machine and that did not help.

Help would be much appreciated.

5

I wasn’t able to figure out what the issue was on my server running the nextcloud snap package. I gave up on making it work and migrated to AIO and everything worked out of the box. I know it’s not really a fix or solution and wouldn’t be an option for some people but I ran out of ideas.