this error means, you have no domain with php enabled or no domains. php-fpm cries about missing at least one vhost with pool.
create a domain and enable php in its settings.
Posts by flames
-
-
default config is just fine
-
-
Nimm die 1.2.2 lieber (achte auf den kleinen vlogger bug), Spalte "domain_dns_status" ist in 1.2.x github version. Diese Modifikation ist noch unfertig. kommt in 1.2.3 raus.
-
- thanks for info, never tested this on ubuntu (added this to the install-howto)
- yep, right. (updated). for those behind a firewall or NAT, don't forget to forward needed port (TCP 53) -
heh, you try to help people, but some of them don't want to read, they want to get everything served on a silver platter in perfect mouthpieces. if they don't, they write sarcastic shit and dislike you for the adequate reaction. i love that, as much as i love diarrhea
-
you still didn't read the thread i gave you a link to. there is a second listener file Listener::Named::nameservers
and yes, the thread is very detailed. do you expect we write for every duplicate question a fully documented answer? -.- -
i gave you already a link, where you can find a listener to modify zones. just read the topic, and modify the listener (Listener::Named::nameservers) there to your needs
-
- cant help with IXFR, need to know more about your setup. how you realize the transfer. more settings.
- what problem with 00_master.conf? it is not a problem, but expected behaviour (just different than before). you can use PanelRedirect plugin or ServerDefaultPage plugin (depends on what behaviour you want)
- yes, i-MSCP overrides your manual changes in configuration files of services, that are used by i-MSCP. if you want to make persistent changes, you can write simple listener files (hooks). read on forum, how to do that and how to use them.1. search Forum, so you find this Listener::Named::Zonetransfer - Zonetransfer to Secondary Nameserver + Howto a listener that helps to provision zones.
2. search Forum, so you find this http://i-mscp.net/index.php/Bo…usly-known-as-hook-files/ here are a lot of examples for hooks/listeners -
Make a simple listener file and put it in /etc/imscp/listeners.d/
So you can automate the changes on setup/update and do even a lot more. listeners are preserved on i-MSCP updates.
For examples look here http://i-mscp.net/index.php/Bo…usly-known-as-hook-files/