Your commands are OK, however I looked at /etc/e-smith/templates/httpd/vhost-default/30SOGo and the /SOGo location is expected. I understand it does not solve your issue.
Do you want to try this workaround?
install the File server module
create a shared folder and set it as web root of the webmail virtual host
add an index.php into the web root with the following content:
In a fresh NS 7.5.1804 I’m facing a comparable problem.
in the default root /var/www/html I’ve installed my www.domain.nl
Redirect cloud.domain.nl for nextcloud works like a charme, including the use of the letsencrypt certificate.
Redirect webmail.domain.nl for SOGo gives the above problem, I still need to ad the ./SOGo to reach the page, but also the letsencrypt certificate is ignored. The certificate is multidomain and works for the other aliases as well as the installed vhost www.otherdomain.nl.
Is there a solution so that I don’t have to ad any samba shares on this server to keep it a clean web/mail server?
This is a old post and there for not every accurate;
Did you see this thread?
I think it’s better you explain the certificate issue in a separate post…
Quite a while ago tried to accomplish this, never succeeded with the all the (reverse) proxing to the localhost port of sogod. I think I cracked it now, could you test this?
First set up SOGo to listen to its own virtual host
Edit /etc/e-smith/templates-custom/etc/httpd/conf.d/SOGo.conf/10base Add add the lineRedirectMatch ^/\$ https://$sogo_host/SOGo
(note the escape \ before $)
I came to this post over the thread you mentioned.
Regarding the certificate issue, it is imo related, I use a multidomain certificate but the set default letsencrypt certificate doesn’t get used due to the default certificate SOGo is taken account for in its config.
I followed your instructions and it works. So I also made the user template and put in the redirect as instructed. Also I commented out the lines in this user template of the SSLCertificateFile and SSLCertificateKeyFile. Result is a correct redirect and use of the correct multi domain certificate.
But what I expected by putting the question on line is the following:
Nextcloud installation was reached by https/www.domain.nl/nextcloud and after following the instructions in nextcloud manuall of nethserver (the same kind of instructions as for SOGo) I now reach the cloud server over https://cloud.domain.nl without further redirect and in the same way my webdav listens to https://cloud.domain.nl/remote.php/webdav instead of https://www.domain.nl/nextcloud/remote.php/webdav
The commit you did redirect ‘/’ to /SOGo, but a side effect exists, the SOGo.conf vhost becomes the default vhost and all vhost are redirected to /SOGo. Hence I moved the sogo.conf to zzz_SOGO.conf
[root@prometheus ~]# httpd -S
VirtualHost configuration:
*:80 is a NameVirtualHost
default server webmail.aubrac-medical.com (/etc/httpd/conf.d/SOGo.conf:10)
port 80 namevhost webmail.aubrac-medical.com (/etc/httpd/conf.d/SOGo.conf:10)
port 80 namevhost webmail.de-labrusse.fr (/etc/httpd/conf.d/zz_SOGo.conf:10)
*:443 is a NameVirtualHost
default server webmail.aubrac-medical.com (/etc/httpd/conf.d/SOGo.conf:18)
port 443 namevhost webmail.aubrac-medical.com (/etc/httpd/conf.d/SOGo.conf:18)
port 443 namevhost prometheus.de-labrusse.fr (/etc/httpd/conf.d/nethserver.conf:42)
port 443 namevhost prometheus.de-labrusse.fr (/etc/httpd/conf.d/ssl.conf:56)
port 443 namevhost webmail.de-labrusse.fr (/etc/httpd/conf.d/zz_SOGo.conf:18)
Twe two are redirected to /SOGo even if you use only sub1.domain.com in the apache sogo configuration.
This is done when you have several web app configured and when your apache configuration is taken as the default one. We have configured like this mattermost, dokuwiki, nextcloud and now SOGo by naming the apache configuration to zz_*. Like this the nethserver.conf become the default vhost
lets close the sogo bug if you agree and start a new talk on the 000-nethserver.conf…since you raised your hand, please shoot first to start a discussion on discourse