Search results

This issue sounds like it scales with traffic (if you always had high wait time then that might point to an underlying infrastructure issue). You can likely rule ot a Plesk-related update problem at this point so when the issue is occurring, it might help to see if the traffic loads are being...

Where you able to actually suspend the subscription? If you received an error, was it similar to this?

Out of curiosity, you placed the log file in a publicly accessible web directory?

If you're a visual guy or gal and just can't get by without a good GUI, you can also use WinSCP which enables you to upload these via a windows-style explorer interface.

The error is accurate; the URL above can't be reached so the certificate can be re-issued. Serving pages again should be the first priority then the renewal process can run.

Plesk generates the notification but the underlying issue isn't Plesk itself. You have a PHP process that is spawning children or exceed the limits of the Amazon instance that you're running so it might be a good idea to check into why that's occurring.

The first order of business is to regain access to your server. Start with SSH if you can't get into your panel and if you're not able to SSH the ask your provider for assistance to regain access (assuming that it's a virtualized server, VPS, or that they can get in).

Very quick fix if that's the case!

Igor might have been referring to bug reports in the special sub-section of this forum (not support requests). Submitting bug reports via the forum does not require a valid support license.

For clarification, this isn't so much of a redirection issue but rather the websites are bound to the wrong IP.

Did you restart Apache?

It's by far a better practice to have your development environment match your production rather than the other way around.

And with that Frankenstein lives!

"Wonderfully Attentive Plesk?"

This isn't a Plesk issue - You're barking up the wrong tree. This is the one that you want: fail2ban/fail2ban

Good to hear - I'm a happy camper if I'm supported until my own EOL :)

hmmm... Everyone raised their hands at once on this one - A bit obscure but have you read into this?

Checkout the HTTP server status module (be sure to restrict it to your IP) but if you're looking just to get a general idea of what's going on: See the top cpu load processes as they happen! # watch "ps aux | sort -nrk 3,3 | head -n 20" Find the process that the ID is attached to: # ls -la...

So your objective is manually setup a domain inside the vhosts structure manually? I'm not sure if this is really a Plesk question as you can do this via SSH just as you would without Plesk and I'm also not entirely sure about the long-term implications.

Instead of using the repair service, have you tried running this command? # find /var/www/vhosts/domaingeneratingtheerror.com/logs/ -type f -a -not -perm 644 -exec chmod 644 {} \;