Search results

PTR should either be set to mail.tompaz.org or the postfix myhostname to "tompaz.org" Just make sure the HELO and the PTR do match up exactly, or you will run into problems when sending emails to certain destinations. The hosts file looks OK and does not need any changes

with this method you will need to check and update these DNS records manually every two months. (the certbot renewal will fail otherwise)

Some questions (or the possible answers) in the Plesk Expert exam do really seem ambiguous. I've skimmed through the Plesk University courses and yes, not everything is covered there in the details that is asked in the exam. But for an "Expert" certification I really don't mind that. I believe...

reinstall the system and copy over the data, as there is no sane way to recover your server. but a "chmod 700 ./root ./root/.ssh" on the mounted plesk partition should at least allow you to login again. (as Ubuntu will not allow an SSH logon, when stuff in the root folder is readable by anyone)

Any file based backup/recovery procedure should "merge" the emails, as Plesk does use the MDIR format to store emails. (every email is a single file with an unique name)

Can you guys test if the segfaults still happen with the new php packages that got released today? Possibly they are related to Segmentation fault on unknown address 0x0001ffff8041 with XML extension under certain memory limit · Issue #14124 · php/php-src

We did not have any further segfaults so far, after we disabled "opcache.jit" and "opcache.jit_buffer_size" (i.e. reset it to server/php defaults) and also increased the "opcache.max_accelerated_files" from 8000 to 16000 But this may not be representative, as on that server the segfaults only...

Nope, this is not a hardware problem. (our affected system is a VMware based virtual machine anyway, that runs a single Typo3 website) I suspect some obscure opcache/Jit problem, that may only trigger under certain conditions (possibly a combination of conditions), like: - usage of a specific...

Just a heads up for everyone affected by it... While I thought that none of our systems were affected, just yesterday we discovered that indeed we have one server showing the same errors for some days now. It's an older system with Debian 10 (initially Debian9 i believe) that is using the PHP...

There are certain caveats, like that your procedure ONLY works properly when migrating to a brand new server and do it all at once. But if you already have some accounts running on the new server, this will screw up big time. The same if you migrate in batches. That being said, it would be...

Your image/screenshot is not accessible (possibly for anyone except yourself) As for the segfaults, I do somehow suspect that this problem may only affect Hetzner customer at most, as otherwise I'm quite sure we would have much more similar reports right now. I've never used any services from...

I strongly doubt that a new setup does change anything, as it uses the same bits for PHP as lets say a server that was installed a couple months ago. If anything, then our setup may slightly differ from yours, in regards to libraries and additional software packages that may or may not be...

Nope, we run our own physical servers and virtual infrastructures Does the problem also happen when using the "OS" PHP version with Plesk? That would eliminate a possible influence of the php compiling process that Plesk uses for it's own shipped versions.

if not for PHP 7.4, I would have suspected that maybe the JiT compiler has some say in this...

already did that, checked syslog on multiple servers (with several thousand websites on it) and so far zero/zilch segfaults on what PHP versions does this happen for you? (we do use deb.sury.org for some, as to have older versions and also longer maintained ones, than from Plesk)

Our Debian 10, 11 and 12 servers do not show any problems with PHP and they are all on 18.0.61#1 Maybe an extension you have loaded and we don't? (we use the default set of plesk)

We've upgraded several servers to 18.0.61 Update #1 (Debian 10, 11 and 12) and so far the internal monitoring tool of Plesk still works on all of them. (we did not enable http3 anywhere)

1) your "proxy_pass http://0.0.0.0:5000" line needs a semicolon in the end 2) you are not allowed to use a "server_name xxx;" in a location {} block

You also need to disable the "Proxy mode" in the "Apache & nginx Settings" and I recommend to disable PHP for this subdomain as well.

Just askin, because we've already installed it on two servers... Something we need to be worried about or look after specifically?