Search results

Just cause I'm curious, what exactly were you expecting from Plesk here? That's kinda like if I were to make a post asking for someone like Peter to make me a cheeseburger, the error you're having isn't exactly relevant to Plesk, Plesk is simply notifying you of a connection issue with the host.

Sounds like it's possibly the subscription limit, not the disk limit.

Sounds like you're looking to disable php's mail function essentially. Check this out; https://www.plesk.com/kb/support/how-to-disable-php-mail-function-for-a-spamming-domain-on-plesk-for-linux-server/

I'm an independent Plesk user just like the majority here. You're right on one thing, I literally can't do anything. :D That's about all you're right on though with this statement.

Do you have outbound port 80 and 443 open in your firewall? You able to curl any domains whatsoever?

Why are you coming at Plesk making demands and being rude in the process? Um. This doesn't even fall on Plesk. You're under the assumption whomever's account is doing whatever you're accusing them of, is the same individual that is the Plesk license holder / actual server owner, completely...

At 500 zones, you can actually contact AWS for special pricing.

What's the timezone under Tools & Settings > System Time?

I would do exactly what you said. I'd do like a 1GB boot, 8GB SWAP, rest in /, no home. Edit; these directions mention CentOS7 but it's exactly what you're looking to do and identical in Alma. Check home though first, if it's empty - skip step 1, 7, and 8. Resize root partition (or how to...

check this? https://support.plesk.com/hc/en-us/articles/12377014560023-Error-while-backing-up-a-subscription-in-Plesk-Unable-to-back-up-files-owned-by-system-user

Tools & Settings > Security Policy > Secure FTP - set on one of the first two choices? Edit - Another thing, make sure passive ports are open; (Plesk for Linux) Configuring Passive FTP Mode

There's no point essentially of having two IPs if NS1 and NS2 are both resolving to the same server - You might as well just use a single IP and point both NS1 and NS2 to it. Since you're already using R53, one option would be to setup the plugin; Amazon Route 53 - that would allow you to use...

If you do end up going with Alma, I would review the limitations for Alma9 at https://support.plesk.com/hc/en-us/articles/12376955168919-Does-Plesk-support-RHEL9-AlmaLinux-9- before deciding between Alma8 or 9.

Should be under; Domains > example.com > Apache & Nginx settings > Additional nginx directives: client_max_body_size 128m; Adding the above should do the trick.

If you added it as as subdomain first, you likely have another A record in there for it pointing to the IP of the Plesk server. You can simply remove the subdomain. Since you're not hosting it on Plesk - you simply just need to add the A record only as Peter mentioned.

error log is just warnings so not really a concern there. you could have possibly triggered a temp IP block in your firewall, and by the time you rebooted enough time had lapsed. pretty much shooting in the dark here though.

So with a default page, that generally indicates DNS is correct, and it's an apache config issue. First thing I would do is restart apache. If that doesn't work, I would run "plesk repair web" as explained here; Plesk Repair Utility: Web which will rebuild the configuration.

Beta 3 is out by the way which may address this, however, I personally didn't have that issue with Beta 2.

Issue is Debian 9. You need to update your OS. https://docs.plesk.com/release-notes/obsidian/software-requirements/#s2-1

You can just trial license the new machine, and move the existing license over after. Generally what I would do.