wolstech

There's something wrong with the service plans on the server, we think something broke when we make changes to fix the 503 errors that users were seeing... i'll take another look when I get to a computer later this morning.

Usually, the three strikes policy applies to the same suspension reason. Your previous two suspensions were for load, but this one’s for multiple accounts. Which account do you want to keep?

Should be fixed. The subscription was set to the 3000 MB plan but for some reason the quota on your account was still 1000MB. I manually changed it to 3000MB in Plesk and removed the suspension on the subscription.

The initial invite is still going to go to the email on the PayPal account though. You only can change the email address after you have signed up. If you can’t receive email at that address, you would need to provide us the transaction number of the PayPal purchase and we can cancel the invite sent to the PayPal address and send it to your email address instead.

I see the $19 payment you made in our logs, which is $24 of credit. Thank you for your payment. Your account is now moving to Morty...you'll receive an email when it starts and a second one when it finishes. Please read both emails thoroughly as they contain information you may need such as IP information. The move can take several hours to complete.

Host name is incorrect...2steps.gr.helioho:3306 should be tommy.heliohost.org:3306 assuming the database is on your Tommy account. Also, be sure you enabled remote access in Plesk (it's under the settings for the database user, at the bottom)

Since you mention you need this for school and you're one of the many students from your university using our service, the account meglopez2604 which is linked to your school email has been unsuspended.

What errors are you seeing? Error 503 was a known problem on this server recently (should be resolved now), and 502 for a few minutes every 2 hours is normal (Apache restart).

Setting the values that way would cause the domain to not be hosted here. What are you trying to do? Are you trying to use your account only for email?

MX should point to tommy.heliohost.org. You'll also need to create TXT records for SPF and DKIM if you want to be able to send mail. FTP subdomain record isn't necessary as we recommend using tommy.heliohost.org in your client when connecting to FTP. If you want to create it anyway, it should be an A record pointing to same IP as the domain itself. NS isn't necessary if you're using your own DNS. If you want to use our name servers, you would need to change the name servers to ns1.heliohost.org and ns2.heliohost.org. If you decide to do this, let us know, and we can set up the necessary records for email for you.

We turned off webmail on Tommy late last night. Thanks for letting us know that the performance has in fact improved Please let us know if you need any additional help.

Domain added. Please be sure to configure DNS, the domain may take up to 2 hours to work.

Are you sure the app isn't opening multiple connections at once? Some apps are designed to open multiple connections, and these will fail if they cause the limit to exceed 10. If there is a way to limit the number of connections your app opens in your code, I would suggest setting the limit to 1 and seeing if the issue persists. Krydos may have more information about this.

We're working on this still. For Tommy at least, the latest update is that there is a DDoS attack occurring against the Roundcube webmail service again. Bots keep hitting the Roundcube pages, causing it to run constantly and hog all the PHP slots. This results in 503s when there's none available for actual websites to run. The removal of webmail service is reportedly being tested and considered as a solution since prior efforts to block the bots have been unsuccessful.

We don't know what's causing this problem, but it affects everyone on Tommy and Johnny. It started a few weeks ago and we initially thought it was affecting only a few users and was related to a DDoS against our webmail service, but that doesn't seem to be the case as the issue is now widespread. Investigation into this issue is ongoing. Please see this News posting for more information and updates as they become available: https://helionet.org/index/topic/64305-503-errors/?do=getNewComment

If these are student accounts, do you have a school email address we can attach to your accounts so we can exempt them? We need one student email address per student account, so please find out which account belongs to which person and provide a list of whose email goes to whose account. Also, tecandsoft already has a replacement account on Tommy (tecandsoftsrv), so it cannot be unsuspended without suspending the new account. The policy is one account per human being, not one account per server.

For MySQL you actually do this yourself. It's in the database user properties in plesk, at the bottom.

Krydos can do this for you.

This is going to be a Krydos question...

Users have a concurrent connection limit of 10 for mariadb, so this would be a reduction.

Yeah that's the impression we got too. It's not code or account specific. Many users are seeing them at random. Logging has been enabled on the servers to try and find the cause. As of now, we know that Tommy and Johnny are affected, but Morty isn't.

int(components["port"]) Considering the value mentioned looks to be a port number, you probably just need to set it somewhere...likely to 443. None (null) does not meaningfully coerce to int in Python (unlike some other languages such as PHP where (int) null = 0). Aside from just setting the variable to start with, your fix would be to use an if statement to check for components["port"] = None and set it to a number.

If you enable Node through Plesk and let Passenger handle it, the server should start it when needed and kill it when it has no traffic. This only works for apps that receive HTTP traffic though. Passenger launches the app when the traffic comes in, and kills it after a period of inactivity. If you start it manually with npm run start or similar, you have to contact support and ask for your processes to be killed. There is no way to kill a manually started node process, and as a result, our typical recommendation is to never start a node process manually. We do offer VPS service with full SSH root access if you want total control over the app: https://heliohost.org/vps/ Those start at $4/month and come as an empty linux VM. You'll need to install node and anything else you need.

I'll guess you didn't read the instructions for that test completely... By "real email", we mean an actual message you've sent someone, with a body and subject. You sent an empty email... -2.344 EMPTY_MESSAGE Message appears to have no textual parts and no Subject: text -1.767 MISSING_SUBJECT Missing Subject: header Add a subject to your message! -1.985 PYZOR_CHECK Similar message reported on Pyzor (https://www.pyzor.org) https://pyzor.readthedocs.io/en/latest/ Please test a real content, test Newsletters will always be flagged by Pyzor Adjust your message or request whitelisting (https://www.pyzor.org)

Please check your PMs for information regarding your Lily account.