-
Posts
18,217 -
Joined
-
Last visited
-
Days Won
696
Everything posted by wolstech
-
All users who were on Tommy will see an erroneous inactive/suspended message if they try to log in. You can disregard it. You're not suspended, you just need to sign up again once the server's fixed. Once we announce it, donors can just re-request an invite, others will need to sign up again for free. See Sohamb03's post for the details.
-
WordPress is infamous for this. The best solution for WordPress issues is not using WordPress. It's garbage software...bloated, terribly written, and full of security holes to boot. Just about every other CMS under the sun is less bloated, less resource hungry, and more secure. We usually recommend using Joomla. Unsuspended.
-
GMX has a known problem with our systems (they reject our emails entirely as spam, even if it's whitelisted by recipient). They're the only ones that tend to randomly do this, others either put it in Spam (Gmail), or deliver it (almost everyone else). Hopefully Luigi's manual email went through, because I do know that many/most of HelioHost's system emails don't.
-
The domain shaverda.com has been cleaned up. Please try again now.
-
[Solved] Add-On Domain Issues (DNS won't clean up)
wolstech replied to jbbdude's topic in Escalated Requests
Awesome. I'll go ahead and mark this solved for you Let us know if you need anything else. -
HelioHost Server Monitor (created by Piotr GRD)
wolstech replied to Piotr GRD's topic in Customer Service
Johnny likely won’t be “moved” in the proper sense of the word, he’ll just be rebuilt again on the new server. It definitely won’t be done while tommy is still being fixed though because we can’t afford to have 2 servers down at once. -
Tommy is not back online, and your account no longer exists, which is why you can’t sign in. Backups are available from https://heliohost.org/backup/ An announcement will be made when repairs are complete.
-
Posts moved. Discussion of server monitor is that way ---> https://www.helionet.org/index/topic/7459-heliohost-server-monitor-created-by-piotr-grd/
-
Please post the exact domain that needs to be cleaned up.
-
Assuming the python can be run in a browser by calling it’s URL and it producing browser-compatible output (I.e. http headers, etc.), call it via file_get_contents() using its full public URL. The function will call the script and return the output for further use.
-
@rajdis: That's high load. That was the same one I had the other day. I tried again a few minutes later and it worked fine.
-
What IP? The 47.30 address in your post headers was only blocked on Johnny for failed IMAP...
-
[Solved] Please remove my Tommy domains so they can be recreated
wolstech replied to flexo's topic in Escalated Requests
The domain hotnova.com could not be cleaned up. root@ricky [~]# /scripts/killdns hotnova.com Unable to remove zone hotnova.com from the Bind configuration (named.conf) on ricky. The zone was possibly removed earlier on ricky. Unable to remove zone hotnova.com from the Bind configuration (named.conf) on cody. The zone was possibly removed earlier on cody. Unable to remove zone: “hotnova.com” on tommy. Unable to remove zone: “hotnova.com” on johnny. Tommy is expected, but Johnny failed. I can't try parking it for you because I can't find your account. Escalating to Krydos... -
Your username was lucasgv. Try using that with the email address to get your backup.
-
That domain is working properly...
-
[Solved] Add-On Domain Issues (DNS won't clean up)
wolstech replied to jbbdude's topic in Escalated Requests
Moving to Johnny won't fix it, it'll need to be cleaned up before it can be hosted again on any server. I'll have Krydos take a look when he gets a moment. @Krydos: Can you manually scrub web.jbbdude.win from Johnny's DNS so he can add it to his account? For some reason killdns keeps failing for Johnny on this domain. Ricky/Cody cleaned up OK and Tommy has no idea it ever existed. -
It's the same as always. They have to be renamed if you want the same username as before. I agree that the system should be modified so forum accounts do not conflict with the hosting accounts. Instead of auto creating forum accounts (and subsequently refusing hosting accounts due to occupied forum accounts), I think it'd be better if the user was asked about the forum account after their hosting is created, and give an option: "Use the same name for my forum account" (shown only if it's not taken), "Use this name for my forum account: <text field>", or "I don't want to create a forum account right now".
-
Tommy is still out for maintenance. The suspended/inactivity message is erroneous and a result of a recent database cleanup that occurred as part of the rebuild process. When the server is back online, an announcement will be made, at which point you can request a new invite using your existing donation transaction to get an account No additional donation is required. If you've created a Ricky or Johnny account in the meantime, we can move that for you instead.
-
[Solved] Add-On Domain Issues (DNS won't clean up)
wolstech replied to jbbdude's topic in Escalated Requests
Oh, you're trying to separate the www. Yeah, you can't do that natively (though as you discovered, there's ways to do it by messing with the DNS after adding the naked domain). The www subdomain is a special subdomain in cPanel. It cannot be added manually because it auto-creates and is always supposed to point to the same thing as the naked domain it belongs to. cPanel always expects example.com and www.example.com to be identical because it's generally considered bad practice for them not to be (many people don't type www anymore, but some people still do, and as such by making this assumption, it ensures visitors see the same content regardless of how they approach it...if it didn't do this, most users here would have no idea how to set it up, or that they even need to). As you said, what you're trying to do is unsupported. The domain web.jbbdude.win cannot be fully cleaned up. Go ahead and give it a try, but the server did spit out an an error saying it cannot remove the zone from Johnny, so it might still fail. If that's the case, I'll put this in the escalated bin for Krydos to manually clean it up. -
Tommy is not back. Your account is not suspended either, it's gone entirely due to the server rebuild. You'll need to wait until the rebuild is finished (there will be a News posting), then you can ask for an invite to receive a replacement account. If you have a Ricky or Johnny account, we'll be able to move that instead.
-
[Solved] Add-On Domain Issues (DNS won't clean up)
wolstech replied to jbbdude's topic in Escalated Requests
The IP of Afraid. cPanel won't accept sub-delegations. cPanel only looks at the FIRST name server in the chain (the GTLD's delegation response, which is usually the entries you set at your registrar), and checks its IP address. It does not follow the chain beyond that point, and could care less what the subsequent server tells it, because it never asks. cPanel queries root->gTLD servers, and the gTLD's NS records for your domain must be a server name that resolves to 65.19.141.3 or 64.62.211.133, or it fails. This check is not a HelioHost decision, it's a cPanel design decision. All cPanel hosts work the same way. Afraid is known for being incompatible with cPanel. Your solutions are: Eliminate Afraid and use us as your DNS provider.Use the domain in question as your main domain (the main domain doesn't have an NS check).Change the NS to us temporarily, let it propagate, add the domain, then change the NS back to Afraid and add the delegation. -
Please clear your cache.
-
[Solved] Suspended Account: Alfonso
wolstech replied to alfonso's topic in Suspended and Queued Accounts
That inactivity message is because we deleted the account as part of the rebuild. That database was cleaned up last night. The login form won't show a maintenance message anymore because the system no longer knows you were on Tommy. It only knows that your account does not exist (which will display an inactive or non-exist message). -
[Solved] Account Reactivate - Tommy
wolstech replied to jmccrary's topic in Suspended and Queued Accounts
See sohamb03's answer. The accounts don't actually exist anymore contrary to what your domain is showing.