Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-03-2008, 12:17 PM
Trained Alumni
 
Posts: 22
Default Unable to revert to http mode

Currently my Zimbra server (zcs-NETWORK-5.0.2_GA_1975.RHEL5_64.20080130215245 on CentOS x86_64) is configured to redirect web requests to SSL. Zimbra listens to port 8080 for http and 1443 for SSL (apache2 is also running on this server).

I would like for users to be able to login and use the web client over http. However, if I run zmtlsctl http and restart Zimbra services, the redirect still occurs but fails to render the page (since jetty is no longer listening on 1443). There are no iptables rules on this server nor is apache involved (I get the same behavior if apache is stopped). I'm not sure what else to look for. Any ideas?
Reply With Quote
  #2 (permalink)  
Old 03-04-2008, 10:52 AM
Former Zimbran
 
Posts: 5,606
Default

Any reason zimbra can't run on 80?
Reply With Quote
  #3 (permalink)  
Old 03-04-2008, 11:42 AM
Trained Alumni
 
Posts: 22
Default

This server also has a number of internal web applications running on apache. Port 81 or 8080 would be fine if I could convince zimbra to listen instead of automatically redirecting to SSL (currently 1443).
Reply With Quote
  #4 (permalink)  
Old 03-09-2008, 12:20 PM
Starter Member
 
Posts: 1
Default Same on Network Edition too

I'm having the same problem. Added details to this bug report
Bug 24884 - zmtlsctl doesn't update zimbra.web.xml.in or zimbraAdmin.web.xml.in

BUILD: Release 5.0.2_GA_1975.RHEL5_20080130212656 CentOS5 NETWORK edition

Steps to reproduce
(to set redirect)

zmtlsctl redirect
zmcontrol stop
zmcontrol start
zmprov gs domain.com |grep Auth
zimbraMtaAuthEnabled: TRUE
zimbraMtaAuthHost: domain.com
zimbraMtaAuthTarget: TRUE
zimbraMtaAuthURL: https://domain.com:443/service/soap/
zimbraMtaTlsAuthOnly: TRUE
zmprov gs domain.com |grep Mode
zimbraMailMode: redirect
zmprov ms domain.com zimbraMtaAuthHost domain.com
curl http://domain.com |grep Location
Location: https://domain.com:443/zimbra


(to set back to http)

zmtlsctl http
zmcontrol stop
zmcontrol start
zmprov ms domain.com zimbraMtaAuthHost domain.com
zmprov ms domain.com zimbraMtaTlsAuthOnly FALSE
zmprov gs domain.com |grep Auth
zimbraMtaAuthEnabled: TRUE
zimbraMtaAuthHost: domain
zimbraMtaAuthTarget: TRUE
zimbraMtaAuthURL: http://domain.com/service/soap/
zimbraMtaTlsAuthOnly: FALSE
zmprov gs domain.com |grep Mode
zimbraMailMode: http
curl http://domain.com |grep Location
Location: https://domain.com:443/zimbra


Editing out the protocol used and the section in
mailboxd/webapps/zimbra/WEB-INF/web.xml
does not solve this, as the REDIRECTBEGIN block is somehow added back after the
reboot.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.