[solved] Interworx integration for webmail

Discussion in 'Install/Configuration' started by bangsters, Feb 1, 2012.

  1. bangsters

    bangsters New Member

    Guys. So far everything rocks with litespeed. Using it production-wise. Just have some minor glitches, like the mod_rewrite for wordpress issue (separate thread), and not getting the webmail at port 80.

    Basically, with interworx, webmail is at port 2443, the default for their internal webserver I think. However, with apache, I think it's being proxied (mod_proxy as per interworx reply) to be accessible at port 80, like http://domain.com/webmail. This is done automatically and no webmail folder really exists per website.

    However, with the switch to litespeed, webmail is no longer accessible at port 80, and now our clients have to go through port 2443, which everyone of my clients hate. Anyway I can get litespeed to work the same way? Any suggestions? Below is the response I got form interworx support, hoping that helps as well

    Here are my questions to them and their reply, hopefully some can chime in....

    1. webmail is no longer accessible from domain.com/webmail. Now I have to
    put the port 2443 to access webmail. Before with apache, webmail was in port 80
    at domain.com/webmail

    The apache configuration for webmail at port 80 is in the /etc/httpd/conf.d/iworx.conf. It uses apache's mod_proxy, so my best guess is that litespeed doesn't handle that apache configuration? Perhaps the litespeed folks could provide an alternative.

    2. webserver part of nodeworx is empty. I mean the RRD graphs now looks like no traffic at all....

    This is because that particular graph is generated from the mod_watch apache module, which litespeed doesn't support. There's not much we can do about this one unfortunately.
    Last edited by a moderator: Feb 16, 2012
  2. webizen

    webizen New Member

  3. bangsters

    bangsters New Member

    Thanks! but what do I do with it and where do I put it? :)
  4. webizen

    webizen New Member

    you need to
    1. create a web server external app (e.g. name: webmail, addr: server_address:2443) at server level.
    2. create rewrite rule in .htaccess under domain docroot.
  5. bangsters

    bangsters New Member

    I have added the external app. I created the .htaccess file. I get a 500 error. My .htaccess located in my ./html folder is

    RewriteEngine On
    RewriteRule ^(.*)$ http://webmail/$1 [P,E=Proxy-Host:domainxyz.com/webmail]

    Anything I'm doing wrong?

    EDIT: What's worse is the domain itself becomes accessble with a 500 error once I have the rewriterule in place.
    Last edited: Feb 1, 2012
  6. bangsters

    bangsters New Member

    I got a workaround by using a subdomain. works like a charm.

    however, it is only for http proxying....

    any idea when litespeed will support proxy for https?
  7. webizen

    webizen New Member

    Proxy through https is not a priority item. You can use https as frontend interface with user and have backend proxy through http as a workaround.
  8. bangsters

    bangsters New Member

    HI.

    How can I do that? I meant having the front end in https?
    Last edited: Feb 16, 2012
  9. webizen

    webizen New Member

  10. bangsters

    bangsters New Member

    That is how i did it I think....

    I created a vhost with a dedicated IP in portal.domainxyz.com/webmail. Then I created an .htaccess file inside that subdomain containing:

    RewriteRule ^(.*)$ https://webmail/$1 [P] #,E=Proxy-Host:portal.domainxyz.com]

    In the litespeed backend, do I still use webmail with 127.0.0.1:2080 (http) or 127.0.0.1:2443? I currently left it at port 2080 since it should be http.

    But I'm getting a 500 error. what am i doing wrong?
    Last edited: Feb 16, 2012
  11. bangsters

    bangsters New Member

    Actually got it to work!!! Thanks!!!

    My rewrite rule was wrong.... I should have kept it at http://webmail/ instead of https://webmail/

    Thanks again webizen and everyone in the forums.
  12. webizen

    webizen New Member

    thanks for the confirmation.

    here is the wrap-up:

    vhost accepts https request:

    https://portal.domain.com/webmail

    .htaccess rewrite rule in question should be proxy to http (not https) as follows:
    webmail is the 'web server' type ext app pointing to 127.0.0.1:2080
    Last edited: Feb 16, 2012

Share This Page