How to set document root path for Roundcube 1.7 when manually installed in ISPConfig 3 website

Discussion in 'Server Operation' started by gdeputy, May 10, 2026.

Tags:
  1. gdeputy

    gdeputy New Member HowtoForge Supporter

    I saw the stable release of roundcube 1.7 today, and tried to install it. Apparently they have changed their web structure, and require a /public_html folder be the root of the site, and then it references other files/folders that are above that root folder. This obviously does not work with ISPConfig, as it doesnt let you have 'custom' folders above /web. I tried using apache directives to override it to use /web/public_html as the root, but couldnt get that to work.
    Its rather irritating they made a change like this that entirely breaks roundcube on ispconfig3. Wondering if anyone else has tried this or has a workaround.
     
    /dev/null/ likes this.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    This assumption is not correct. ISPConfig allows you to configure a custom directory in Apache as well as in Nginx using the Apache or Nginx directives field for many years now. For Apache, the directive is named DocumentRoot, you use:

    Code:
    DocumentRoot "{DOCROOT_CLIENT}/public_html"
     
    /dev/null/, Nicram and ahrasis like this.
  3. gdeputy

    gdeputy New Member HowtoForge Supporter

    Thanks, I had tried that but was having trouble getting it to work. I'll give it another go.
     
  4. jnewman67

    jnewman67 Active Member HowtoForge Supporter

    Could I get a little deeper explanation of what's this change in RC 1.7 means? In the 1.6 version, "/webmail" was just an alias that became available to all domains added to an ISPConfig website as part of the global conf.d/roundcubemail.conf configuration file for Apache. Do I now have to "enable" roundcube for each domain added to server that has v1.7 installed by using the DocRoot directive above? is that directive ADDING another document root, or replacing the existing one? does the conf.d/roundcubemail.conf that we were using for v1.6 need to be changed for 1.7 to make it work globally?
    I've been looking around for an explanation to this, but have only been finding "you have to use public_html" but I've not seen what anyone actually changed to make that work.
    thanks.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    @jnewman67 The first poster manually installed RoundCube into a website, he does not use a standard ISPconfig installation. So any information above does not apply to standard ISPConfig setups. The post title is a bit misleading because it is not about a normal ISPconfig RoundCube installation.

    No.

    Do not add that directive to your website unless you also manually installed RoundCube into that website from source. Above, I answered a specific question about the manual installation of software that the first user made. The answer is specific to his case and manual setup; it does not apply to RoundCube on ISPConfig systems in general that were installed using our install guides or the auto installer.

    --

    Update: I've altered the thread title now to match the actual topic
     
    Last edited: May 22, 2026 at 6:56 PM
  6. jnewman67

    jnewman67 Active Member HowtoForge Supporter

    thanks for the clarification. I'll keep searching for how to integrate RC 1.7 into ISPConfig.

    edit, to be clear. i don't want roundcube to be the default site. I only want Roundcube to be accessible by using the aliases /webmail or /roundcubemail. i like having the Apache default website be the default.
     
    Last edited: May 23, 2026 at 3:03 AM
  7. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    If I remember correctly, ISPConfig (auto installer) default setup already included that and it uses RC that is shipped with the OS. Do look up in ISPConfig doc for older manual, if your early setup specifically did not include it but now wish to add that manually.
     
  8. jnewman67

    jnewman67 Active Member HowtoForge Supporter

    I'm on a CentOS/Rocky 9.7 platform, so roundcube is installed manually (untar, copy/paste config mainly, db initialize - still pretty simple).
    The real issue is that RC 1.7 has been revamped, and they want the default website to be the RC site. v1.6 was a generic install that you just created an alias for to access it - that doesn't appear to work any longer.
    My fix for the short term is to just stick with 1.6.15 and use the alias method - i don't want the default site to be Roundcube - don't need to advertise that's it's available for hacking :)

    thanks.
     
    ahrasis likes this.
  9. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Hurmmm... About that, the core change in Roundcube 1.7 is that the root of your web alias must point strictly to the public_html subfolder, rather than the main installation folder, so I think, you can still use the traditional /webmail alias on a shared domain without making Roundcube the default website or exposing it broadly. That said, I have not tested this.
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes, I'm pretty sure that he can do that. There is no need to make RoundCube the default site of your server and I won't do that on my systems.
     

Share This Page