Koozali.org: home of the SME Server

HTTPS Access from the web

Offline wpatkip

  • 4
  • +0/-0
HTTPS Access from the web
« on: November 12, 2007, 02:13:51 PM »
Dear All,

I used for a few months a 7.2 sme server as mail server. My Server is configured as Server Only with samba functionalities and DNS functionalities. Users access that server either from the LAN or from internet using an url like that https://mail.domain.com/groupoffice (we use GO as webmail client).

Maybe Am i too optimistic ? But i apply periodically the yum updates proposed thru the server manager. And since november the 10th, the access from the web is impossible neither with the symbolic name of my domain nor with the public IP address. The configuration of my firewall didn't change. I just did an update with theses packages :

Nov 10 16:04:22 Updated: e-smith-lib.noarch 1.18.0-18.el4.sme
Nov 10 16:04:24 Updated: e-smith-base.i386 4.18.0-75.el4.sme
Nov 10 16:04:25 Updated: qpsmtpd.noarch 0.40-1.7.el4.sme
Nov 10 16:04:25 Updated: e-smith-samba.noarch 1.14.0-33.el4.sme
Nov 10 16:04:26 Updated: smeserver-locale-it.noarch 1.2.0-30.el4.sme
Nov 10 16:04:28 Updated: cups-libs.i386 1:1.1.22-0.rc1.9.20.2.el4_5.2
Nov 10 16:04:28 Updated: e-smith-portforwarding.noarch 1.2.0-5.el4.sme
Nov 10 16:04:28 Updated: e-smith-proxy.noarch 4.14.0-8.el4.sme
Nov 10 16:04:29 Updated: e-smith-viewlogfiles.noarch 1.8.0-5.el4.sme
Nov 10 16:04:29 Updated: e-smith-proftpd.noarch 1.12.0-10.el4.sme
Nov 10 16:04:29 Updated: ipsvd.i386 0.12.1-5.el4.sme
Nov 10 16:04:30 Updated: e-smith-apache.noarch 1.2.0-16.el4.sme
Nov 10 16:04:31 Updated: e-smith-domains.noarch 1.4.0-8.el4.sme
Nov 10 16:04:31 Updated: smeserver-locale-fr.noarch 1.2.0-30.el4.sme
Nov 10 16:04:31 Updated: e-smith-openssh.noarch 1.12.0-10.el4.sme
Nov 10 16:04:32 Updated: smeserver-locale-sv.noarch 1.2.0-30.el4.sme
Nov 10 16:04:32 Updated: smeserver-locale-de.noarch 1.2.0-30.el4.sme
Nov 10 16:04:33 Updated: smeserver-locale-es.noarch 1.2.0-30.el4.sme
Nov 10 16:04:33 Updated: e-smith-dnscache.noarch 1.0.0-8.el4.sme

Help would be appreciated !!
Thanks

Offline mmccarn

  • *
  • 2,656
  • +10/-0
Re: HTTPS Access from the web
« Reply #1 on: November 12, 2007, 03:44:51 PM »
Are you still able to access your server from the local network?

If so, the issue may relate to 'Public' / 'Private' access rights on something. 

If not, I suspect a problem with the GroupOffice installation...

You'll want to open a report in the bug tracker.  If you can, run the following command and upload the results to the bug.  If the output is extensive (over 20 lines or so) please upload it as an attachment rather than pasting it directly into the bug report...

/sbin/e-smith/audittools/newrpms


Offline wpatkip

  • 4
  • +0/-0
Re: HTTPS Access from the web
« Reply #2 on: November 12, 2007, 04:16:43 PM »
Thank you for your answer mmccarn.

But this is not an issue of rights on Group Office. I omitted to tell that we can not reach our server from the web with the standard webmail of SME (Horde - IMP) too.

Thanks

Offline mmccarn

  • *
  • 2,656
  • +10/-0
Re: HTTPS Access from the web
« Reply #3 on: November 12, 2007, 04:41:25 PM »
Are you still able to access your server as you wish from the local network?

Offline wpatkip

  • 4
  • +0/-0
Re: HTTPS Access from the web
« Reply #4 on: November 12, 2007, 04:51:00 PM »
Yes !

Both webmail client (Groupoffice and IMP) are accessible within my LAN with the standard path, i.e. https://myserver.mydomain.com/webmail or https://myserver.mydomain.com/groupoffice

Very strange.... a telnet connection on HTTPS port works on my lan but not from the web (telnet myserver.mydomain.com 443).

I told in my former messages about possible problems with RPM updates....but i'm not so sure. HTTP logs and HTTPD error logs show that access from the web broke down on friday the 9th at 10:54...and we did nothing on the server at this time...

Thanks for your help

Offline wpatkip

  • 4
  • +0/-0
Re: HTTPS Access from the web
« Reply #5 on: November 12, 2007, 06:29:30 PM »
Sorry for all that noise....

It seems that our firewall is guilty of that situation. The one-to-one NAT between our public IP address and the IP address on the LAN does not work in certain cases....Thanks Sonicwall "Comprehensive Internet Security" !!