Posts by viper_iii

    1.3.x definitely helped the issues I was seeing ..


    had some cookie issues and clearing cache helped but also


    For my use via cloudflare even using selfsigned Certs is showing up fully secure interestingly enough and not even having to use the Origin Cert provided...


    might try that later though and see if its all working correctly.


    -------
    To correct some of my tweaks / modifications in the ssl_conf files
    deleted ssl certs via GUI - then created self signed for all domains with issues.


    Currently appears to be working well.


    also have phpswitcher 2.2.5 installed and working.. really like the per site option and 7.x php is really much faster!

    Got all the way through it again now its doing the same thing again crashing the installer right after imscp_user password autogeneration.


    trying as suggested above:
    Installer closed after creating IMSCP SQL Users | Installation beendet nach Erstellen des IMSCP SQL Users
    ---
    both of mine were already at no for ssl on panel -
    PANEL_SSL_ENABLED = no
    SERVICES_SSL_ENABLED = no
    in both files.


    rerunning -d to see if same issue happens


    yes it does.... same issue


    [Mon Jun 27 17:15:27 2016] [debug] iMSCP::Execute::execute: /usr/bin/dialog --yes-label Yes --help-label Help --insecure --backtitle 'i-MSCP - internet Multi Server Control Panel (1.3.0)' --cancel-label Back --exit-label Abort --title 'i-MSCP Installer Dialog' --colors --ok-label Ok --no-label No --radiolist '
    \Z4\Zb\ZuMySQL Database Prefix/Suffix\Zn
    (This screen never came up)
    Do you want use a prefix or suffix for customer'\''s SQL databases?


    \Z4Infront:\Zn A numeric prefix such as '\''1_'\'' will be added to each customer
    SQL user and database name.
    \Z4Behind:\Zn A numeric suffix such as '\''_1'\'' will be added to each customer
    SQL user and database name.
    \Z4None\Zn: Choice will be let to customer.
    ' 14 70 3 infront '' off behind '' off none '' on
    [Mon Jun 27 17:15:27 2016] [debug] iMSCP::Execute::getExitCode: Command exited with value: 255

    Setup runs great and finishes - but still getting 500 errors on all sites after updating mysql root password...


    control panel loads fine.. checking access error logs to see what is happening on each site...


    errors in log are apache errors..



    [Mon Jun 27 10:02:32 2016] [error] [client 108.162.215.250] (2)No such file or directory: FastCGI: failed to connect to server "/var/lib/apache2/fastcgi/php5-fcgi-invoice.<domain>.com": connect() failed, referer: http://invoice.<domain>.com/


    [Mon Jun 27 10:02:32 2016] [error] [client 108.162.215.250] FastCGI: incomplete headers (0 bytes) received from server "/var/lib/apache2/fastcgi/php5-fcgi-invoice.<domain>.com", referer: http://invoice.<domain>.com/


    ---
    so it looks like I'm using fastcgi vs fpm correct?


    restarted apache
    sudo service apache2 restart
    no change still same errors..


    rebooting server just for kicks.


    That seems to have resolved the issue - rebooting the server - (kicked all services to restart probably php services) and now running with correct sql root password (or at least documented!)


    ---- Will try upgrade again later / soon (thx for help - getting further!)

    currently rolled back to backup and changing mysql password
    re-running 1.2.17 setup -dr and verifying things work before proceeding to attempt 1.3 again with correct root mysql password in hand.


    currently 1.2.17 install via -dr update is running without issue and able to connect to known mysql - using reset method I used above.


    --- link you showed looked like ssl version of admin side - I'm not using ssl for admin mgmt as of yet just port 8080 http until I can figure out what I want there!


    Showing Successfully installed / updated.
    testing:
    ... control panel is fine --- all sites now have internal error 500... no bueno...
    rolling back again to get sites back online...


    I'll just hold off for a bit... sure its something on my end - obviously "I" have plenty of issues to work out!!!!

    Wheezy 7.11 with php 5.6
    noticed errata doesn't include editing any more if you're on higher php levels


    did deactivate plugins - wondering if I missed something else..


    Always grab a backup (snapshot image) before initial upgrade test (and now try to read through errata a little better!!!)


    --- Guessing same issue as previous version need to delete out php-apc line from debian package list.


    error at:
    processing distribution packages


    error was: autoinstaller::adapter:debianadapter::installpackages: could not install packages: Reading Package lists...


    re-ran installer - same error..


    --- Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:


    The following packages have unmet dependencies:
    php-apc : Depends: phpapi-20100525
    E: Unable to correct problems, you have held broken packages.


    autoinstaller::Functions::build: An error occurred while performing build steps



    upgerr.PNGupgerr-01.PNG


    --------------------
    Guessing this is fix from 1.2.x errata (testing now):
    https://goo.gl/bGgo9M
    --------------------


    PHP version in use


    If you're using, either Debian Wheezy or Ubuntu Precise with a PHP version that is not provided by official repositories, you must be aware that the php-apc package has been added in the list of package to install. Because that package is no longer provided for PHP versions > 5.4, you must remove the package from the packages file before upgrading, else, packages installation will fail.
    You can find the packages file inside the i-MSCP archive, under the docs/\<distro\> directory.


    --------------------


    Delete Line # 52 like so: of ..../docs/<distro>/packages-<version>.xml


    Code
    1. <package>php5-mysqlnd</package>
    2. </php5>

    Testing Upgrade again now.......
    ....................................... getting further..........
    Step 5 of 6 still processing correctly (saving persistent data).....



    have to remember / locate sql root password during upgrade - been awhile!


    --- so that was a different problem --- didn't remember root password...


    restoring back to backup until I locate/change original root mysql password - one password that wasn't documented - not sure if it was generated either like some of the others have been.


    ------- still looks good just need more before proceeding it looks like!
    -------------------------
    ---- too lazy to find it - tried decode - no bueno -
    used this method to reset - didn't update imscp.conf with current - hoping upgrade resolves but we'll see!!


    https://www.howtoforge.com/res…otten-mysql-root-password



    ---- seemed to get further but installer just closed out after imscp_user screen nothing else came up just dumped back out to CLI..


    Running again - same issue - dumps out after imscp master user section - probably need to update sql db and that is causing something... doing that now... and trying again


    review of
    /var/log/imscp/imscp-setup.log gets errors shown in source code - not sure how I did that... whoops...

    A SSL cert is normally binded to the domain name.
    If you provide the key and cert file, he is able to create a server with this cert and locally create a host entry for that domain to his own server.
    So he will communicate with your Domain. BUT locally so he can test the SSL on his own local machine.


    Anyway.
    I would recommend to wait for the release of 1.3.0 (what im doing as well, like a dog waiting for his master xD)

    Yes understand how that works -
    However with cloudflare that won't work - I'll probably have to aim cloudflare at his Server IP and fully resolve correctly...
    otherwise will get ssl-invalid when doing hostname to direct to ip locally which is what I use as well for testing many times.


    the cloudflare ssl is an "Origin" cert - (not exactly sure how that works), basically not as secure as a full trusted ssl and trusts that Cloudflare's cert is solid


    so if he applies the SSL keys (sent via pm) - then it won't work as it will require first having the CloudFlare server being the initiator...


    So from there cloudflare "proxies" all requests into your webserver giving it another layer of protection - haven't noticed any issues of slowness and tends to just work.


    https://blog.cloudflare.com/cloudflare-ca-encryption-origin/
    more information here on the process



    Using cloudflare as the Nameservers vs i-mscp - would be really cool if there was api that allowed edits via i-mscp to be made on cloudflare - believe this is what dreamhost just went to but not sure.

    meaning hasn't been released...
    At least haven't seen a release post... figured it was still beta...


    I'll try and grab this week and see how it goes


    ------
    was reading while mobile and didn't see entire post...
    will try and send you the keys -
    trick on cloud flare is a bit different - they filter the IP address of the server - effectively hiding the actual server IP by routing all the data through them - helps with attacks I guess.