Mailcow + nextcloud (2 machine)

shellrider

Good afternoon, everyone. I have an interesting task.
There is a mail server that is configured as needed, works and pleases users. However, an interesting task has appeared - to organize a file cloud storage. Of course nextcloud, but deploying nextcloud on the same machine together with the mail server is a bad idea, because there is a saying about a basket and all the eggs in it. (that if the basket falls, then all the eggs will break)

And so. How to set up a machine with mailcow so that it is possible when adding https://mail.exsample.com/nextcloud.exsample was there a redirection from a mail machine to a machine with a cloud?

In addition, how do I add a button to the menu when entering mailcow?

I am new to the topic of administration and engineering of linux systems. I have a database, but I’m not ready to call myself a system administrator yet))

D4niel

Have you read the docs? https://docs.mailcow.email/third_party/nextcloud/third_party-nextcloud/
You can also setup Nextcloud independently from Mailcow with a reverse proxy.

shellrider Of course nextcloud, but deploying nextcloud on the same machine together with the mail server is a bad idea, because there is a saying about a basket and all the eggs in it.

I don’t think that is true in this case. That saying would basically mean that you could only host one virtual machine (or docker project in this case) per hypervisor. No one does that.

shellrider

D4niel

I tried according to the guide, adding the necessary lines to nginx. Locally, it forwards to the address. Yes, everything works, but locally. But from outside, it either does not connect at all (as if it is trying to connect to a local address, or it gives an error about “forwarding too many times”

That’s what interests me. How to make it so that it exchanges data through the server with mail, and does not try to crawl locally to a non-existent address in its network (in the network from where we intend to connect, that is, from outside)

roelofz

Looking at the overwhelming responses on Nextcloud questions, I think you’re right. It is one egg too many in a basket for the mailcow folks. This is not criticizing the mailcow folks, they’re doing a great job on mailcow, but I think one or two third party products are too many as they also need support).
The integration of the Nextcloud mail client for instance is not described (search for “nextcloud mail” and mailcow, neither on Nexcloud fora nor here), the backup script is not taking care of the /opt/mailcow-dockerized folder (containing all file data), and fixing issues getting it working is very complicated. This also has to do with the design of Nextcloud as Nextcloud is also not so easy to implement.

I took the long road last week and have it working, but it required a lot of searching and retrying (Collabora is a requirement in my case, it was nearly impossible as a result of the shared proxy, nginx). The mail client is still a mistery, as nginx (nextcloud is sitting in that container) may not have the rights to interact with dovecot (allthough sogo does that too using nginx, so there’s the puzzling part). I created an extra backup script saving the /opt/mailcow-dockerized folder (900 Mb on a clean install, difficult to filter).

So I have Nextcloud running in the same containerset as Mailcow and I think I may be able to restore it after a crash, but again, this is at my own risk, as good documentation (and time needed to create it) is missing. I can share my backup script, may be helpfull.