Search results

Okay, I restarted the server, the repair is currently running again (it's still running), but at least mails are working again now. o_O

Admin user, from the overview page. I just realized that I see the scheduled tasks from the Tools&Settings page.. I tried running the plesk repair installation command before that, which resulted in an error and now mails are not relayed anymore: Executing: /lib/systemd/systemd-sysv-install...

psaadm is not empty, looks similar to what you've posted, root only contains: # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/opt/psa/tmp/sssvEV4gr installed on Mon Aug 28 23:03:22 2023) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)

I was deleting backups in my backup manager when I suddenly saw an error message that a task with a specific id could not be run, so I checked my scheduled tasked tab and it is suddenly empty. I do not know what happened. I only had the standard plesk tasks in there. How/why did this happen, and...

Unfortunately those changes do not seem to add a delay to messages - checking the logs, when a client is sending a message to ~100 addresses, they are all sent out at once (logs only show ms in between) - which causes the fork error. Any other ideas?

Sorry coming back to a relatively old topic, but I am having the same issue when sending out a big amount of mails at the same time. Where exactly to I implement those settings in Plesk?

Interestingly, that I was not told.

Yeah, so this was the supports answer basically: At this point, I've configured a large timeout in panel.ini: [ext-firewall] confirmTimeout = 660 ; the timeout in seconds before the configuration is rolled back confirmTimeoutCli = 660 ; the timeout in seconds for the --confirm CLI command...

I had plesk support help me, as it turns out iptables takes forever to process a single command, sometimes several minutes. So applying any new configuration/turning on the firewall from the GUI was impossible. Increasing the timeout to 600 seconds enabled me to at least apply the configuration...

I am having the same issue.. any news on this?

I got the same problem, also Strato as a hoster after updating to Ubuntu 22

Right, I would have expected other posts, too - which I did not find. I'm probably going to reset the vm, restore a backup and see if that helps. I

I still have this issue, maybe someone can help me. Interestingly, before updating to the latest Plesk version, this is how long it took to backup my mails: Now, with roughly the same size, it takes much longer: Any help would be highly appreciated.

I also just got some Plesk errors when trying to view certain pages (did also happen on other pages in the backend, nut just telemetry): TypeError: Cannot read properties of null (reading 'replace') at i (https://redacted/cp/javascript/main.js?1683033466:8:59923) at...

Since I recently updated Plesk to Plesk Obsidian 18.0.52 Update #2 (Ubuntu 18.04.6 LTS), we had a few issues with our server. Everything seems fine now again, except for when I start a backup, it not only basically takes forever (I had to pause the update after ~8hours, the last full backup only...

Well, setting the rate limit to 0 actually reactivated the brute force protection from roundcube. Fail2ban now bans my correct ip Adresse after 5 failed login attempts, but the ban had no effect - I can still continue trying to login in.

So, turned out that since our server is protected by cloudflare, I had to add some extra headers to nginx (see https://support.plesk.com/hc/en-us/articles/360025828373-Incorrect-IP-addresses-logged-by-Plesk-behind-load-balancer-or-reverse-forward-proxy) Now, I can see my ip being put in jail...

Now suddenly banned ips show up in plesk-roundcube (some cloudflare ips), but my IP from my phone is not showing up - is it because my requests that I send manually form my phone are too slow? Although findtime is set to 660, and I have no other setting for roundcube set...

So, I failed logging in to roundcube with more than five tries, but fail2ban does not jail my ip. The config is setup as following (default): [plesk-roundcube] enabled = true filter = plesk-roundcube action = iptables-multiport[name="plesk-roundcube", port="http,https,7080,7081"] logpath =...

Which would not be a problem, since fail2ban is also setup to work with roundcube. Here the limit for example is set to 5, which is not even reached because of the rate limit of roundcube. I am going to test $config['login_rate_limit'] = 0; and going to report back.