Posts by Nuxwin

    The master branch is now reopened for new features and so on. If you want keep a stable state of your i-MSCP installation, we recommend you to not try to update to last master branch.


    A specific branch named first-stable has been created for the maintenance of the first stable release. You can update your installation with it if you want get fixes before the official maintenance releases.


    For those that are not afraid to use the current development branch, they can still use the master branch either to install or update but keep in mind that you will not be able to go back.


    Nuxwin
    the interesting line is the next one: "<Date> logged in - same IP" - this may lead to a false interpretation.
    Normally if I read "logged in" then I think "ok, someone logged in" - and with the IP from Uklraine and the line before - I'm sort of confused...


    /J


    You must read log by log:


    First log:

    Code
    1. 23.03.2012 00:31 Authentication failed. Reason: Unbekannter BenutzernameUser IP: 89.252.58.37


    Here authentication for client with IP 89.252.58.37 failed because unknown username.


    Second log:

    Code
    1. 23.03.2012 00:31 logged in
    2. User IP: 89.252.58.37


    Here , the authentication for the IP 89.252.58.37 is successful.


    To resume:


    Whatever it's same client or not you must simply read log by log. ;) It's not because authentication fail for a specific client IP that this client will fail to next authentication (retry).

    To moderators:


    I think that this thread must be simply deleted since we have not to talk about any ispCP things other than migration to imscp issues. We are not here to be against ispCP. It's another project, nothing more and we must not take care more about it.

    It's not a Debian bug since you can have vhost using fcgid |fastcgi and other mod-php5. After, that also depend of some usage context. At first time, I've also thinked about missing conflict fields in Debian packages. ;)