Beiträge von ñull

Ich habe im Zabbix-Forum eine mögliche Lösung für dieses Problem gefunden. Anscheinend muss ich einen virtuellen Host für diesen Dienst konfigurieren. Meine Frage ist, wo ich sie am besten ablegen kann, damit Liveconfig sie nicht überschreibt?

Wie verhindern wir, dass es dabei zu Problemen kommt? Hilft es, das Zertifikat zu löschen und ein neues zu erstellen? Wird Liveconfig rechtzeitig ein Tool zur Massenaktualisierung bereitstellen?

https://techcrunch.com/2021/09/21/lets-encrypt-root-expiry/

When a machine in question travels it can have either ipv4 or ipv6 or even both, depending on the connection. What are the myip and myip6 values to remove the A or AAAA record when there is no ipv4 or ipv6 address anymore or when the dynamic DNS zone should only point to the machine when it is necessary?

Apparently it is possible to create a zone without A or AAAA record because that is what I see right after creating a new Dynamic DNS subdomain before I set any dynamic address. I tried some myip values but I found none that would remove the invalid record. I can only update to new values.

I considered using the values 127.0.0.1 and ::1 for this but after reading the related policy I don't think I am allowed to use these because my case is not among the listed exceptions. I think the only valid option would be when the invalid record is removed from the zone.

BTW I don't mind when you answer in German.

The FTP management has a bug that allows you to create FTP accounts while no FTP service is available to be configured. This results in a "not yet created (an error occured)" status message and then disallows deleting the created FTP accounts. Better would be to disallow creating any accounts or even remove the whole "FTP Accounts" table. What is not possible should not be allowed.

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 chunk

I 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

Thema

.http.conf in Proxy and skel support

Thread
forum.liveconfig.com/thread/?postID=13206#post13206suggests the use of a proxy domain to use LE certificates for LC itself, taking away the administrative hassle of updating and manually installing valid LC certificates.

From apache 2.4 the default setting is that peer certificates are checked for errors, which makes the proposed proxy solution error out on localhost and anything else that can be wrong with the LC certificate, expiry for instance. I could only get it working when LC had a…

ñull

22. November 2017

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?