Hi,
for me this solution works
I've modified the fpm pool as said by Nuxwin
and edited the .htaccess with
With this mod, you must to disable the php permission editing for the user, because, if they make a change, the pool will restored without the security limit setting
service php5-fpm restart
And now the .html file can run the php code included
Bye bye
Hello.
I confirm, I also use fail2ban to fight bruteforce attacks
Hi,
I have implemented a little change to the Spamassassin plugin
Many users have informed to me that they received too much spam, even if it was properly stored in the Junk folder.
Many of these emails have a very high spam score, much higher than 10 points. Looking at the spamass-milter demon options, I see that it's possible to reject the mail if the spamassassin score reaches a certain level.
I have edited the file /var/www/imscp/gui/plugins/SpamAssassin/config.php:
Quote// Don't change anything, if you don't know what you are doing!
'spamassMilterOptions' => '-e -f -I -u spamass-milter -r 10',
In this way, all the emails that reach or exceed the 10 points of spam are rejected
Updated / Reloaded plugin in the i-MSCP panel and it works
I think that it can be interesting for many users, it can be implemented directly in the Spamassassin plugin as an option?
Thank you very much
Hi,
for the others that use ubuntu 14.04, i've found a problem with proftp
Sometimes, i've found that the proftp service are stopped.
This problem could be caused by the logrotate service
I've applied this solution and now it works correctly
The workaround is to edit the service file, to add a retry and sleep.
/etc/init.d/proftpd
Find this line:
start-stop-daemon --stop --signal $SIGNAL --quiet --pidfile "$PIDFILE"
Change to this:
start-stop-daemon --stop --signal $SIGNAL --retry 1 --quiet --pidfile "$PIDFILE"
Source: http://stackoverflow.com/quest…x-logrotate-restart-error
I hope that this can help someone
Bye bye
Display MoreRoundcube Plugins are not compatible with latest i-MSCP.
I don't know, when it will be updated to work again with I-MSCP.
Nuxwin: we should ship Passwort Changer seperatly, because i don't beleave that RC Addons Addon will be updated in near Future.
Maybe we should add it as default to RC Repro
Hi,
I don't have found a problem to install this plugin in the last version of i-MSCP
I've upgraded a prior version to the newest and i've also installed a new server without problems
My i-MSCP configuration:
System: Ubuntu 14.04 (trusty tahr)
i-MSCP Git 1.1.x Build: 20140915
Server implementation: Apache/2.4.7 with php5-fpm 5.5.9 , dovecot 2.2.9
Hi,
for me this plugin does not work. 
I have followed the tutorial to install the plugin, but when i call the url created, the page showed is blank.
This work only when i call https//my_domain/cgi-bin/mailman/admin/mailing_list_created and, also with this url, works correctly only with the mailman mailing list. Using the others mailing lists created, the urls in admin page it's incorrect. It links, eg, to https://my_domain/admin/mailing_list_created/members that show i-MSCP Error 404
My i-MSCP configuration:
System: Ubuntu 14.04 (trusty tahr)
i-MSCP Git 1.1.xBuild: 20140915
Server implementation: Apache/2.4.7 with php5-fpm 5.5.9 , dovecot 2.2.9
Thank you very much
Hi,
I have found a little problem when sending a email from the control panel.
I have customized the text when sending the welcome message.
I have also created some hosting plans and initially I have configured that the hosting plans are available for the administrators and not for the resellers
Using these settings, when I create a new domain, i-MSCP sends the mail successfully with the text that I have customized. However, if (e.g.) I change the domain user password and send back the login information to the user, the email is sent with the default text of i-MSCP and not with the one that I have customized.
Configuring, instead, that the hosting plans are available for the resellers, the problem does not occur and i-MSCP sends the e-mail with text that I have customized.
My i-MSCP configuration:
System: Ubuntu 14.04 (trusty tahr)
i-MSCP Git 1.1.x
Build: 20140915
Server implementation: Apache/2.4.7 with php5-fpm 5.5.9 , dovecot 2.2.9
Thank you very much
Hello,
I do not think that you are stupid and I do not need to cry, I have confidence in the project and the people who work there, otherwise I would have used an ispconfig, plesk or cpanel.
Ok, at this point I can say that I'm wrong I to use the git stable channel, I have not read the information that the channel "stable" was actually "beta"
I have read that the stable channel it's used for the maintenance of the upcoming new stable release, not thinking that it was beta code but stable code with bug fixes for the version currently in use
Git Master user please, consider to no longer use it
And the last time that you helped me, Nuxwin, you have asked me to perform the upgrade by using the git stable channel, it is precisely for this reason that I used the stable channel for new installations and for upgrades
Sorry for the inconvenience
Thank you very much
Hi,
I'm sorry, but I do not understand your position. First of all, mine was a consideration, and I believe that many other users of imscp can be in the same situation. For a release of maintenance I think it can be too much a change like this. Do you have any idea what it means to tell to a thousand users that completely changes from day to day the access to services because it has been made an update? A MAINTENANCE update??
As I said before, I think this is still a very good choice, but you also have to think that those who decide to use imscp, should not find "surprises" that can then be difficult to manage in a short time and may cause damage or disruption.
I think that the release of maintenance should keep the same characteristics as the previous one and make some bugfix or introduce minor improvements, while in the newer releases (such as 1.2.x), you can introduce new features and other changes, in terms of graphics or core or more.
I was wrong to do a upgrade using the stable channel?
Thank you very much
Hi,
on a VM, that I have not yet put into production, I did the upgrade by using the git stable channel
I've seen that i-MSCP now uses a different port for the admin panel and uses ngix as webserver
It 'a great choice to use a separate web server for administration panel and another for the actual hosting sites, however, in my case, involves a problem.
I have configured the I-MSCP using SSL and now after the update works on port 4443, I have created a generic certificate using StartSSL. I have created the redirects for web services such as webmail, ftp, mysql.
Now I think that those who have used the webmail on the VM that I have in production, he saved that address in your browser's favorites and if I did the update on these servers could create problems for users because they can no longer find the address of the webmail
The redirect is set to this simple work
http://webmail.example.com ---> https://my_imscp_url/webmail
In doing so I can use a single certificate for all areas that require secure access
With the new configuration of I-MSCP I can also use a single certificate but all the addresses have changed because they use a different port
The cost of a multi-domain certificate is high but still not solve the problem.
IMHO the solution that may be the best and that does not create too much inconvenience to users, would be to manage I-MSCP using ngix and other services using apache
Example:
I-MSCP Control Panel: https://my_imscp_url:4443 (ngix)
Default site on I-MSCP: http://my_imscp_url (apache)
Webmail: https://my_imscp_url/webmail (apache)
What do you think about?
Thank you very much
Sorry for my bad english
