Posts by techie

  • PHP Settings does not work properly for client

    Per site selected, it is default option.
    Creating a site with "allow_url_fopen = On" and changing of php settings does not work. As far as I can see, there are two table with related "allow url fopen option". One of them is in "domain" table, the other is "php_ini" table. I can see that there is no problem with "domain" table. All column fields are updated correctly. However, "allow_url_fopen" and "display_errors" column fields does not updated in "php_ini" table.

  • PHP Settings does not work properly for client

    I installed i-mscp (selected php 5.6 with fcgid) from latest branch 1.6.x version from Github I logged as reseller and i created a client domain. When I want to change php "allow_url_fopen" settings of client, panel says that settings changed successfully. However, I can see that "allow_url_fopen" value did not changed in /var/www/fcgi/domain.com/php5.6/php.ini.
    When I checked "allow_url_fopen" php value in the php_ini table, I see that the value also did not changed.


    OS: debian 8.9 jessie / LXC on proxmox
    PHP: 5.6 with Fcgid
    - libapache2-mod-fcgid 1:2.3.9-1+b1
    - libapache2-mod-php5.6 5.6.32-1+0~20171027135825.7+jessie~1.gbpd60169
    i-mscp version: Git 1.6.x latest branch from Github
    CodeName = Alan Silvestri
    Browser: Firefox 53.0.3

  • Billing Plugins

    Nuxwin
    You are the marvelous hardworking man. Everyone,who follows i-mscp project, knows this fact. :)
    I think you can overcome this too.


    Is this in your short or long term plan? Do you have planned due date?

  • Billing Plugins

    I see that all billing plugins (KaziWhcms or Boxbilling) does not compatible with 1.2.17 or current 1.2.x branch.
    They are also not updated for a long time. This plugins are dead or still alive?


    Nuxwin:
    What do you think about i-mscp billing plugins for the future?

  • LXC container (Proxmox) - i-MSCP bind mount

    This is the my error log:


    Servers::httpd::apache_fcgid::mountLogsFolder: mount: /var/log/apache2/test.com is write-protected, mounting read-only mount: cannot mount /var/log/apache2/test.com read-only


    I have already commented
    # mount options=(rw, bind),
    as said in this URL: http://wiki.i-mscp.net/doku.ph…an#behind_a_lxc_container


    my /etc/apparmor.d/lxc/lxc-default.conf is:
    ----------
    profile lxc-container-default flags=(attach_disconnected,mediate_deleted) {
    #include <abstractions/lxc/container-base>
    # mount options=(rw, bind),
    # the container may never be allowed to mount devpts. If it does, it
    # will remount the host's devpts. We could allow it to do it with
    # the newinstance option (but, right now, we don't).
    deny mount fstype=devpts,
    }
    -----------


    Using: proxmox 4.0, debian jessie 8 and ZFS file system.