wolstech

Please check the email address associated with your account for an email with a new password. I have verified that the password in that email is working on cPanel's login interface at https://johnny.heliohost.org:2083/ The other system should have updated as well because they both check against the password on the hosting server and thus can't be changed independently. I agree that our system should enforce the same requirements. I'll see if Krydos can do some additional testing and perhaps add a max password length check. You're only the second user in my 7 years to ever have a password that's too long though. As for having a limit to begin with, yeah, cP is behind on quite a few things, and actually surprisingly up to date on others. The password limit I'm unsure why this exists (and oddly, the actual password was stored correctly because our system could verify it). The former username actually was a limitation of MySQL based on my reading...cPanel just enforced it so MySQL would work properly.

Assuming what I can find from 2014 is still true with today's versions, cPanel's maximum on passwords is 18 characters, which would explain why your ridiculously long password won't work. Can you try changing the password to something 18 characters long and see if that one works correctly?

Remove your forced HTTPS redirect. You may also need to disable CloudFlare.

Try changing your password to something <20 characters, no symbols. While there shouldn't be an issue, I did run into an issue a little while back on here that turned out to be caused by a password being too long. Also, be aware that the "additional accounts" options don't work with SFTP (you need to use plain unencrypted FTP on port 21 for these). We also limit our usernames to 8 characters...(though this one there's no longer any reason for technically...it's a legacy thing from old cPanel versions).

If it'll allow you to donate on the gofundme, go ahead We're always accepting donations, so even if it's not letting you, donate via Paypal and post here so we can count it for you.

OK, that's unblocked (you may need to give it up to 10 minutes to take effect). You're correct that cPanel didn't work because of the block (when blocked, nothing on the server you're blocked from will work for you). I'm not sure what's up with the SFTP...you're using the same username and password as cPanel correct? If so, it just might be load, but I'll move this so Krydos can double check for you.

Er, yes they do. Chrome leads by 47% over the second most popular choice: https://netmarketshare.com/browser-market-share.aspx

The IP you're posting from isn't blocked. Try going to https://heliohost.org/login/ and logging in. If it's blocked, that will tell you the exact IP that's blocked on our end, and why it got blocked. Once we know that, I can unblock you. Also, be aware that if you're on Johnny, he's down a lot due to load. Login failures due to load generally just show up as invalid logins (they time out), and you can resolve it by just trying again later. (You can see load history for your server here: http://heliohost.grd.net.pl/monitor/)

You're actually blocked for failed SMTP attempts, which means you have a mail client that's misconfigured somewhere. Unblocked. It may take up to 10 minutes to be effective.

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

Are you aware that you're only allowed one account? Please delete either vivekks or viveks within 24 hours. If you do not, the account viveks (the one you did NOT deploy your servlet on) will be suspended. You can delete an account here: http://www.heliohost.org/classic/support/scripts/delete

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Most common issue is #1 in mrj's list. Once added, they can take 12 hours to start working.

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. <br /><br />If you still see the suspended page, please clear your cache.<br /><br />If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic you might consider trying paid hosting from our partner starting at only a cent for the first month. https://www.heliohost.org/partners/hostgator

It does when he can't even install the certificates on our end so Chrome sees them. He has a self-signed cert by default, and every browser in existence will squawk at that. Chrome will show a privacy warning, then if ignored, leaves an HTTPS in the bar that's crossed out in red because the cert is bad. The secure/not secure/green https/etc. is a different thing altogether in chrome, and is specific to chrome. Other browsers don't do that.

That's the thing, we can't tell you because we don't have any idea either...if we did, we'd have gotten it installed for you. Odds are it's just our server is broken though. Johnny has a ton of issues with involved processes like installing ssl or creating new domains. That's why he recommended trying Ricky, which doesn't have these sorts of issues.

I had the same problem when implementing something for heliomine, and I don't even have asp.net on my account. I ended up just changing the extensions and making the program rename them. I'd love to see a proper solution to this though. Moving.

You can use https://johnny.heliohost.org:2083/ to log in directly if our site won't work. Our website likes to time out a lot when signing into Johnny accounts. Those timeouts show up as the invalid logins you see.

Usually that not secure error is a result of not waiting long enough (it takes up to 12 hours for Johnny to refresh and recognize SSL certs after installation), but considering you said it's been 2 days...I'm not sure what's up here. The fact you see a different site if you ignore the security warning is kind of odd...usually you get the same site with an invalid (usually self-signed) certificate. I'll let Krydos look at this further. Please note though that SSL barely works on Johnny, and it's known for being troublesome. You have to play with it until you get it working. I'd recommend moving to Ricky or Tommy if you can, they actually work reliably with SSL. Also, those servers don't even require you install a certificate for SSL since cPanel automatically gets one for you and renews it when it expires.

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

@helio607: Please create your own topic for your issue in the future. I've done it for you this time: https://www.helionet.org/index/topic/31806-archived-helio607/

Yeah, you're supposed to log in before that happens. Unarchiving...

Krydos edited his post... We found it. It was in the regular donations. We can count that for extra storage for you

You have to use plain ftp on port 21 for those extra accounts to work. It can't be FTP over TLS or SFTP, has to be plain unencrypted FTP. The default account is just your cpanel username and password. Hostname is Johnny.heliohost.org. Port is 1373 for SFTP (which is supported only for this default account), or 21 with plain unencrypted FTP. Unblocked.

Krydos can confirm, but anyone who donated through GoFundMe's website prior to the announcement (and possibly even after, since you can still donate to the GoFundMe as of this post) will be counted I believe.