Posts by DragonZX

  • SQL error on domain recreation


    Yes, yes and yes, but there was no answer for me, if i need to delete this entery "by hands", so "I can't connect to MySQL" to view it.
    Another question is - why do we have such error at all.

  • SQL error on domain recreation

    Now i have strange thing. My customer give me the abuse about his domain (virtual. After backup we made a desidion to recreate an account).
    But on the third step of creation (in the debug mode).

    Code
    1. An unexpected error occuredAn exception has been thrown in file /var/www/imscp/gui/library/shared-functions.php at line 2532:SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'domain.tld' for key 'admin_name'Query was: INSERT INTO admin ( admin_name, admin_pass, admin_type, domain_created, created_by, fname, lname, firm, zip, city, state, country, email, phone, fax, street1, street2, customer_id, gender, admin_status ) VALUES ( ?, ?, 'user', unix_timestamp(), ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )


    In the debugger - "i-MSCP Daemon tools -3 Execute requests" and "Daemon request successful."
    Without any changes


    Can't connect to the MySQL root using pma, in fact

    imscp.conf


    PMA told me "No mysql connection"


    Any ideas? ?(


    i-MSCP 1.2.0 Debian 7.7, Mariadb 5.5.41-MariaDB-1, php 5.6.4, php-fpm

  • Нужна помощь!!!!!!!

    Включите отображение ошибок в настроках панели. Что там пишет?
    И это простите лог чего?
    Warning как правило не означает ничего критичного.

  • [not a bug] version 1.2.0 needs a redirect

    Quote from Nuxwin

    Re;


    When you use ISPConfig, do you say: It's a bug because the panel is not reachable on common ports? It's a change, not a bug ;)


    Аgree with you in such case, but in the other hand the problem is in the page, which resolving the 80 port. There may be to ways of redirection/resolving
    - To the hoster's site
    - To the panel site
    Now it is resolving the first virtualhost by alphabet (then the clients site), which is not good for the SEO, etc... Also it can be changed if we have alphabetically less virtualhost... It's not good.

  • [not a bug] version 1.2.0 needs a redirect

    I've just updated to 1.2.0 on the production server. Works great but:
    Admin panel is accessable at x.x.x.x:8080, but customers uses panel.mydomain.tld (without ports)
    Now on this domain I have the first alfabetic virtualhost. Maybe we need a redirect to 8080 or error 403/404?
    Then maybe we have to use another port to the main panel at all? x.x.x.x:12000 i.e.?