Search results

Hi Nik, Answers to your points. Manual backup works 100% - zero errors. But this was on a smaller subset of data. I've tried removing and re-adding Dropbox in the past, didn't seem to make any difference, but I can try again. I've changed the [ext-dropbox-backup] values to those suggested...

Hi... To further bolster security, I'd like to turn off scripted sendmail on most of the domains I host on my server, aside from one or two. Is this possible? OS: CentOS Linux 7.8.2003 (Core) Product: Plesk Obsidian Version 18.0.35 Update #1

I have updated my server as advised - all the latest releases. I have performed a smaller, manual backup for a single customer to Dropbox and it all worked perfectly, with zero errors. The full server backup is still generating a massive file on Dropbox too, but the errors keep coming after it...

A side Q: In the Extensions Library, there's the "Backup to Cloud Pro" option. Would this be a wise investment? Or will I experience similar errors...

INFO from the server: OS : CentOS Linux 7.8.2003 (Core) Product : Plesk Obsidian Version : 18.0.34 Update #2, last updated on April 1, 2021 07:05 AM Dropbox Backup Version: 4.1.2-46 I do not prepare any backups manually, they are performed solely within the Backup Manager. I'll update to...

I have the following error on the Plesk Backup page: "Warning: Could not display the list of backups in the Dropbox Backup storage: Unable to get dumps list: Transport error: Extension transport: ext://dropbox-backup/server:. Please check the storage settings." In addition, for the past...

I just checked my plan... I have 30 days worth of versions I can restore.

Hope this helps! As a rule, Dropbox retains versions of files that are uploaded. If you tap on the three dots to right of the file and choose history, you should probably see various versions of the file, and the date they were uploaded. I thought the same as you, but seeing as Dropbox retains...

Hi Jan, AFAIK fail2ban was working fine... It was the recent update to Plesk that caused the problem? Unless I've got things the wrong way around in my head of course... As for running CentOS 6.6 rather than CentOS 6.7 as you said yourself, "...is a bugfix and new functionality release, not...

I have this same problem... . Plesk v12.0.18_build1200140606.15 os_CentOS 6.6 (Final) . fail2ban 0.9.3-1.el6 What did you break, and is there an eta for it to be fixed without having to do the hacks above?

Could you expand upon what tempfail will cause to happen, specifically? I would like to know if my clients emails will get stored and eventually get sent out, hour by hour... or if they'll have to re-send any 'failed' messages from their email software (Outlook / Thunderbird) again. Many thanks!

I thought that only affected draining bathwater? ;)

If we set an account to have a maximum of 10 emails per hour, and the user sends 24... ...what happens to the remaining 14 emails? Do 10 get sent in the following hour... and then the final 4 in the next hour? And if they send another 5 in that second hour, will this additional 5 get sent in...

Have you tried re-starting Postfix? Does this reset the limits?

Good question... :)

This makes no sense at all... Security wise, you'd want your default limits per hour to be low server wide, and then allow exceptions for clients who can justify needing to send lots of mail. Why would you want the server default to be huge per domain, and then clamp down on individual accounts...

My System: Plesk 12.0.18 & CentOS 6.6 with PHP 5.3.3-46.el6_6 I changed the following in /etc/php.ini and restarted Apache; ; Log all mail() calls including the full path of the script, line #, to address and headers mail.log = /var/log/php_sent_mail.log This should log all PHP mail() usage...