Thank you, very nice! but there are still some small bugs .. 1. DNS server still empty (maybe there some bad settings in my system..) 2. Harddisk quota. It seems that value has been taken from "Max. number of web domains".
I have just pushed a fix for the quota error to github. However this latest commit also changes how the module works. It now uses the username, password, ss; and port number configured in the server to login to ISPConfig. The DNS servers listed in that server are also the dns servers used when creating an account now. You now only require the ISPConfig server that hosts the web interface in the server group too. So you now need to make sure the Hostname of the server is correct for the ISPConfig system. If you are using test servers like me, then you may need to add entries to your hosts file. Under the server add the dns servers that you want to be used when creating the domain in dns. Update the username and password for the ISPConfig remote user that used to be in ISPConfig Remote Username and ISPConfig Remote Password and if need be, tick the SSL box and override the port.
Does anyone use Site.pro? I have removed a lot of the options from the products module page and I am thinking of removing the site.pro options as I do not think it is likely being used by anyone. Also I have added automated creation of databases and if selected, a db read only user. Havent worked out what to do about the read only database user password yet.
We use it. Have a few customers using it now. Site.pro is one of the easiest site builders out there.
I have just pushed some more changes to Git. I think this is very close to being finished now. So I really need as many people as possible to start testing it out on development systems to find any bugs or errors.
Another small but important improvement. There is now a test connection button on the servers page in whmcs.
I have updated the wiki on GitHub. Can you please pass your eyes over this page and let me know if you see any errors. https://github.com/cwispy/ispcfg3/wiki
I was just about to install, but this says that its not currently suitable for a production environment, how long before this works again?
Depends on how many bugs are found. You could just install only the ispcfg3.php file only to your whmcs server. That should be fairly safe.
Question about the server groups and how they worked before. If I have a multiserver system with separate mail servers and web servers and wanted a plan to only choose a certain set of mail servers or web servers I added them to a Server group and added that server group to the Module settings. It seems this new method does away with that. Lets say I have 10 slave mail servers and 20 slave web servers and I want to only use mail servers 3 & 4 and web servers 4 & 9 for a certain plan. How is that specified? Is it the Limit Template where you have to do that now?
Just found a bug, If there is multiple servers selected for a service in the template, the first one is always being used.
Hi, I get this message : Module Create Failed - Service ID 40 - Error: SOAP Error: email_error_isemail SOAP Connexion is Ok ISPConfig template = 1 Website creation is set ISPConfig DOmain Tool is set AutoSubdomain : w w w Active is set DNS SOA Email Name : hostamaster the other field is default Bests regards, Nico
Did you enter a valid domain name in the product order before you tried to run the module? The error is saying that it is an invalid email address. For more details, check the module log in whmcs.
ISPConfig has checking of things like email addresses etc and if they are invalid, it will return an error like you got. Try using a domain like example.com and see what happens.
so, i confirm : ispconfig doesnt like the tag in email Now i have another error : Module Create Failed - Service ID: 42 - Error: SOAP Error: no_server_error<br /> It is on the create line Array ( [server_id] => [ip_address] => * [domain] => toto.com [type] => vhost [parent_domain_id] => 0 [vhost_type] => name [hd_quota] => -1 [traffic_quota] => -1 [cgi] => n [ssi] => n [perl] => n [ruby] => n [python] => n [suexec] => y [errordocs] => n [is_subdomainwww] => 1 [subdomain] => www [redirect_type] => [redirect_path] => [ssl] => n [ssl_letsencrypt] => n [ssl_state] => [ssl_locality] => [ssl_organisation] => [ssl_organisation_unit] => [ssl_country] => [ssl_domain] => [ssl_request] => [ssl_key] => [ssl_cert] => [ssl_bundle] => [ssl_action] => [stats_password] => fvpG434v7F [stats_type] => webalizer [allow_override] => All [php_open_basedir] => / [php_fpm_use_socket] => y [pm] => dynamic [pm_max_children] => 10 [pm_start_servers] => 2 [pm_min_spare_servers] => 1 [pm_max_spare_servers] => 5 [pm_process_idle_timeout] => 10 [pm_max_requests] => 0 [custom_php_ini] => [nginx_directives] => [backup_interval] => [backup_copies] => 1 [active] => y [http_port] => 80 [https_port] => 443 [traffic_quota_lock] => n [added_date] => 2017-11-17 [added_by] => )
I found why : in the template, we have to select the web server I we just create a default, the field is empty... so... So now i can test and use your plug in. In a first time : nice ! In a second time : i would be great if we can hide all functionnality that are not actived in the setup Example : i want just bill website without mail... i should not see mail button. In your plugin, if we setup two product : one for webmail and one for mail => create two customer in ispconfig or just one ? PS : are you french ?
