wolstech

Please check your PMs for information regarding your Lily account.

That's normal for the current version of Tommy (it's overloaded and on old hardware). We're actually in the process of rebuilding the server to deal with multiple issues on Tommy, performance and outdated software being among them. The rebuilt Tommy should be on faster hardware, and will have newer software versions along with several other enhancements we're working on (we're using the empty server to develop those, which is one reason we haven't started moving accounts). Not sure when we'll be moving users to the new Tommy, but I'd imagine soon.

This appears to have already been changed.

Considering your account's content is just a copy of afterlogic webmail, are you sure one of your mailboxes doesn't have a compromised password? Are you actually sending email in bulk (note that 278 sent emails is 278 recipients, not messages...for example, one email sent to 5 people counts as a 5 emails in our system)?

I'll try to get to this tomorrow for you. Been way too busy with real life and haven't had a chance to get free time to do it.

You're suspended for sending 278 emails in one day. The limit is 50. Do you know why your account was sending these emails?

Not quite. Its the load limits we impose that effectively limit it to 70MB continuous. The amount of memory total on the servers varies by server, the load limit does not. Also, if users would use tools like Passenger (a tool that starts apps such as node when requests come in, then stops when idle), they can go a lot further with that memory limit.

Node uses memory to literally sit there and do nothing because it runs continuously waiting for requests to come in. Also, the more modules you load into your app, the heavier it gets. This is in contrast to things like PHP which only run when called...they use 0 CPU or RAM to sit there when they aren't being used.

This has been reinstalled on Tommy. The softaculous one apparently doesn’t work properly, so we might just turn that one off instead.

We don't have a donation from that email address. I just went through every donation we received for a Tommy invite in the past 4 days and there was only one transaction where an invite or account didn't exist (that one has now been sent). The email address on it did not match yours. I've escalated this in a staff channel so it can be researched further. In the meantime, if you're able to get the actual paypal transaction ID (will be numbers and letters together), please let us know as that will make the research easier on our side.

Node is infamous for this...it gets users suspended all the time because of its rather heavy design. Please fix the issue quickly. You can monitor your load here: https://heliohost.org/dashboard/load/ If you get suspended a second time, you'll need to provide a detailed plan for correcting it before you get unsuspended again. Unsuspended. It may take a few minutes to work again.

You were blocked for failed SFTP logins. Please check your FTP credentials. Unblocked.

That transaction number isn't valid, and it doesn't like right either (they usually have letters in them). Make sure you're using the transaction ID from Paypal, not your bank. Also, what is the email address on the paypal account you donated with? We can find it that way as well.

Can you please provide the transaction ID of the donation?

I'll have to take a look to see if it's possible. I think I'm confusing it with the WordPress management tools, which do have similar functionality in both plesk and softaculus. And looking at their documentation, I suspect it may just limited to install and uninstall like other applications are.

You only need one of the two. The configuration shown there supports AVIF (it meets the requirement of "GD extension compiled with AVIF support on PHP 8.1 or greater").

Domains added. Please make sure DNS is configured properly. You'll need to add A records for each of the domains pointed to the IPs shown in Plesk since you're using Cloudflare. The domains can take up to 2 hours to start working.

Domains added. Please make sure DNS is configured properly. You'll need to add A records for each of the domains pointed to the IPs shown in Plesk since you're using Cloudflare. The domains can take up to 2 hours to start working.

It looks like the server may have put the cert back on its own (its configured to do that by default). I just disabled that feature for your domain, if you want to disable HTTPS go ahead and remove the cert again and it should stay that way now. Please let us know if you need anything else.

I always forget that *nix is case sensitive for usernames (Windows isn't...)

You technically can configure a domain this way, but be aware that basically no browser today will be able to access the site if you do. The two largest browsers (Chrome and Edge) prefer or require HTTPS to avoid security warnings, and Google will also not index or promote sites without HTTPS.

These have been configured...I think. First time doing it with these really long DKIM keys. Let me know if it doesn't work.

We didn't announce it, just quietly deleted it (it was quietly added too when it first appeared, came with a Plesk update). It was breaking people's domains (changing document root and a few other settings, that users could then not change back) and Laravel itself was causing tons of load from people trying it. You can manage the existing Laravel installs manually by editing their files or by importing them into Softaculous, which has its own Laravel tools. If you need to remove Laravel, let us know. Removing Laravel completely from a domain requires us to remove the domain from your account and add it back, since the toolkit does a bunch of weird things to domain settings and messes with the document root. If the domain it was installed on was your main domain, we may need to reset your account.

Those are the correct settings. Make sure you're using the username, not email address, for the username. Other than that, I'll escalate this to Krydos to see if he has any additional insights.

Please don't keep trying over and over, doing so will result in the server blocking you completely, which is why everything stopped responding. You've been unblocked. If your FTP account isn't working, try resetting your password. You can also manually change just FTP's password through Plesk.