Posts by flames
-
-
and since the panel is running on nginx, you won't find problems in apache log. i think you could do well, if you read some ebooks about linux at all, and use search in our forum. and understand how i-MSCP is working.
i want to say, its nice that you try things out for learning purposes. but maybe a hosting panel is a little bit too far away to begin with. you need to understand the basic things first.edit: if you want to host customers, but have no knowhow about server administration, you should start with a reseller (at a managed professional hosting provider) account first. your customers wold issue you in a court, if you mess their sites up
-
check if all services are running, especially nginx. if not, look into the log files. report back when you acquire some more information
-
i bet your sources.list contains "testing" instead of exact codename. "testing" is always automatically the next testing release. change it to jessie and try a downgrade. don't try to downgrade to wheezy, that might be more complicated, because of systemd, and jessie is the recomended release for i-MSCP.
-
On initial customer creation .htpasswd is created with same credentials as the customer. After that the customer can use Webtools / Protected areas to change his .htaccess/.htpasswd credentials independently of panel login.
This is expeted behaviour. In case a customer creates .htpasswd not only for himself but also for other users, those should not be overwritten. -
you have probably orphaned records in your database from older versions. check your db consistency first, then remove the orphaned folders too. -
why not use always for all domains: ns1.imscp.tld ns2.secondarry.tld ?
you can do that, just setup only one nameserver, use it as secondary and use the i-MSCP server as primary.
for my setup it was necessary to setup two separate nameservers, because i have more than one i-MSCP server, and the two nameservers are responsible for all domains/zones on those i-MSCP servers. look into the second listener in howto to understand better.ah, incorrectly understood the question. see the second listener file Listener::Named::Tuning2 does exactly this, it replaces the default nsX.domain.tld against your custom nameservers.
-
-
-
since 1.2.2 policyweightd and postgrey are gone, this might be the reason.
you can use plugins postscreen, spamassassin and clamav.
i suggest, you wait for the very soon release of i-MSCP 1.2.3, update your server and install those plugins.
there are also plugins for policyweightd and postgrey, but those are not needed, when you have postscreen.