Search results

More details: https://exim.org/static/doc/security/CVE-2023-zdi.txt

Yes, i have checked that option That's correct. All aliases work fine. As on above yes, on /var/www/html PHP doesn't work and roundcube and phpmyadmin works fine. Thanks for the workaround. I will try it tomorrow and i will post the results here. I hope this will be fixed in the future updates.

Just test it with CURL curl -k -6 https://[IPv6 Address]/redirect.php Results in this output: <?php header("Location: http://".$_SERVER['HTTP_HOST'].":2222"); ?> Via hostname curl -k -6 https://<hostname>/redirect.php Does the normal redirect Via IPv4 there are no issues

IPv6 is linked to IPv4 and working. Connection on hostnames is not a problem on IPv6.

Hello, After installing a new server (with nginx + apache) and checking if IPv6 works i just noticed something weird. in the /var/www/html/ we have placed a index.php that displayed the name of the requested domain. If lookup the website via hostname there is no problem. But if i request it...

Bad news. Still the same error on 1.62.2. 'fatal creating main HTTP server error=newServer failed to initialize TLS certificate cache:'

F.Y.I. 1.62.1 doesn't solve the problem.

This doesn't change anything. Still the same error.

Have you tried to setup let's encrypt for your host again? 'Installing an SSL certificate for your hostname using LetsEncrypt' - https://help.directadmin.com/item.php?id=629

Just put an # before the carootcert= rule in the directadmin.conf and then start directadmin again. I also reported this here edit: You don't have this in your config? Thats strange. Are you using a own cert or let's encrypt?

Since the upgrade to 1.62 DA won't accept the carootcert file and i get these errors (DirectAdmin won't start): The error is a little different: 'fatal creating main HTTP server error=newServer failed to initialize TLS certificate cache: open /usr/local/directadmin/conf/cabundle.pem: no such...

Just an update. I have a few other servers that did an auto update to the latest version on DA. These also have problems with my CA-bundle certificates. In this file is a root and intermediate certificate from Sectigo. The error is a little different: 'fatal creating main HTTP server...

I just comment-out the carootcert rule and directadmin runs fine. So the new DA version has problems with my CA bundle.

Yes i did. Everything works fine like SSL in apache etc. Only DA won't run with SSL enabled on port 2222. The certificate files are not changed. So its a little strange to get this error 'TLS certificate cache: tls: private key does not match public key'

No luck with update and update_versions. This server was installed last week. The update to 1.62 was done this morning. It runs normal with ssl turned off.

After updating to 1.62 I got this error and DA won't run with our SSL certificate. 'HTTP server error=newServer failed to initialize TLS certificate cache: tls: private key does not match public key port=2222' Anyone else got this error?

Since a few weeks we experience a slow DA interface on all servers. Websites are running fine and only DA is impacted. Loading of scripts and images have stalled connections of 10 seconds.. It takes up to 20 seconds to load the home page of DA. Are there any other users that have the same issue?

I have updated directadmin to 1.60.1 and all works fine. Thanks for the quick fix! (y)

Yes an IPv6 that is linked to the IPv4 address. To be correct Under the IPv4 settings the IPv6 is linked

Same issue here. After the update last night nginx stopped with error: nginx: [emerg] open() "/usr/local/directadmin/data/users/apache/nginx_php.conf" failed (2: No such file or directory) in /etc/nginx/directadmin-ips.conf:17 But here is no user apache in /usr/local/directadmin/data/users/. So...