[OPEN-ILS-DEV] Changing Apache Ports

[Ryan Laverdiere]

I have talked with some of my library staff and found out that they can host on port 80 and is willing to let me use it. I now think I could use a proxy or tunnel the request through ssh.
  ----- Original Message ----- 
  From: Ryan Laverdiere<mailto:ryan at laverdieres.com> 
  To: Evergreen Development Discussion List<mailto:open-ils-dev at list.georgialibraries.org> 
  Sent: Sunday, October 26, 2008 7:56 PM
  Subject: Re: [OPEN-ILS-DEV] Changing Apache Ports


  I can use ssh without a problem! I have used this on a different computer. I am only thinking now how I could make SSH or a VPN easy for me and the Library Staff. Got any ideas? I am a devloper so I will try to do anything I can.
    ----- Original Message ----- 
    From: Jason Etheridge<mailto:jason at esilibrary.com> 
    To: Evergreen Development Discussion List<mailto:open-ils-dev at list.georgialibraries.org> 
    Sent: Saturday, October 25, 2008 12:19 PM
    Subject: Re: [OPEN-ILS-DEV] Changing Apache Ports


    > I am a simple user who is trying to setup evergreen for a small family
    > library system. It seems that in my research that verizon blocks port 80.
    > Can I change the http port of apache? Will evergreen still function if this
    > is done? Or is there a better solution?

    Hi Ryan,

    There are actually two ports you need to work with, port 80 for HTTP
    and port 443 for HTTPS.  I tried remapping these ports in the past (I
    think for you) and ran into difficulty.  One thing you might try
    doing, however, is running either a VPN or using SSH tunneling.

    Client Machine A  (extended family)  <->  Firewall   <-> Server
    Machine B (your house)   <-> Client Machine C (your house)

    So if the problem is that Machine C can connect to Evergreen on
    Machine B, but Machine A can't because you can't host a port-80/443
    service past the Verizon Firewall, then you could try running a ssh
    server on your side of the firewall, and have Machine A ssh into that
    server, and then tunnel Machine B's port 80/443 to Machine A such that
    the client on machine A would point to "localhost" port 80/443, and
    have it magically connect to Machine B instead.

    Of course, ssh (port 22) might be blocked as well.  You may have all
    connection requests initiated from the outside blocked, with only
    responses to requests that originated from your network allowed back
    in.

    Does this seem like a tack you might want to try?

    -- 
    Jason Etheridge
     | VP, Community Support and Advocacy
     | Equinox Software, Inc. / The Evergreen Experts
     | phone:  1-877-OPEN-ILS (673-6457)
     | email:  jason at esilibrary.com<mailto:jason at esilibrary.com>
     | web:  http://www.esilibrary.com<http://www.esilibrary.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20081028/7dd8afc4/attachment.htm