wolstech

Done. Thank you for the donation.

Yep. This isn’t supported. You’ll need to find a way to use a non-ssl connection.

You're the same user as these two from yesterday, and the account is banned for the same reason (Phishing). Please don't bother making new accounts, they'll all be banned for phishing automatically. https://www.helionet.org/index/topic/37443-account-suspension/ https://www.helionet.org/index/topic/37441-account-suspended/

Actually, after one of our other admins found what appears to be stolen information, these ARE in fact phishing...I just missed the phishing content when I originally suspended them. These accounts can not be unsuspended.

This one's actually a mistake on my part. It should actually be for multiple accounts...not phishing. I just did it alongside a bunch of phishing this morning and forgot to change the reason once they finished suspending. Which account do you want to keep?

Yeah, FTP over TLS does work on Tommy (I use it all the time because SFTP is problematic from work), but I've never had any consistent success with the other two servers (Johnny especially). On rare occasion I've had them work, but they usually either time out or give a login failure. Plain FTP and SFTP almost always work even when TLS doesn't. It's probably load related if I had to guess.

Unblocked. Spaces in your password are known to be problematic with some systems are not recommended. Not sure if it would cause this issue or not, but you could try changing your password if need be. Since you're trying to use SFTP, try manually setting it up. Host name: johnny.heliohost.org Port: 1373 Connection: SFTP (do not select FTP over explicit TLS, it's not supported). Username: chrp Password: Your cpanel password If you create additional accounts, they need to use unencrypted (plain) FTP on port 21 to connect. Only the main cpanel account can connect via SFTP.

Krydos can enable remote access for you. What IP needs access? If you're running the node code on Tommy, you shouldn't need remote access and can use localhost as the server name.

Your account is most definitely not the source, just the recipient. The DKIM will be valid because of the forwarders (both Tommy and Gmail re-signed as the mail went from mailbox to mailbox). The originating server did not sign the email. Also, the Tommy spam filter correctly identified it as spam. I would suggest adding a rule the Tommy filter to discard spam (as opposed to just tagging and delivering it) above a certain score to block these. The email source is actually: Received: from 189-18-165-106.dsl.telesp.net.br ([189.18.165.106]:24249) by tommy.heliohost.org The domain telesp.net.br has no valid content, but Googling shows it belongs to an ISP and is used as a domain for the DNS zones of a dynamic IP address block (further backed up by the dsl subdomain). From the looks of it, some random person using that ISP either has malware and his computer is unknowingly spewing spam, or he's intentionally running a spambot on his own (or a backdoored) PC. The IP address shown is blacklisted by most major spam blacklists as a known source of abuse.

@Byron: Login and display have to match. Changing only the display half can cause weird issues with hosting registration because the scripts don't correctly handle scenarios where the login and display name are different.

I'm trying to understand the purpose of that one...it says it uses Paypal (or stripe) to actually handle the payment processing, so it's not really any different than just accepting recurring donations via paypal (which we already do). They look to just be a middleman between paypal and those seeking donations. With the addition of VPS service and an increase in larger donations though, I wonder if Patreon itself might be more feasible now. In the past their model that penalizes small donors made no sense for us, but we now have quite a few larger ones.

I'm assuming you are running into an error when trying to use Full SSL on CF? Full ssl on CF is not supported when used with autossl due to the nature of the autossl service. With full ssl, the service will not be able to make the plain HTTP connections required for the server to generate and renew certificates. Your best bet is to configure cloudflare to connect to Heliohost over plain http (flexible ssl). Alternately, you can disable autossl and manually install ssl certificates from a source like let's encrypt on Ricky, then use full ssl. Note that you will need to manually renew these certificates when they expire every 90 days.

I see two emails in a mailbox called einsatz, both of which appear to be a test message...

Whatever that script is, it's either broken or way too heavy to run here. Please fix it quickly. Unsuspended.

The domain rydermais.com has been cleaned up. Because of a weird error, I also manually parked it as an alias on your account for you to verify it would add successfully. If it's supposed to be an addon domain, you can remove it and re-add it in cPanel.

You can post it here and we can remove it for you.

Done. You should now be able to log in and your website should start working within 2 hours.

That account's username is actually wayota, is on Johnny, and is archived. Unarchiving...

Devios actually just got moved to Tommy yesterday, he earned his move from Heliomine proceeds. Would he still qualify for the space and immunity?

Well, your lifetime earnings are actually worth about $0.60 in today's market, so I suspect that scoreboard is feeding from a dead API (I didn't build that, someone's just using coin counts from the RGS system and doing math). The good news is that as of last month, there was a point where your coins would've been worth about $1.02, so you technically qualified as a donor just before the market tanked. I believe you're one of (if not the) first persons who wasn't dev or staff to do so. That USD number does not reflect what you've personally earned. The USD number is based on a % of total earnings by everyone, where the % you're credited with is determined by your standings alongside everyone else. Higher ranking means a bigger cut of the proceeds count for you vs. others. Of course, you have to keep mining yourself to not lose your position If you stopped mining and let it sit for a month or so, you'll have something much closer to $0 simply because you will eventually be passed up by others and receive a smaller % of the credit as a result. For reference, a single TRTL is currently worth $0.00002192 (two hundred-thousandths of one cent) as of this post. If you used today's numbers, you would need to mine about 46,000 TRTL to qualify for a free server move.

The DNS zones don't go away if Tommy crashes. However, you won't be able to edit them or reuse the domains in a new account unless we delete the records manually for you. Yes you can redirect a normal domain. Just add it to your account, then go to Zone Editor and change the A record. Subdomains are usually CNAME'd to the parent domain, so redirecting the parent will redirect the subs as well.

That happens sometimes. If the client acts up too much (e.g. AV keeps killing miners, poor internet causes it to go out of sync too often, etc.), the pool IP bans you for 5 minutes due to a malfunctioning miner. Just stopping it and letting it sit will let the ban clear up. I changed your assignment to a different miner since xmrig doesn't seem to be very productive on this PC. Also, where are you seeing $2.27 mined? There's no public earnings report. (Also, $0.07 of TRTL mining is about 1-3 days of 24 hour mining on a high end PC, so odds are what you saw was market price fluctuation).

Support for AUTH PLAIN and TLS v1.0/1.1 have been turned back off. Please let me know if you need anything else.

Try it now. I turned the legacy TLS v1 and TLS v1.1 support back on for exim. Outlook 2007 (actually, anything before Outlook 2016) is too old to support TLS v1.2, which is what all cPanel versions after mid-2018 use by default. As a result, the proper fix here is actually to get a mail client that's not 12 years old. Once we know that this is the issue, please update your mail client and verify mail is sending securely so I can turn these off again. I don't want to leave these options (especially TLS v1.0 and AUTH PLAIN) enabled, they're security risks.

Space increased.