Posts by viper_iii

  • 1.3.0 Wheezy > 1.3.1 Upgrade

    Upgrade when ok
    manually stopped services
    disabled all plugins - then had to use normal ports (already updated to 8443 on mine.
    errata - disabled php-APC line in wheezy docs - still only shows in 1.2 but still an issue for Wheezy users that upgraded to php5.5 manually.


    ran the installer
    no errors finished sucessfully
    admin panel would never load on any ports.


    All websites worked fine - didn't have time to dig deeper rolled back to 1.3.0 via shapshot.
    panel webserver never started back up it appears.


    which logs should I check on next attempt? so I can post more information?
    (other plan) move sites to fresh jessie install without too many customization - which seem to cause some of my issues!

  • Serie 1.3.x - Panel listening ports - CloudFlare

    Quote from Ninos

    Why it would not work? Please read what the PanelRedirect plugin is doing. It's proxying the Panel through default ports (80/443) of the panel domain.

    good call - installed redirect


    proxy didn't work initially -
    changed config to redirect and worked - restarted apache2 service - not sure if that helped or not... had rebooted as well no difference.


    (last night I also found I wasn't forwarding https through firewall when I updated the 8443 port I forgot to re-add https to the inbound so I'm pretty sure redirect would have worked initially without any trouble!)



    Code
    1. /var/www/imscp/gui/plugins/PanelRedirect/config.php

    odd on the redirect - it doesn't show the :8443 - but is working so I'm not complaining!


    changed back to proxy - restarted apache service again - still working -
    so much better with the panel redirect
    thx!

  • Serie 1.3.x - Panel listening ports - CloudFlare

    Code
    1. perl /var/www/imscp/engine/setup/imscp-reconfigure -r panel_ports

    perfect - also appreciate the help on the commands to get forward.
    that did the trick exactly!


    just had to update firewall inbound rules for 8443 - which didn't take on the firewall initially - (juniper headache and edit interface & policy have to have both apparently updated... argh...


    Either way I've definitely learned a bit more... help commands are available! and fairly in depth!
    (only with your examples did I really get it quicker though)


    also huge thx for hopefully getting cloudflare to add 4443 panel port to their inbound ports - mine is currently 8443 and working as desired -


    auto forward - http://admin.domain.com:8443 gets an error from cloud flare:



    400 Bad Request
    The plain HTTP request was sent to HTTPS portcloudflare-nginx



    which is because their http ports don't go through on that port - so makes sense on that end as well - not imscp there either...


    self signed - cloudflare - crypto = Full - not full Strict - (Full strict would require a valid cert)
    (can wait until 1.4.x version and letsencrypt)

  • Serie 1.3.x - Panel listening ports - CloudFlare

    hummm.... Was resolving fine prior to enabling https for panel...


    Will pm hostnames and up... Uses cloudflare so won't see direct ip without pm.


    Can see nginx listening ipv4 and ipv6 but v4 shows host.domaon.com:4443


    v6 shows
    *:4443


    Connected with fqdn after adding matching to DNS... But now none work..... Now wondering if it's firewall related vs server.

  • Serie 1.3.x - Panel listening ports - CloudFlare

    ok found another issue - have the correct ports forwarded however found the server is listening to hostname on https : 4443 vs * like other services..


    so if I goto hxxps://admin.domain.com:4443 it will not load - Server Not Found
    however if I goto hxxps://hostname.domain.com:4443 it loads but has a cert for admin.domain.com -


    Not sure where to edit the nginx config to listen for the alias name - at least it appears it will only listen on that name which is odd... but appears to be that way...