NextCloud AIO Docker ( 443 Loginpage broken pipe )

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1

Hello community,

Well, I’m not very experienced in forum communication, so I ask for your patience.
For several days now, I am completely clueless., or in other words, I can’t see the forest for the trees.

My supposedly simple goal is to install Nextcloud AIO. Condition: only for internal use, not accessible from the internet.

My environment
Router/switch
Proxmox (ThinkCentre)
VM with Ubuntu 24 LTS (for NC AIO)
NGINX NPM
Adguard Home

  • …
    All systems and applications are up to date

The Docker Run command from github is used for the installation, and the necessary settings for NGNIX are entered. Tested with different entries and commands as well

Ultimately, when we get to “Submit Domain,” the domain is not accessible via 443 of the container.

If I skip the verification, the installation is completed, but the login page for admin and initial password does not open.

Everything I have already tried would only show that I have tried a lot with a certain degree of cluelessness. :wink:

You could say that I have tried all IP addresses with the different ports and sometimes with http and https.

Before I start throwing around guesses, I would like to ask you directly what the problem could be.

Just one more thing. . Something I can’t explain. NC checks whether the domain is accessible via 443, but even in the VM I can’t open the port.
Info: All firewalls at the Proxmox levels are disabled.

The log nextcloud-aio-mastercontainer says

The response of the connection attempt to “https://nxcd.local:443” was:
NOTICE: PHP message: Expected was: 85e2f2e5825f6ec0846012268e2fc735daddf0002d8044c5
NOTICE: PHP message: The error message was: Send failure: Broken pipe

I hope you can show me the tree that I can’t see. :wink:

Thanks & best regards
Eckstein

github docker run all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub

2

I recommend checking out this thread (including the replies):
:backhand_index_pointing_right: Ubuntu 24.04 + Nextcloud AIO best practices

In my answers there I’ve summarized a couple of things that should help you get oriented:

  • Best practices for running Nextcloud AIO in Docker using a docker-compose.yml file instead of the raw docker run command. This makes it easier to manage and modify the setup.

  • Proxmox + Ubuntu VM configuration that avoids common pitfalls, especially if you want stable performance and seamless large file uploads. - Testing Large File Synchronization with Nextcloud AIO and NGINX Proxy — June 2025 Update

  • Nginx Proxy Manager configuration for Nextcloud, with working reverse proxy rules. - the same URL

  • Explanation of how to adapt the docker-compose.yml if you need to attach Nextcloud AIO to an existing volume.

  • Portainer benefits

If you go through that thread and the answers, you’ll have a clearer overview of how the pieces (AIO, VM, NPM) fit together and how to avoid the broken-pipe / port 443 issues you’re seeing now.

3

AiO is supposed to be accessible from the internet. you want to review all-in-one/local-instance.md at main · nextcloud/all-in-one · GitHub for options

4

Thank you for sharing the additional links. I learned a lot and tried out some things that seemed relevant to my problem. Unfortunately, however, the problem has not been resolved.

It seems to me that there is a problem with name resolution. However, I was unable to define it more precisely because there are no entries in the LOG at the time the error occurred.

The entries in the NPM are correct. The IP addresses and ports are correct!

The DNS description in Adgurad is present and correct.

Ping to the NC IP is answered.

Nslookup to the NC domain is answered.

Proxmox = vmbr0 | DNS entry present and correct | Firewalls disabled

5

This topic was automatically closed after 90 days. New replies are no longer allowed.