Remote Access to ISPConfig on https

Discussion in 'Installation/Configuration' started by roadster, Apr 27, 2007.

  1. roadster

    roadster New Member

    My problems seem identical to those in this post, which didn't ever seem to be resolved:

    I have ISPConfig on

    I can access everything fine from within the LAN and am able to access externally (shows default Apache/Fedora page) but NOT

    Domain settings in /home/admispconfig/ispconfig/lib/ are for and this domain and hostname are mirrored in the ISP Server settings within ISPConfig.

    The Lan is behind a NAT router/Firewall. Port 81 has been opened and tests as visible using Shields Up. The port is not being blocked upstream by our ISP.

    When accessing externally IE7 gives same result as the original poster received and Firefox reports that the connection has timed out and the server is taking too long to respond.

    This is the only issue I have had in this installation, which has otherwise gone very smoothly - thanks to the excellent How To tutorials :)

    Regards & TIA

    Roadster Chris
  2. roadster

    roadster New Member

    I may already have the answer myself! I believe that the provider at the external site that I was testing from may be blocking port 81, as it is a 'non-standard' port. They also block 8443 as used by Plesk.

    I'm at another site today with more liberal policies and will re-test from there. If all is OK then the next question will be .....

    How can ISPConfig be re-configured to use say port 8080, which is a little more 'standard'? Several of my clients use the draconian provider!

    Thanx again

    Roadster Chris
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    You can change the port in the file /root/ispconfig/httpd/conf/httpd.conf Just search for all occurrences of "81" and replace it with your new port.

    Then restart the ISPConfig server:

    /etc/init.d/ispconfig_server restart

    We do not have chosen port 8080 because this port is often used by Java application servers :)
  4. roadster

    roadster New Member

    Many thanks, Till.

    I have confirmed that the access issue was due to the external provider. 8080 is fine as Java app servers will not be used on this setup.

    Roadster Chris
  5. Hans

    Hans Moderator ISPConfig Developer

    Alternative, you can use portforwarding within your router.
    For example, you forward port 8080 to 81.
    In that case, you are able to visit your ISPConfig site from outside your LAN via http://yourdomain.tld:8080.

    Of course in this example, i assume that port 8080 is open within your router/firewall.
  6. roadster

    roadster New Member

    Of course! Sometimes the obvious and simple gets overlooked when one thinks the problem is deeper than it actually is. Works perfectly now through the ISP of those client sites that were proving troublesome.

    Thanks, Hans :)

    Roadster Chris

Share This Page