Search results

I don't think there is going to be a resolution for this. Plesk is making a headObject call to the Bucket + Path, I presume to check for existence - on B2, this throws a 404: It throws a 404, so everything halts. I presume this is related to Backblaze's implementation of s3 - folders are...

My needs and preference will differ from yours, so my preference is irrelevant :) Consider if you have the in-house expertise to maintain and optimize a server for high performance or the budget to properly outsource this. Otherwise, a managed WP company might be the better option.

Funny that you mentioned this - we found this out the hard way a few days back while testing DR and couldn't get the "Path" to work yet. I was going to submit a ticket but didn't get a chance to hash out a full report. Or maybe it's a missing config option. I'll look into it later today

I think it's worth asking. I presume 192.168.0.1 is your gateway and also what shows up for other traceroutes?

Common misnomers: - Fast hosting will get you great PSI/CVW scores - That PSI actually matters (it doesn't. Google doesn't use your PSI to rank your site, rather CrUX data) To answer your question directly: If budget truly isn't a major concern, there are a lot of a "enterprise" WordPress...

Funky routing? Firewall? There isn't a tool that can tell you the cause because there is so much that can go wrong :) You have to start somewhere, eliminate possibilities, and work your way up. For one, I'd traceroute from another server that mailtester does work on, to see if that's a red...

Given that it literally says: It is now possible to add and manage DNS records (including TTL) in a DNS zone via REST API I'd try a POST request (maybe Plesk didn't update their reference? ) or contact Plesk to clarify

The best way for you to answer that question is to measure it. Given, I'm not actually familiar with how Plesk takes it's backups, but there might be something in the docs or someone else can chip in. From what I'm seeing in our data, it looks to be subscription-based.

deny x.x.x.x in .htaccess for just one site. Can put that in a global config file for multiple. You can also block off all connections with a firewall (ie, iptables) Configure a WAF under Tools + Settings -> Web Application Firewall (Modsecurity)

Blocking IPs post incident does little. If you find suspicious countries or ASN, you could consider a full block, but even that doesn't do much. IPs are just too easy to rotate out and away. Consider a WAF - either Cloud/Serverside

It looks like a memory issue. What is the resource usage like during the backups?

Take a look at this: Using multiple "myhostname" in postfix

Do you have some modified setup that would change the cache behavior? I'm seeing: Which means the browser won't cache the page

Is remoteip properly configured for CF?

Have you taken a look at this: DBD::mysql::INSTALL - How to install and configure DBD::mysql - metacpan.org

You should also have p3306 blocked from 0.0.0.0/0 anyways....if you need remote access do it over a secured tunnel.

You can change the behavior under Database Servers to default to local only I wouldn't consider this a bug

What's your use case for varnish over, say, NGINX FCGI?

There is no set rule. I'd reference my previous post on another thread: Static files don't use PHP processes, so that's irrelevant - NGINX/HTTPD handle that load and it's mostly minimal. To understand how many PHP processes you need, you'd have to understand why you have them; each PHP...

10 is likely too high. Issue with large mem + post size stems from things like $_POST being memory bound, so if someone submitted 500 MB of data, it would be allowed with a 700 max_post and mem_limit, and then now you've got a PHP worker using 500MB of memory. Repeat that, and you're server...