# Cannot deploy AIO with existing npm

**URL:** <https://help.nextcloud.com/t/cannot-deploy-aio-with-existing-npm/247056>\
**Category:** ℹ️ Support\
**Tags:** caddy, docker, portainer, selinux, aio, cloudflare, docker-compose\
**Created:** [July 17, 2026, 7:53pm UTC](https://help.nextcloud.com/t/cannot-deploy-aio-with-existing-npm/247056 "2026-07-17T19:53:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![vawaver](https://help.nextcloud.com/user_avatar/help.nextcloud.com/vawaver/32/71824_2.png) [@vawaver](https://help.nextcloud.com/u/vawaver)\
**Post date:** [July 17, 2026, 8:18pm UTC](https://help.nextcloud.com/t/cannot-deploy-aio-with-existing-npm/247056/2 "2026-07-17T20:18:20Z")

</div>

This error is not caused by NGINX Proxy Manager. Portainer is rejecting the Compose file before AIO is even deployed.

I would also avoid pasting the configuration directly into Portainer as a Stack. For a critical service, I prefer keeping the `docker-compose.yml` file directly on the host and deploying it with:

```bash
docker compose config
docker compose up -d

```

Portainer can still be used for monitoring, logs and container management, but it should not be the only place where the deployment configuration exists.

My complete working setup is documented here:

> [@Proxmox + NGINX + Nextcloud AIO + Watchtower Deployment Guide](https://help.nextcloud.com/t/proxmox-nginx-nextcloud-aio-watchtower-deployment-guide/233643):
>
> 1. Introduction This guide is designed for self-hosting enthusiasts who want to deploy Nextcloud AIO on their own infrastructure rather than relying on third-party hosting providers. It assumes that the user already has access to the following: a public IP address, a registered subdomain, and a running Proxmox server. While the guide primarily focuses on a Proxmox-based home or lab environment, it can also be adapted for VPS installations, provided certain conditions are met. Throu…

I have been using this setup for almost 3 years now, and it has been working reliably without issues.

For the current problem, fix the YAML structure first and validate it with `docker compose config`.

---

_[View the full topic](https://help.nextcloud.com/t/cannot-deploy-aio-with-existing-npm/247056)._