How does Stalwart mesh with a web server on the same machine, e.g. Nextcloud, etc.?

[rcfa]

Is Stalwart using its own built-in web server, or does it create an apache vhost for its purposes that can coexist with other web services on the same port, as it’s URL based?

Don’t seem to be able to find any information on that matter…

Point is, I don’t want to use docker or the like, but preferably a single server...

[enaut]

YOU can configure apache for a URL based routing and set the management port to something other than 443 and 80. Or you just access the management page from a different port.
But the configuration of apache, nginx, etc. is not done automatically.

[rcfa]

OK, thanks.

Is there documentation somewhere on how to do this?

In particular there’s also the issue with ACME certificates and how to share and renew them in a way Apache/Nextcloud and Stalwart don’t step on each other’s toes.

There may also be other issues, like CalDAV, etc. so a document that describes same-host setup of Stalwart and Nextcloud would be very welcome, particularly in light of the recent announcement of the collaboration between Nexctloud and Stalwart...

[mdecimus]

Is Stalwart using its own built-in web server

Yes, Stalwart includes its own webserver. If you want to use Nginx or other reverse proxy here is the documentation.

[mitexleo]

I have multiple applications on the same server. If I configure nginx reverse proxy according to the documentation will I cause any issues with the websites already running?

[mdecimus]

No issues, just make sure that in Nginx you route these HTTP endpoints to Stalwart.

[alex9434]

I currently use the following configuration for nginx:

server {
	listen 443 ssl http2;
	listen [::]:443 ssl http2;

	server_name mail.example.com autoconfig.example.com autodiscover.example.com;

	include snippets/ssl.conf;
	include snippets/letsencrypt.conf;

	location / {
		proxy_set_header Host $host;
		proxy_set_header X-Real-IP $remote_addr;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_set_header X-Forwarded-Proto $scheme;
		proxy_set_header X-Forwarded-Host $host:$server_port;

		# support http 1.1 persistent connections
		#proxy_set_header Connection "upgrade";
		proxy_set_header Upgrade $http_upgrade;
		proxy_pass  http://127.0.0.1:8080/;
	}
}

I hope that helps. So far I have only tested the webinterface. If anybody has any improvements, I would be very happy to include them.

Remark: Currently it does not seem possible to use a subfolder , e.g. example.com/stalwart/login instead of mail.example.com/login. Using configurable subfolder would be a great feature for me!