Results 1 to 3 of 3

Thread: using default ports 80, 443 with other services

  1. #1
    Join Date
    Jul 2008
    Posts
    44
    Rep Power
    7

    Default using default ports 80, 443 with other services

    i've got other services using port 80, 443 on my server, with nginx proxying between many different services using virtual hosts

    however, for zimbra i've got it running on port 81 and port 444 so as to not conflict with my other services.

    i'ld like to explore a way to get zimbra running on the default ports along with my other services.

    i've tried configuring my personal nginx to proxy a virtual host at 80 to 81 (443 to 444), but this falls short of my goals because the zimbra web client during login will forward physically to 81/444 after login. i'ld have to manually retype the URL after login.

    has anyone found an alternative solution that is more integrated?

  2. #2
    Join Date
    Sep 2005
    Location
    Sydney, Australia
    Posts
    291
    Rep Power
    10

    Default

    we do nginx proxying from another host that might help you out here. if you seach the forums you should be able to find a sample nginx config that does what you need, with some tweaking of course.
    http://www.solutionsfirst.com.au/hosting/zimbra/
    Australia's premier Zimbra Hosting Partner
    Resellers wanted!

  3. #3
    Join Date
    Jul 2008
    Posts
    44
    Rep Power
    7

    Default solved!

    i came up with a round-about solution that works for my particular setup.

    the proxying from my personal nginx to localhost was working, but when logging in, it would always redirect out to port 444, i realized this was because zimbra was set to always forward to https

    i modified it to use http instead with

    PHP Code:
    zmtlsctl http 
    my nginx takes care of ssl, and proxies 443 to localhost:81, and everything works.

    in case anyone is interested, here is my nginx conf that proxies to zimbra which runs off port 81 (used) and 444 (unused)

    PHP Code:
    # redirect http to https version
    server {
       
    listen      80;
       
    server_name mail.mydomain.com;
       
    rewrite     ^(.*)   https://mail.mydomain.com$1 permanent;
    }

    # my personal nginx will take care of ssl
    # and then use zimbra http underneath since i don't care
    # about security within the server, as it is all running on the same box
    server {
       
    listen   443;
       
    server_name  mail.mydomain.com;

       
    ssl  on;
       
    ssl_certificate  /path/to/cert.pem;
       
    ssl_certificate_key  /path/to/cert.pem;

       
    ssl_session_timeout  5m;

       
    ssl_protocols  SSLv2 SSLv3 TLSv1;
       
    ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
       
    ssl_prefer_server_ciphers   on;

       
    location / {
          include /
    etc/nginx/proxy.conf;
          
    proxy_pass  http://127.0.0.1:81;
          
    proxy_redirect  default;
       }


Similar Threads

  1. Replies: 45
    Last Post: 11-28-2007, 06:39 PM
  2. Perdition not restart !!!!
    By olibite in forum Administrators
    Replies: 2
    Last Post: 05-22-2007, 04:50 AM
  3. 3.0 to 4.5.3 Upgrade failed (mysql error)
    By dealt in forum Installation
    Replies: 35
    Last Post: 03-19-2007, 11:30 PM
  4. perdition won't start after 4.5 Upgrade
    By freeformz in forum Administrators
    Replies: 1
    Last Post: 01-29-2007, 07:39 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •