wolstech

Can you please find out who the other account belongs to and have them contact us as well from the email address on their account? We just need to confirm there's 2 people here and both accounts can be kept.

That works. If it will only be used for personal use and not for bulk email, 100/day should be plenty. Limit increased. Note that multiple recipients on a message do count as their own email (for example, if I send one email to 4 friends about a party...that counts as 4 emails in our system, not 1).

It works because you installed a real publicly trusted cert instead of CF's origin cert. Whether it plays nicely for IMAP will depend on the client you use. If it's working, feel free to use it. It definitely doesn't work with all clients though, which is why we recommend using morty.heliohost.org. If you come across a client that won't connect using your domain as the server, this is the first thing to try. Once the certificate takes effect (about 90 minutes from now), you can try turning the CF proxy back on for the main domain record (giuliodinatale.it) and the www CNAME record, and testing with the security features you mentioned. They should work Be sure to leave the proxy off for the mail.giuliodinatale.it and ftp.giuliodinatale.it domains. CF does not support proxying mail and FTP services, so they will break if proxied. By the way, you exceeded your mail sending limit of 50 per day while testing and the server disabled your ability to send email. I went ahead and turned that back on for you. Please be mindful of the 50/day sending limit going forward. If you need more emails due to sending bulk messages, there are some questions you'll need to answer and we can have the limit increased.

Leave the name servers set to CF for now since you already have that set up. Turn off the cloudflare proxy for all records you have set in CF. This effectively just turns CF into a DNS server with no fancy features. Update the DNS records as above: Change the MX to morty.heliohost.org, and the SPF to the one I provided. Change the p=reject in the DMARC record to p=quarantine instead. In Plesk, reissue the certificates for your domain using the Lets Encrypt option. Since you have all required DNS records including webmail created, you can select all options except for wildcard certificate (which we don't support). Once it succeeds, wait 2 hours for the certificate to take effect, then clear your cache. After that, try connecting to morty.heliohost.org using a mail client (IMAP and SMTP). Use an email address you created on your account as the username, and the matching password. If it gives an authentication error, reset the mailbox's password and try again. If you get an error, please post the settings you used and the error message. When the emails come back, is there an error message? If so, please post it. Returned mail is usually an SPF/DMARC/DKIM issue.

Please check your PMs for information regarding your Lily account.

The IP not working for accessing your site is normal. It's a shared IP used by thousands of domains and relies on SNI (Server Name Indication) to determine what content to serve. I've added d2.mwl04155.top as an alias on your account. You'll need to configure the Cloudflare zone for that domain to point to the same IPs as the yriver.heliohost.us domain, then wait 2 hours and it should work.

So there's a couple issues here: DNS...sounds like you're working on the NS issue. You'll need your registrar to get the IF NS removed before everything will work reliably. I only see CF when I run tests, but if there's two sets of name servers at your registrar, there's a possibility the wrong server answers and things break. For the zone itself: Change your DMARC policy to quarantine, not reject. SPF should be fine but is more inclusive than necessary. The record we'd use on our name servers for a Morty user domain would be "v=spf1 ip4:65.19.154.94 ip6:2001:470:1:1ee::3004 ~all". Change the MX to morty.heliohost.org at least until we get it working. Most clients won't like using your domain as a mail server even if it is configured correctly simply because do not like being told "connect to mail.giuliodinatale.it" and essentially getting back a response "Hi I'm morty.heliohost.org!". Since the mail server is shared by everyone, it announces itself as the server host name, which will cause TLS validation and client security checks to fail if other domains are used to refer to it. CF origin certificates are notorious for causing issues because they aren't trusted by anyone except CF's servers. Remove and replace this with an LE certificate through Plesk, then wait 2 hours and try again. If validation fails, disable the CF proxy to initially issue the certificate, then turn it back on after the process finishes. Renewals usually work fine as long as you don't enable strict mode in CF. Make sure CF's SSL setting is "Full", and not "Full (strict)". Strict mode is not supported and will cause issues like certificate issuance/renewal failures. Have you tried changing the mailbox passwords for the email accounts after the move? While they should migrate in theory, we've seen passwords not always migrate cleanly.

Krydos can do all of this for you.

The minimum charge is $1/month, so assuming you have no overages due to excessive load (which it sounds like you won't with a basic webpage), you're looking at about 2 years of service for that $19 after the bonus we give for prepaying. Morty really is that much faster, and it has an actual 100% uptime over the last 7 days, in contrast to Tommy's 99.8% and Johnny's 97%. We do offer refunds too (https://heliohost.org/refunds/), you can always cancel it and request a refund of the unused balance, minus the bonus and a $0.50 fee (because Paypal charges us to process a refund), if you're unhappy with it.

Welcome back! Your old account looks like it was lost because it was never migrated to Plesk when we switched a few years ago. In order to reuse an account username, the account must be reregistered using the same email address as before. I've sent an invite to the email address on file for the old account so you can recreate it. Please click the link in that email and follow the directions to finish the registration. If you have any questions, please let us know and we'll be glad to assist further.

Account voltars has been unsuspended. It may take a few minutes to work again. As I said in my last post, please ensure that you and orca never share a computer, network connection, or content, and neither of you should ever log into the other person's account for any reason. Future suspensions for multiple accounts may result in both accounts receiving a permanent ban. Also, apologies for the delays in getting this issue resolved. We're always happy to help, but we need clear answers in order to understand the nature of an account's usage and determine a resolution to these suspensions. Please let us know if you need any additional assistance with your account.

Ok. I'm going to just change the email on the account and unsuspend it instead. It may be a little while because I have to get someone to reset your multiple account detection first...otherwise it's just going to suspend you again. I'll let you know when it's unsuspended.

Thank you for the clear answer. Ok...so your issue is that your friend isn't allowed to do that per our terms of service. Accounts must be created and maintained ONLY by the actual owner unless permission is requested in advance, so the account is in violation simply because you asked him to violate the TOS on your behalf. If you would like your own account, you are welcome to it, but you will need to sign up under your own email address, and under no circumstances are you allowed to share a PC, network connection, or content with him. He is not allowed to maintain the account for you, and you cannot store any content for his website (or vice versa). If we detect this again, both accounts will be permanently banned from our service. Would you like me to delete the voltars account so you can sign up again under your own email address? If so, let me know what email address you would like to use and I'll reinvite you for your own account.

We've been seeing these 503s a lot recently, heavy traffic to the server (including intermittent DDoS attacks against webmail) have been to blame for those. It's caused by the server being too busy with other requests, not really anything you can fix on your part. The error itself "can't apply process slot" basically means there were no process slots left to start PHP when your website was called. I've asked again about these errors in a staff channel since you're not the only one complaining about them, but there isn't a fix for these at the moment besides switching to Morty or buying a VPS and running your own server. Error 504 is usually a result of your script taking too long to execute. This could be inefficient code, or could just be high server load (server too busy to finish within the timeout period). Error 502 if you see it would be Apache restarting and is normal. Usually happens every 2 hours and lasts a few minutes.

What version of Python do you need these installed for?

To access it from a Django app running on our server, yes just localhost. To access it remotely, you’ll use the server host name (tommy.heliohost.org). Escalating to Krydos.

Tracebacks usually dump into the Plesk Logs section if there is one. They're a bit hard to read because of how Plesk formats them, but they're usually there. If you can't find what you need, just let us know and Krydos can check the backend for any additional logs. As for Postgres, there is no management tool and it does not support remote access by default. You have to either install something like Adminer, or request remote access to it so you can connect from a desktop tool like pgadmin and configure it that way. What is the name of the database and database user that needs remote access?

Support is all volunteer and is primarily based in the USA. We were all asleep when you responded. If you post anywhere between 12AM and 7AM (US Eastern time), you won't receive a response quickly since there's nobody available. That said, we don't believe your story either, especially since the supposed owner of the other account has been caught lying to staff previously (which is bannable on its own). If it's your account, you should be signing up on your own, under your own email address, and managing your own account from your own computer. Our terms of service does not allow users to manage another person's account on their behalf without requesting permission before creating the account. Can you explain why the email addresses on these accounts have the same person's name in them?

Krydos indeed has to do this.

Your suspension has nothing to do with inactivity. It's because you used a disposable email address, which violates our terms of service. Please provide a real email address (PM me if you wish to keep it private, or post it and we can edit it out afterwards) and we can update your account and unsuspend you

You can, but you have to watch your load to make sure it isn't too heavy, otherwise you'll end up suspended for excessive resource usage. Here is a tutorial on how to build a Discord bot that runs here. The methods used to start and stop the bot can be adapted for most other bots as well: https://wiki.helionet.org/Discord_Bot

Marking solved since you no longer need a refund. Please let us know if you need anything else.

Since you mentioned it is a VPS, Krydos would have to be the one to look at it. Escalating.

If you would like to delete your entire account, you can do that here yourself: https://heliohost.org/dashboard/delete/

Looks good. You actually sent 75 messages today already. Note that each recipient is one message (a single email sent to 4 people counts as 4 emails, not 1). Since you're only planning to send 50/day and you've already hit 75, I'll make the limit 75 so there's some room over the 50 you said. If you need more, let us know. I've turned your email service back on for you. Please be sure the unsubscribe options are added before you start sending these to actual users.