Koozali.org: home of the SME Server

Primary I-Bay

Offline ltwally

  • ****
  • 108
  • +0/-0
Primary I-Bay
« on: September 26, 2007, 09:18:44 PM »
Our primary I-Bay is accessible from the internal network, and can be reached from our external network via HTTPS... but is not available from the outside via HTTP.  The SME server is running version 7.2, and has a network card directly on the outside.  The website is registered correctly, and all DNS is pointing to the correct IP address.

Anyone know of some setting that would prohibit the html directory of I-bays to be inaccessible from the outside?

Thanks,
-ltwally

Offline pfloor

  • *****
  • 889
  • +1/-0
Re: Primary I-Bay
« Reply #1 on: September 27, 2007, 04:27:38 AM »
Your ISP may be blocking port 80 to prevent you from running a web server, have you checked that?

In life, you must either "Push, Pull or Get out of the way!"

Offline ltwally

  • ****
  • 108
  • +0/-0
Re: Primary I-Bay
« Reply #2 on: September 28, 2007, 04:25:58 PM »
They're on a T1 line.  This isn't a home install, but a business server.  ;)

There has got to be a security setting that's disabling public http, but allowing https.  Anyone know of it?

Thanks

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Primary I-Bay
« Reply #3 on: September 28, 2007, 04:46:30 PM »
Our primary I-Bay is accessible from the internal network, and can be reached from our external network via HTTPS... but is not available from the outside via HTTP.

Please define exactly what you mean by "is not available". What do you see when you try to access it?

Offline ltwally

  • ****
  • 108
  • +0/-0
Re: Primary I-Bay
« Reply #4 on: September 28, 2007, 04:48:58 PM »
It'll time out.  The server flat does not respond to outside requests on port 80.

However, port 443 is fine on both sides and port 80 is fine on the inside.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Primary I-Bay
« Reply #5 on: September 28, 2007, 07:41:38 PM »
It'll time out.  The server flat does not respond to outside requests on port 80.

Then the reference specifically to 'Primary I-Bay' is bogus. HTTP access on port 80 is blocked somewhere. The exact resource your browser might have requested if it was able to is not relevant.

I agree with Paul Floor that the most likely cause is your ISP blocking port 80 traffic.

Offline ltwally

  • ****
  • 108
  • +0/-0
Re: Primary I-Bay
« Reply #6 on: September 28, 2007, 09:12:15 PM »
We can safely rule that one out.  We threw another server up on that IP and it worked fine.

It's definitely SME.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Primary I-Bay
« Reply #7 on: September 28, 2007, 10:29:22 PM »
We can safely rule that one out.  We threw another server up on that IP and it worked fine.

It's definitely SME.

Then use the Bug Tracker and ask that SME be fixed.

Offline haymann

  • *
  • 212
  • +0/-0
Re: Primary I-Bay
« Reply #8 on: October 04, 2007, 05:16:42 PM »
If you create another ibay and set it up so it is open to the local network and the internet, can you get to it? Or is the problem only the primary ibay?