Hello everyone, I would like to ask you for a hand to solve the following problem with Roundcube Webmail which is installed with an installation of ISPConfig, the problem is as follows: When I type https://webmail.dominioexample.com/webmail (With the webmail. domainexample.com registered on ISPConfig with forwarding to https://webmail.dominioexample.com/webmail) gives me error 500 and does not go, this does it with all domains by typing / webmail, while instead everything works correctly if I log in using the port of ISPConfig 8080 then typing https://webmail.dominioexample.com:8080/webmail. If anyone can help me out to solve this problem. Thank you
Which OS do you use and which tutorial to install the server? If you created a separate website webmail.domain.tld for the webmail client, then you should consider installing webmail directly into that site instead of using global aliases.
The OS is Debian while the tutorial I followed to install the ISPConfig server is the following: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/, yes, however, if I want access to be possible even from other sites it will no longer be possible.
I tell users to write the mail server URL / webmail, I find the setting up of /webmail for all possible domains is not a good idea. I believe writing port number is not needed.
Ok, I have disabled PHP now but it does not access the webmail with https but only with http because I am not using the ssl certificate generated by the panel but I am using one of my own, how should I access with https even using my certificate? Thank you
Set it up as a reverse proxy if you want access from customer websites, as allowing a shared roundcube install with a single config file is very insecure (add in the ispconfig plugins for roundcube and you're giving away a lot of access to your ispconfig system to all your clients, or anyone who hacks any of their sites). You could probably create a shared webmail.lots-of-domains.tld site and add webmail.clientdomain.tld domains to that, but the clients don't actually have any access to that site. That can become a mess in the future, eg. when a customer moves their domain and webmail.clientdomain.tld no longer points to your server, so your ssl certificate can't renew, so I wouldn't recommend this either. The easiest thing to do is simply use the server's hostname or a dedicated webmail name, as mentioned above.
I may not be clear on what you mean here, but you're accessing roundcube via a client website in this question? You would need to add an ssl certificate to every client site for this. Also note you can configure roundcube to require https, so that any sites which don't have a certificate can't be used in the clear. But I wouldn't do this, it is very insecure to share a single roundcube installation including configuration between sites.
Ok now it seems to work however when I set forwarding on ISPConfig on the website webmail.domainexample.com to make it go to https://webmail.domainexample.com/webmail gives me This page does not redirect correctly, how should I do to fix this error? Thank you
So this is a website you created to install roundcube in? And you want the http(s)://webmail.domainexample.com/ (no path) url to redirect to /webmail of the same site? Presumably all paths which do not start with /webmail should have that prepended? If so, that will need to be configured in the web server (apache or nginx, you haven't disclosed which), not from the website Redirect tab, which I think is what you are using?
No roundcube is not installed on the site, I just want to configure forwarding to that site with / webmail
Thanks to everyone for the advice / explanations on how to solve the problem, now for the moment everything seems to be working correctly.
