Search results

We as paying customers are helping debug stuff that plesk will use to justify price increases.

Something is weird here. Why did this directory change? Did someone set a redirect between 3. and 4.4.?

Would probably be easier to just put one of the working IPs in /etc/hosts.

I got a mail on Sunday and Monday, but not today, so maybe it was fixed? Mail has one line more than yours: /etc/cron.daily/drweb-update: ERROR: Dr.Web Updater: failed to download files ! run-parts: /etc/cron.daily/drweb-update exited with return code 103 Side note: Mail comes from...

Huh? Certificates should be just updated in-place without changing their names.

Isn't the panel served by nginx (only)?

Well, it is, just not targeted. It's become background noise by now.

see Issue - Backup utility and "Failed to copy files" error about .ssh keys

It is stored (birth date), but it can't be modified from user space (intentionally immutable), so there's no way to restore it with tar.

It looks like they bounce, but the bounce notification bounces too, so nothing remains. Normally there should be a line MAILTO="add@ress" so all output of entries below that line will be mailed to that address. Just set a MAILTO= as described above. However it is not recommended to forward to...

That's why you let rsync run and transfer the majority of files, then stop the sql server (maybe web- and mailserver too, but those are a lot more resilient than the sql server; however you'll probably get lots of sql server errors in the logs if you keep them running), and run rsync again until...

Might also a search engine crawler going through all your listing options. In that case you should probably not ban them if you still want to be found, but instead adjust the robots.txt and declare links to search pages as nofollow.

The thing is that enabling forwarding to work with spf also allows spamming to work.

It would be nice to have the maillog processed and checked for certain problems automatically: greylisting problems (reattempt for same mail comes from another ip and is therefore greylisted too, if the domain is not already whitelisted) delivery errors due to spf/dkim/dmarc configuration...

The reason is that the uploaded file does not exist in the filesystem. It is assembled on-the-fly from the .tar.gz/zstd archives in the domain subdirectory under /var/lib/psa/dumps/domains/. Those already compressed archives are assembled in a streamed tar archive, buffered by the stream cache...

Is there a blank line before Return-Path:?

Shouldn't the server respond to APPEnd with the size that already exists on the server? This sounds like the transfer is restarting from 0, which would require the whole stream from the start to be cached, meaning that if the interruption occurs late in the transfer, the start won't be in the...

Could you post the full headers from Thunderbird (More -> View Source)? Would be very interesting what's before the Return-Path: header.

No further warnings since that chown.

So what is upstream? You'll need to tell us that part of the directive ... And check the systemd journal for that upstream service.