wolstech

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.

The restriction you're experiencing is intentional. We restrict the email service to 10 emails per hour and 50 per day to prevent users from sending spam or bulk email. The questions posted above by moneybroz will need to be answered if you'd like this limit increased.

Domain added. Please be sure to configure DNS by either using our name servers (ns1.heliohost.org and ns2.heliohost.org) or by using A and AAAA records pointed to the IPs shown in Plesk. The domain may take up to 2 hours to start working.

Your logs are mostly 503 errors, which is due to an ongoing issue involving high volumes of traffic against our webmail service. We're working on mitigating that now. Note that this is different from 502 bad gateway, which is normal when Apache is restarting on the server. That happens approximately every 2 hours and usually lasts 5-10 minutes on Johnny. It's faster on Tommy, and currently doesn't happen at all on Morty due to newer hardware and having so few users and domains on Morty. Static pages will always be fastest because there's no server side scripting, and will typically not be affected by 503 errors. InfinityFree's service is faster for a few reasons: They have a massive for-profit corporate parent company (iFastnet) with huge amounts of money and can afford millions in server costs, so servers aren't crowded. We're a tiny nonprofit with an operating budget of <$10k/year that owns our equipment and has no corporate parent. We can't easily afford more servers. Infinity Free is artificially crippled. Those restrictions tend to mean people don't stick around for very long, and they can't run larger applications if they do. Our free Johnny service and the one-time-donation Tommy plans aren't. To give you an idea, 96% of our shared hosting users are free users, or are one-time donors who donated as little as $1 for lifetime service.

Sure. Account reflux has been unsuspended. It may take a few minutes to work again. The other account can just be abandoned. It will delete itself in time since it's suspended. If you'd like to request it be deleted, please post from its matching forum account and we can do that.

The discord/dmarc/dkim/atproto ones have names, so you need to actually ask for, for example, _atproto.tenkyuu.dev to see it. The file you posted is only the domain itself (i.e. records with no name or with the name of the domain). The root domain shows the same thing as your file: https://dnschecker.org/all-dns-records-of-domain.php?query=tenkyuu.dev&rtype=ALL&dns=google For the named ones, they do appear if you specify their names. For example, the _atproto and _discord ones: https://dnschecker.org/all-dns-records-of-domain.php?query=_atproto.tenkyuu.dev&rtype=ALL&dns=google and https://dnschecker.org/all-dns-records-of-domain.php?query=_discord.tenkyuu.dev&rtype=ALL&dns=google This is the expected behavior for the records provided.

502 is related to Apache restarting and is normal. Should occur approximately every 2 hours and usually lasts 5-10 minutes. If you're unable to tolerate this, you would need to move to Morty, where the Apache restarts currently take under a minute. Note that on Morty, you'll get a 504 instead of a 502 during an Apache restart. 504 on Tommy can happen if your script takes too long. It basically means nginx timed out waiting for Apache to return content, which is usually caused by your website's code taking too long and not finishing. This can be caused by many things, including high server load or badly written code. 503 Service Unavailable is an unusual error to get on Tommy though, and I do see a few instances of that in your logs. I'm not sure what would cause this error specifically. Perhaps Krydos would know?

Account aloneguardspare has been deleted and you've been unsubscribed from emails. If you want the other account removed as well, please post here from the other account's matching forum account to confirm and we can do the same for that one too.

Looks good if I check the actual DNS queries. Our admin tools still show (cloudflare) next to your domain which is why I said that. There's probably a stale cache somewhere on our side, but that shouldn't impact the domain itself since public DNS is showing the right name servers...it's just a UI issue in our admin tools...

You're using Cloudflare so you have to do this yourself. That said, the webmail and www CNAMEs exist already on our servers (they're standard) as well as the MX. The TXTs for the email stuff are generated by a script when you request SPF/DKIM/DMARC if you request email support, no need to supply values as our system generates them automatically. I've gone ahead and done this for you. I especially did not use that DMARC record. You'd be hating yourself if I did...you'll be spammed to all hell by the automated reports (and probably end up suspended for disk space, the ruf can get you thousands of emails a day!), and your sent mail likely won't deliver on reject as most providers already have enough trouble accepting our mail without us telling them to throw it away... This is your zone file on our side. You'll need to use our name servers though for it to actually do anything: $TTL 14400 @ 86400 IN SOA ns1.heliohost.org. heliohost4.gmail.com. ( 2025041701 ; serial, todays date+todays 3600 ; refresh, seconds 1800 ; retry, seconds 1209600 ; expire, seconds 86400 ) ; minimum, seconds tenkyuu.dev. 86400 IN NS ns1.heliohost.org. tenkyuu.dev. 86400 IN NS ns2.heliohost.org. tenkyuu.dev. IN A 64.62.151.106 tenkyuu.dev. IN AAAA 2001:470:1:1ee::2009 ipv6 IN AAAA 2001:470:1:1ee::2009 tenkyuu.dev. IN MX 0 johnny.heliohost.org. mail IN CNAME tenkyuu.dev. www IN CNAME tenkyuu.dev. ftp IN CNAME tenkyuu.dev. webmail IN A 64.62.151.106 webmail IN AAAA 2001:470:1:1ee::2009 tenkyuu.dev. IN TXT "google-site-verification=gP9DbLrjLTsnPdCxCB4aFindIrtjQTovp2uVO5OX_Ec" _atproto.tenkyuu.dev. IN TXT "did=did:plc:q74gsah26xz3q4qoe5ixx5jx" tenkyuu.dev. 14400 IN TXT "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all" _dmarc 14400 IN TXT "v=DMARC1; p=quarantine" _domainkey.tenkyuu.dev. 14400 IN TXT "o=-" default._domainkey.tenkyuu.dev. 14400 IN TXT ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+SDLc/Hl5PNixlC3Z1QqVI5F0WQUTC0wA2GHBtcHm+cqyRxqCWP7OmmV5Z7Vn3nos10c8TB7chpdkPiTVeO53mrpK6ZC9fjhlfFajdLReXJvRhqR+MBCwUEw1IimwFUz35YIRwqJ2bHaqvtjhuH4oOZ45qq79GB9gsc5OGC/A74pvZBOzMt1zYo3BvwUNo2LT" "gcyMDTunY+ZU15PBFyE34tj8iniPctiznyx+MboWzR4FCG/igoSwuksUm591bW8PblllmtUzdIQi7ORn9P+JO+bCW29gJlJ77wxupzvelwUMbi/iNWrCnyVbJVNxHxGQTu4jzvMg74BfIGZ1YErmQIDAQAB;" )

The account igorhelio has been unsuspended, it may take a few minutes to work again.