Posts by flames

  • Some helpful wishes

    Quote from oekowalti

    Subdomain
    For the opening of a new domain, which isn't reachable not yeat over the the 'domain.tld' we have a the Alternative URL like 'vu20xx.....' to open it.
    The same funstionalitity would be usefull for subdomains.

    this feature also already exists, but it is "hidden", the interface propagates only the temporary url for main domain, but not for aliases or subdomains.
    in the apache host files every subdomain and alias does have a ServerAlias entry for temporary url like this (the number is the id of subomain or alias)...
    vu2003sub5.serverhostname.tld
    vu2003als2.serverhostname.tld
    the local nameresolver also has the records for this temporary urls (in the serverhostname zone). so you only need to know the id of your subdomain or alias and your (external) nameserver, which is responsible for the serverhostname domain, should have the wildcard record enabled

  • Домены перестали видеть DNS server!!! - Domains are no longer visible DNS server!!!

    Дорогой Серебрист,
    я был в отпуске. у тебя есть мой скайп еще с тех времен, когда я тебе настроил твои сервера (года, примерно полтора-два назад).
    панель i-MSCP находилась и находится в разработке, если ты желаешь поддержку, можешь писать мне в скайп или попросить платную поддержку у разработчика. за предоставление логотипа я готов тебе всегда помочь, и в скайпе я могу тебе хотя-бы ответить скоросрочно. но пожалуйста, не ожидай поддержку в форуме на уровне дорогого платного продукта. все-же тут у нас "опен сорс" так-же как и предоставление логотипа на базе "опен сорс". я всегда постараюсь тебе помочь. да и не только я, а многие тут, но тогда есть минимальное требование: писать по русски абсолютно правильно, что-бы гугл переводчик работал, или-же по английски, что-бы хоть кто-то понял (если меня или кого-либо русскоговорящего опытного ;) администратора нет).
    очень рад, что проблема решена. но я должен добавить, что большинство проблем не связаны с самим i-MSCP, и что при отсутствии опыта по администрации серверов на базе линукс, и/или при использовании неготовой софты (alpha/beta), нужен опытный администратор по линуксу и желательно по этой софте. особенно, если ты планируешь использовать линукс и эту неготовую софту в профессиональной сфере удовлетворяя желание третих людей, т.е. твоих клиентов, перед которыми ты стоишь в ответственности.
    далее, по мере того, что выше названая софта, а именно i-MSCP, находится в активной разработке, поддержка устаревших версий закрывается довольно быстро (иначе не продвинемся вперед), надо обновлять регулярно. да, обновление требует тоже опытного админа и резервные копии сервера на всякий случай (опытный админ всегда делает резервные копии). но мы просто технически не можем поддерживать старые версии. неважно связана проблема с i-MSCP или нет. этот пункт даже не рассматривается!
    Доброй ночи (или как некоторые пишут, доброго времени суток)
    Артур.

  • ServerDefaultPage

    see ServerDefaultPage config, there you can specify another certificate for the default page, so it does not use the panel certificate which is not a wildcard certificate.

  • ServerDefaultPage

    probably the default page where the plugin redirects to. @gable, just edit the file /var/www/imscp/gui/plugins/ServerDefaultPage/templates/default/index.html
    for design changes you can edit also the css and image files in /var/www/imscp/gui/plugins/ServerDefaultPage/templates/default/inc/


    you can also add some javascript to recognise browser language and output the string in right language. var lang = navigator.language || navigator.userLanguage;
    but nobody wants to stay on a default page long enough to read the conetent, just redirect to your site or somewhere else.

  • Update from 1.2.11 to 1.2.17 failed / Column not found

    to fix the DB schema you must do it manually, it is a lot of work. since you tested the 1.3.x development version of i-MSCP we are sure it is a testing machine.
    if it is a productive server, you are totally insane! in that case even a proper backup won't help to fix the 1.2.x DB schema, because it looks like you done it a while ago.


    create backup before you start.


    install on a separate testing machine a fresh debian/ubuntu and a fresh i-MSCP 1.2.17, then you need to compare EVERY FIELD IN EVERY TABLE in the imscp DB manually and do the proper changes to the one on the broken server also manually!


    that means you need to find all fields, that are missing, add them and make the correct settings like fieldtype, null/notnull, defaultvalue, collation, and so on.


    i think i can limit your work a little bit, but not for sure, since the exact nightly build of 1.3.x you had installed is not known.


    begin with the tables:
    domain
    php_ini
    reseller_props
    web_software
    web_software_depot


    after you corrected those tables, test EVERYTHING in imscp, really, test every feature. if you don't receive anywhere "unknown error" then you are lucky, if yes, then compare and fix any other table in imscp DB.


    after you are done, you need to correct also the database revision according to the installed imscp version:
    in imscp database, config table, DATABASE_REVISION field


    good luck xD

  • Listener::Named::Slave::Provisioning - Zonetransfer to Secondary Nameserver + Howto

    Listener::Named::Slave::Provisioning


    This listener file will create a php script /var/www/imscp/gui/public/provisioning/slave_provisioning.php that echoes all zones available on your i-MSCP server for zone provisioning on the secondary nameserver. Optionally a HTTP authentication file will be created /var/www/imscp/gui/public/provisioning/.htpasswd. Read the configuration options in the listener file for further details.


    Author / Maintainer


    Compatibility
    i-MSCP >= 1.2.12


    Howto install

    1. Copy the 10_named_slave_provisioning.pl listener file into the /etc/imscp/listeners.d directory. This listener is available in the contrib/Listeners/Named directory of the i-MSCP archive.
    2. Run perl imscp-autoinstall -dasr named from your i-MSCP version archive and add the slave DNS servers


    How-To install the slave DNS servers (w/o i-MSCP)


    For this case study, we have three i-MSCP servers with the following hostnames and IP addresses:

    Code
    1. imscpserver1.domain.tld 1.1.1.1
    2. imscpserver2.domain.tld 1.1.1.2
    3. imscpserver3.domain.tld 1.1.1.3

    We want to add two slave nameservers with the following hostnames and IP addresses:

    Code
    1. ns2.domain.tld 2.2.2.1
    2. ns3.domain.tld 2.2.2.2

    For each slave nameserver we want to create, we install a fresh Debian Jessie or Ubuntu distribution (base/minimal install), and run the following commands:

    Shell-Script
    1. apt-get update && apt-get install bind9 bsdutils dnsutils cron
    2. mkdir /var/log/named
    3. touch /var/log/named/bind9.log /var/log/named/security.log
    4. chown -R bind /var/log/named

    Once done, in the /etc/bind/named.conf file, we need add the following configuration stanzas:

    Code
    1. include "/etc/bind/named.conf.imscpserver1.domain.tld";
    2. include "/etc/bind/named.conf.imscpserver2.domain.tld";
    3. include "/etc/bind/named.conf.imscpserver3.domain.tld";

    then, we need edit the /etc/bind/named.conf.local configuration file as follows:

    then, we need edit the /etc/bind/named.conf.options as follow:

    then, create the /root/syncdns.sh script as follow:

    Code
    1. touch /root/syncdns.sh
    2. chmod +x /root/syncdns.sh

    with the following content:

    And finally add a cron task by running the following command:

    Code
    1. echo '30 * * * * root bash /root/syncdns.sh' > /etc/cron.d/syncdns

  • CalDAV CardDAV integration for Roundcube webmail

    btw. what is more interesting is a push service, in best case microsoft outlook compatible activesync like https://z-push.org/
    also, as z-push and sabre/dav are both written in php, they might be the most easiest to implement with imscp (i.e. as plugins), so that you not just allow any roundcube user to have adressbooks/calendars but even control them through imscp fine granulated (implementing them into hosting plans). but it needs to be ensured, that they are actively developed and updated. this is currently the case, but i.e. z-push had a really long inactivity phase and community was nearly dead.