wolstech

Thank you for your donation. Invites are only automatic if you donate through the form on https://heliohost.org/donate/ Krydos has to send invites for Paypal and Skrill donations manually, so they can take a few hours. Can you post the transaction ID number so we can check if it's been sent?

Blocked for too many failed cPanel logins. Unblocked.

It's actually been existence for less than 24 hours since you created it when the server wasn't processing new accounts (the server didn't actually create that until late yesterday sometime). An Apache restart is showing as in progress right now, which is what you're waiting for to get this working. If it doesn't work once that finishes, I'll escalate.

The server Stevie crashed 6 months ago. That account has been gone since early January. There's no way it was within 48 hours of our notice unless the notice was erroneous. If you need the contents, your can try retrieving a backup of it from http://heliohost.org/backup/, but be aware that not all accounts are available. If you receive a not found error, a broken link, or an empty archive, it means the account could not be backed up. When requesting the backup, your need to use the same email address that was used on that account to request it.

Domains on Johnny accounts take up to 24 hours to start working.

Unblocked and moved to customer service.

Not sure if a typo or not, but if you actually meant server IP, it won't work. You need to use your domain name to see your site. We don't support direct IP address access because we're a shared host. The host name (your domain, which is included in HTTP headers in the Host field) is what tells Apache what account's content to serve. The IP address of the server is not a valid domain, so it will always show queued.

Apache is down on Johnny: http://heliohost.grd.net.pl/monitor/ cPanel and FTP should be working fine, however your actual website will be inaccessible until this is corrected. Escalating.

It's not just you. Johnny's Apache is down: http://heliohost.grd.net.pl/monitor/ Either Krydos is still working on Apache (he was recompiling it recently), or something broke. Escalating.

Its creation is pending. Johnny's account creations are currently not processing because we are rebuilding apache on that server. Similarly, deletions/renewals/etc. also aren't working for Johnny right now. When the apache compile process is finished, the accounts that registered during this time will be created. Best thing to do is just wait.

No. You need to use a different username, email, and domain.

As someone who despises popads and actually went to the effort of blocking it at the network level at my house (they're very good at beating blockers and pushing adware)...just no. For laughs, I just tried opening their website through a VPN...and my malwarebytes blocked it... We already use adsense. It's our primary source of non-donation revenue. We also have a few affiliate programs for things like buying domains, though we don't make much from those.

It was open for a few minutes tonight, but it can be a challenge...Tommy has been known to fill for the day in as little as 9 seconds (yeah, it's literally "mash the refresh button and hope you win the lottery" because everybody else wants those accounts too and we only allow a few a day to prevent him from becoming another Johnny...). Ricky wasn't a bad server when he was up. Decent uptime and reasonably fast. I used to use that server back when it was called Stevie. The server is down due to hard disk failure. We got our money's worth though...10 years on one set of disks ain't bad... Unfortunately, it might be the end of August/early September before he's back up since we have to raise money to buy disks, then wait for the server to be re-disked (most of us are on the east coast, the server's in California, so that'll occur when the founder next travels out there for personal business), then install all the software again.

You were blocked for too many failed POP3 logins...did you change an email password recently and forget to update a mail client or phone mail app? You've been unblocked.

Johnny is meant for testing, not running a production website. His uptime is generally ~85-90%, and is not for things that need to be consistently up. If you need stable, production grade service, you need to move to our Tommy server (uptime of 98-100%). Tommy is hosted on new hardware, and is intended for production sites that need up time. Tommy has strict resource use limits, optimizations, and limited registrations to prevent overcrowding, among other things. The Johnny server allows to play with all the functionality we offer, but because we crammed all of it on one server, allow more resource use per user, and didn't restrict the number of users, we can't really optimize it (the server simply isn't powerful enough). It's also worth noting that the server hardware Johnny lives on is ancient, as opposed to Tommy. The only thing Johnny has that our other servers do not, is Ruby on Rails (this is because we have to use an old version of CentOS and cPanel, RoR support was dropped in newer versions). Finally, the past day or so is particularly bad for Johnny because we were rebuilding Apache...which adds load and required we stop a lot of things like account management, etc. When Apache finishes, there will be downtime for the new version to start, followed by all the backlogged management work trying to catch up...creating more load. The caching thing is definitely something to look into...we already offer CloudFlare support for those wanting the extra performance and gap coverage for the load- and apache-restart-induced outages. Not sure whether this would help or not. TL;DR: Johnny isn't meant to be stable, and is also old. Take a look at Tommy for production-grade service.

It's your computer (or more likely, your internet connection). Either your browser isn't saving cookies, your public IP is changing too often, or both. Can you try a different computer and a different internet connection?

Your account appears to be related to another account that's already active. Our TOS only allows users to have one active account. Do you have another account, or can you explain why it appears that you do?

That account is suspended for Phishing. For security reasons, phishing accounts cannot be unsuspended, backed up, or deleted. You will need to create a new account and restore any backup you may have. Please be aware that you will not be able to reuse any domains on your suspended account, and will need to pick a new username. We apologize for any inconvenience this may have caused.

Bdistler has it here. Your account is on a server that no longer exists (hardware failure). The links he posted will explain more and let you get your backup so you can move to another server.

Not at this time. It's been a planned feature for a while, but I'm not sure where that functionality stands in regards to development... Escalating.

This support request is being escalated to our root admin.

You can make a domain receive mail using an external mail server by changing the MX records, but I don't think we can automatically use an external SMTP server for sending everything on an account. No idea why the server would refuse connection though unless Yahoo blocked us or our firewall is in the way (shouldn't be, assuming Yahoo uses standard mail ports). Krydos will probably have more of an idea as to why this might be failing. Escalating.

We don't allow it by default. A root admin will need to enable that for you. What database name and user account needs remote access, and what IP do you want to access it from?

We're actually working on setting up a fundraiser to purchase storage hardware. The details haven't been announced yet, but when it comes out, donating to that fundraiser will let you instantly get additional storage on our existing hardware as a thank you gift. For right now though, you'll need to make do with the 1GB until we can get that set up. We're hoping to have it available in the coming weeks.

Krydos has to do that, which is why I escalated it. Just wait and he'll unarchive it when he sees the post.