Posts by viper_iii

    ran the below command to change my panel to https...
    Currently on 1.3.0 - Debian - Wheezy - php 5.5 installed


    Code
    1. perl /var/www/imscp/engine/setup/imscp-reconfigure -dar panel_ssl

    and now the panel won't respond to https/http...



    if I re-run the command it will go back to http..


    in the setup I chose:
    Yes - continue
    Yes - Activate SSL
    No - Don't have Cert(expect that means it will create a selfsigned for admin.domain.com)
    https - Default access mode -


    cannot access the panel after this point..
    (it is still using port 8080 over https correct? - so no additional firewall ports need to be pass into our private network do they?


    not sure which specific log might show where an error might be located... or where the self signed cert might be located if not applied?


    -- to regain access --
    re-run the command and change default mode to http
    which gets access back via http - but still not running or able to connect via https



    - I'm sure I'm missing a step or at the part No don't have cert is the issue?


    - hopefully provided enough information per:
    Reporting Rules
    (generally not a bug - usually self generated)

    You're thinking terms of credentials...


    I'm thinking in terms of configuration of the server...
    non-critical / vital information that people may not want generally publicly visible - urls specifically for whatever reason and even version information.


    The information of the actual fix for others is still visible and just minor configs and urls are hidden from public view unless poster / moderator wants them public...


    that way the information is in the same place... - its also why it works well for other platforms... just a few think in terms of all or nothing security and all should be public - when others know there are things that are a bit more grey. between black and white.


    if the information was hacked or available - still not detrimental and not major just hidden a little better for moderators only.


    I use the same type of thing to keep information in one spot on other forums and put emails / numbers and only paid members can see the information.


    So not to protect Sensitive information - protect general information that others don't want publicly posted but isn't really critical so - not a password or credentials - still confidential in nature and moderators could see for replies related to the posters questions.


    ----
    either way only a wishlist item - just don't think passwords - more configs and versions of os and php - some of which is kinda private and others not really.

    Feature Request


    Would like to see a report section that reports environment settings/config for direct copy paste into forums for Moderators / Support to view all applicable settings.


    However - to include all that info publicly may not sit well with many - so a <Confidential>This is not public only Moderators can see</Confidential> type of tag would be useful for the forums - which probably exists just isn't currently see in the tool bar


    -- not currently supported by Burning Boards possibly --
    https://meta.discourse.org/t/w…derator-eyes-only/32482/5


    -- Report Section ---
    Generates a predefined set of BB Code data -
    Currently Kunena Forums has a report page in the Admin section that generates a bbcode post that is posted into the Kunena support forums...


    Just thought the general idea of the report section would be really helpful when posting about trouble with a server - when that page works / is viewable (server not offline case)
    even a shell command that generated the report would be cool


    --- Just a wishlist is all ---

    So I wanted to change my Admin to force https with a selfsigned cert for now - although a lets encrypt cert would also be fine but not necessary currently.


    - What is the installer command to rerun the installer and only change the admin to https (currently set to http only)? - so I don't mess up the install by going through things that I don't need to change.
    (I've seen it in the past but can't seem to find it today - not urgent)
    currently http://admin.site.com:8080 - want it to be forced to https://admin.site.com:8080 - know I saw it in the installer just want to do it right!
    (cloudflare can use self signed and will work fine - just not as secure - but more secure than http only!)
    found this link - does it still work this way in 1.3.x?
    Change panel from http to https

    Code
    1. imscp-autoinstaller -dasr ssl




    - Will lets encrypt plugin work with the admin page vs just user sites? (being admin is nginx not apache)
    Guessing No - same as no admin website options within the control panel itself either.

    the error when trying to get php7 going after update was the redirect however
    while you were testing


    File does not exist: /var/www/virtual/sclr.org/htdocs/php5-fcgi
    was coming up all the time trying to phpinfo to work..


    basically switcher apparently didn't change the alias for php (in my system at least) to /php7-fcgi and kept php5-fcgi which is why I'm guessing it was failing...


    however it may only be systems that are running php5.5 that was manually upgraded that this would show up on...
    (just a guess there though)

    was kidding about format...
    just that its pretty slow for compiling - forgot I had a lot of snapshots on there and consolidating and removing them now... causing more lag


    however yes running 7.0 php added a phpinfo page just to check


    or /info.php rather

    After Nuxwin about wanted to format my server(it might be a little slow!)... and digging for issues....


    I found that simply removing the phpswitcher plugin and reloading 2.2.5 version for my system works perfectly..
    back up and running by going back to older version with issues.


    2.2.6 may not work with wheezy - or maybe just my setup...

    not sure I upgraded properly..


    500 errors on all sites using switcher after update and graceful update of php versions - no actual updates done though was already current but rebuilt anyway.


    sites started having errors before I even updated to the new compiled versions. During compilation the 500 errors started.


    error logs show this:
    Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.


    didn't deactivate just updated plugin - was following along and might have missed deactivate...



    went ahead and double checked directory settings and noted that all I changed was the date to match the new compiled version and deleted the old compiled versions...


    ---
    the errors started during the compiler process - not after I updated the php versions.
    ----


    Updated Plugin
    started compiling 5.6 & 7.0 via:
    perl /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl -i /opt/phpswitcher/$(date +'%Y%m%d') 5.6 7.0


    that is when I noticed the errors on all pages utilizing 5.6 / 7.0...
    when I disabled the php versions and all sites defaulted to the server 5.5.x version all sites started working again.


    --- ideas what I did wrong there / How to Fix?