Search results

Are you running on a 512MB server?

Unfortunately, I can only speculate what's wrong. Spam filters are black boxes, especially Gmail. Sending 3.1 messages/hr only shouldn't get an IP rate limited. However, from what I've seen, these rate limits are done on a IP reputation basis. If your IP has a history of sending "good" email...

Got you :) #!/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin CFTEMP=/root/cloudflare-ips.txt curl -sS https://www.cloudflare.com/ips-v4 >$CFTEMP printf "\n" >> $CFTEMP curl -sS https://www.cloudflare.com/ips-v6 >>$CFTEMP sed -i -e 's/^/set_real_ip_from /' $CFTEMP sed -i '1ireal_ip_header...

You'll need to write your own jail filter to track requests by IP. I would just raise the open file limit as a mitigation - you don't want your server going down from the either way. Then consider something like Cloudflare. Rate Limiting is best done as close to the client as possible.

No. Put the files in /sbin, and it will automatically work on installatino

You'll likely need to configure Plesk's serve static files option to not server .js files for the site.

It seems like it would be a lot easier just to use a VPN, temporarily and whitelist your IP.... If you're in rescue mode, you should have CLI access. From there, just use the firewall CLI to make the changes necessary

Yes. That is not created by Plesk. W3 Total is responsible if I recall corectly

This is really one of my biggest gripes. If Plesk offers caching OOTB but not a way to clear it, it's really quite useless except for micro caching. Does Plesk expect everyone to implement purging themselves? I doubt that is properly detecting caching. Look for the x-proxy-cache header to see...

Why?

I can't imagine Contabo has a particularity clean IP range - https://talosintelligence.com/reputation_center/lookup?search=173.249.25.59 Spam filters are black boxes and there are a lot of factors. However, I'd look into getting a relay from somewhere that probably has a clean IP range.

The data has to get into Plesk somehow. Unless you can walk into your DC, pull out the drive, transfer the data and put it back in, you aren't going to easily get plesk core files into the machine at 10kbps

That doesn't actually do anything. MariaDB won't just update to a minor release by itself.

SInce you're using Plesk, forget whatever is being mentioned about sites-available/enabled It should work if you paste it in the "Additional NGINX Directives." Do you have another rule taking precedent? Ie, serve static files via NGINX

There are some attacks that will slip through cloudflare unfortunately. There is definitely more to do, but it gets progressively more expensive. You could take a look at Sucuri, or StackPath. If that doesn't work, there are other vendors, albeit (very) expensive.

Your code should be: $result = curl_exec($ch); $final = json_decode($result,true); curl_close($ch);

Could you be under a DDoS/resource exhaustion attack?

Mailchannels + Spam Experts are very very popular commercial outbound scanning relays. You could also consider running a separate relay. Postfix has smarthosts support so we just funnel everything to load-balanced external relays that handle filtering for outbound spam. Worst case, an IP gets...

Yeah. Just choose only the remote directly when you schedule a backup in Plesk -> Backup Manager -> Schedule

Uh, what's stopping you from just setting the hostname to the main server's hostname, and issuing a SSL cert for that? Generating custom vhost templates, especially for something like domainVirtualHost.php which we've seen change literally every update cycles is a pretty poor idea usually...