Wenn man nur einige Parametern hinzufügen will dann geht das auch so:
postfix.LOCALCONFIG = {
['smtpd_recipient_restrictions'] = "reject_unknown_reverse_client_hostname",postfix.LOCALCONFIG['smtpd_recipient_restrictions'],
}Damit bleibt die LC Webschnittstelle betriebsfähig. Es ist auch nützlich zu wissen das man mit
liveconfig --diag
sehen kann ob alles Konform LUA Syntax ist.
Auch ich wäre an einer Antwort interessiert. Ich probiere hier "postfix check" und kriege nur diese meldung:
postfix: Postfix is running with backwards-compatible default settings
postfix: See http://www.postfix.org/COMPATIBILITY_README.html for details
postfix: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"Es scheint, dass dies ein kleiner Fehler sein könnte. Wenn man eine Subdomain ohne Hosting mit nur einem benutzerdefinierten A-Eintrag erstellt, dann wird dieser nicht erstellt oder einfach ignoriert. Die Umgehungslösung besteht darin, die Subdomäne zunächst als "normale" lokal gehostete Subdomäne zu erstellen. Danach deaktiviert man das Hosting und fügt den DNS-A-Eintrag hinzu. Diese Änderung wird dann korrekt aufgezeichnet.
Heute wollte ich eine neue Subdomäne erstellen, aber es ändert sich nichts. Es scheint, dass die DNS-Verwaltung von Liveconfig nicht mehr funktioniert. Was soll ich tun, um dies zu analysieren?
I don't know enough about LUA how to do this. I have done this succesfully for function LC.users.addUser but for function LC.vsftpd.configure(cfg, opts) I get this error in the log file:
Can't run /usr/lib/liveconfig/lua/liveconfig.lua: /usr/lib/liveconfig/lua/custom.lua:78: attempt to index field 'vsftpd' (a nil value)
stack traceback:
/usr/lib/liveconfig/lua/custom.lua:78: in main chunk
[C]: in function 'dofile'
/usr/lib/liveconfig/lua/liveconfig.lua:921: in main chunkI know it is has to do something with the fact that vsftpd.lua is loaded, not required:
LC.ftp = require("ftp")
LC.ftp.load("proftpd")
LC.ftp.load("vsftpd")... but I don't know how to solve this puzzle.
I would like to create a reseller contract where only php-fpm is allowed, while other types remain available depending on the contract. Is this presently possible? How?
I use LC via a proxy to allow me to use Let's Encrypt; it is such a hassle to manually renew certificates!
I will try PMA_DISABLE_SSL_PEER_VALIDATION setting next time I get around to it.
btw2: It would also be nice when you could set certain default records in a DNS template, like the SPF record.
I tried putting the contract setting to YES with zero subdomains and WITH permission to change the DNS records, but when I save it resets it to NO subdomains (without permission to edit the DNS records). I think it should be possible to give DNS customisation permission without subdomains for when you want to manipulate the main domain.
btw. It would be handy when a reseller or the admin were allowed to customize the individual DNS records without needing to give that permission to the end user. The end user TAB seems to be the only way to manipulate DNS records and that while it is may be an advanced feature only meant for resellers and admins.
In my case it is rather:
$ lcclient --diag
...
- PHP 5.6.40 (code='php56')
CGI/FastCGI: /opt/php-5.6/bin/php-cgi
FPM: /opt/php-5.6/sbin/php-fpm
pool config: /etc/php-fpm/php56-fpm.d
default php.ini: '/opt/php-5.6/etc/php.ini'
- PHP 7.2.24 [DEFAULT] (code='php7')
CGI/FastCGI: /usr/bin/php-cgi
FPM: /usr/sbin/php-fpm7.2
pool config: /etc/php/7.2/fpm/pool.d
default php.ini: '/etc/php/7.2/cgi/php.ini'
- default PHP CLI: /usr/bin/php
...
Then I tried again to get it working with fpm and I only managed after manually restarting services like this:
systemctl stop apache2 ; systemctl stop php7.2-fpm; systemctl stop php56-fpm; systemctl start apache2; systemctl start php7.2-fpm; systemctl start php56-fpm
Apparently some 7.2 services remain running which inhibits 5.6 to take charge of the site, at least that is how it looks like to me.
English original should be "site" in stead of "side" : https://www.liveconfig.com/poo…te/hosting.po#unit=108182
Old software needs old PHP but there seems to be something wrong when I switch to 5.6
In the Apache configuration I read:
FcgidWrapper /var/www/<contract-name>/conf/php7/php-fcgi-starter .php
FcgidWrapper /var/www/<contract-name>/conf/php7/php-fcgi-starter .php5
Shouldn't that be?:
FcgidWrapper /var/www/<contract-name>/conf/php56/php-fcgi-starter .php
FcgidWrapper /var/www/<contract-name>/conf/php56/php-fcgi-starter .php5
And shouldn't there be an appropriate php-fcgi-starter file available in that folder (presently not)?
Bitte sehe dazu
In the DNS template I changed the primary and first secondary name. As example, I changed ns1.whatever.com to dns1.whatever.com, likewise for the secondory.
A pre-existing client domain correctly reflects these changes in the master DNS when I use the tool dig. In the slave domain it stubbornly keeps showing the old DNS domain names. Any newly added domain correctly shows the the new DNS domain names in both master and slave.
I tried updating the serial number of the domain, but only after several times deleting and creating the domain I finally got them in sync. This is now still possible before I migrate domains but later, when the sever is in full production, how do a make this change without without having to delete domains?
Must later now I gave it another try and yes it works now.
Any news on this issue?
Here I don't see such DNS template select field below "subdomains", nor any of the other services are editable in an existing subscription. In my case database and webserver are available on both servers but cannot be changed once the subscription is created.
I only see this choice in the "Add new subscription" dialogue box that appears when you click the "New subscription... " button of a client, but in that dialogue I don't see a choice for DNS template either:
https://pasteboard.co/Iz0T5Pz.png
I have two Liveconfig managed servers, A and B. Server A has LC managed DNS-, mail-, database- and webserver. Server B has LC managed database- and webserver. I created a reseller contract with the mail on server A, web and database on server B. I then log-in as the reseller and create an end user contract. I then add a domain for the end user. I only see external DNS as choice. While LC manages the DNS on server A it does not allow me to add domains there.
Is this a bug or missing feature?
I tried the following with success:
- lcclient -k stop
- rm /etc/liveconfig/lcclient.key
- lcclient --activate # asks for the new license code
- lcclient -k start
I also forgot that the choice of server is when the contract is created, NOT when creating the hosting plan.
Apparently by mistake I gave the client server also a Business license, which, according to documentation apparently is not what I should have done. It says that Basic or Standard is "erforderlich". Interestingly enough I still was able to add the server and configure it like normal, only I don't see the new server anywhere available when I attempt to assign it to a hosting plan. Could that be because I used the wrong license? Then why does it allow me to add the server with the wrong license?
If indeed "erforderlich" means that it excludes clients with a Business license, how should I correct my error without breaking the configuration? Or should I?:
- Remove the server
- Change the license
- Add the server again
How would you change the client license? The same as with liveconfig master?: https://www.liveconfig.com/de/handbuch/server.license.xhtml
