wolstech
-
Posts
17,963 -
Joined
-
Last visited
-
Days Won
675
Everything posted by wolstech
-
Unblocked. If you use https://heliohost.org/login/ you won't get blocked for incorrect passwords.
-
No it's not actually, considering most people don't use much space at all. In the past month, the long outages you see on the monitors are because our provider had a power outage (building struck by lightning), and the server crashed once (believed related to said outage). The other, shorter, red spots are typically either Apache restarts that took longer than normal or abusive users that took a few minutes to suspend.
-
[Solved] Java Servlet Regularly Shuts Down
wolstech replied to tommygun's topic in Escalated Requests
How about a cron to call your page every minute? Even though we restrict cron in cpanel, we can set it up externally at much greater frequencies as long as the script to be called can be triggered by visiting it in a browser. If that would work, post the URL we need to call and Krydos can set that up for you. -
[Solved] Java Servlet Regularly Shuts Down
wolstech replied to tommygun's topic in Escalated Requests
Apache restarts whenever needed (domain updates, etc.) on Tommy, and I believe Tomcat does the same, so yes, servlets are subject to restarting without notice. Krydos would know more and might have an idea what's going on/how we can make this work for you. Escalating. -
Renaming it will just disable it. The exact effects depend on what's in it. If you want, post the contents of it inside code tags here and I'll look.
-
Very true. There's indeed no such thing as perfect since the internet has far too many variables beyond your control, any of which could change or break and make a website fail. A good host and a service like CloudFlare will go a good way towards closing the gap though. Google probably has the best known uptime out there, and even they had an outage a few years back...
-
It wouldn't provide much benefit. If you have two servers hosting the site, but they share a single database kept on one server, all the servers will stop working if the server containing the database goes down. You need to have two completely independent copies on different servers. Separate database and all. That also means you have to make any edits twice, unless you make a script to synchronize them (probably doable but not fun). Be aware you're only allowed one account unless you ask for permission to have a second and can explain why you need it. Otherwise, you're violating our terms of service and all of your accounts will get suspended. If you need near-perfect reliability, a paid web host is probably more in line with what your client needs. We usually recommend Hostgator.
-
This support request is being escalated to our root admin.
-
[Solved] Perl Www::curl::easy Module Install Failing
wolstech replied to rqqmAuxeh's topic in Escalated Requests
This support request is being escalated to our root admin. -
Email Limit (1) Reached - How To Upgrade Or Use Another Provider?
wolstech replied to jamesarn's topic in Customer Service
We don't limit to 1 per hour like that unless you got throttled for some reason. Our limit is 50/day and you can request more if you can show that you're not sending spam (we'll want to see things like example emails, etc. if you need such an increase) Moved to customer service. -
This support request is being escalated to our root admin.
-
This support request is being escalated to our root admin.
-
The system does this for a variety of reasons. Using certain functions in cpanel will create one for example.
-
You are indeed on Ricky now. I've renamed your forum account back for you. Enjoy your Ricky account
-
Actually, doing that won't work because your forum account is named that. You could use ctfisep1... I'm hoping Krydos fixes Johnny's backlog before then though so your account gets deleted. That way you can just the same username and email address as before and everything will work as it should.
-
Accounts go inactive when they get flagged for deletion, and stay that way until it actually deletes. If you wanted to cancel your deletion in the meantime, you can just renew it. Johnny is really backed up on his account management work though, so I'm not sure it'll even get deleted by tonight...you're 1 of 9 accounts waiting in line for a deletion, and deletions are processed after new sign ups (52 are waiting in line for that). I've put in a request to have that looked at because even Johnny doesn't usually back up this bad. When he does, it's usually because he got hung up restarting Apache and stopped working his queue entirely. Try signing up tonight and if it says the username or email is taken, it didn't delete yet. If I see your account finish its delete I'll let you know.
-
No, you still need to delete the old hosting account first. You can do that here: http://www.heliohost.org/classic/support/scripts/delete Once you do that and it deletes, you're ready to sign up on Ricky when registrations open. Deleting your hosting account will NOT delete your forum account, so you'll keep using the forum account you have now. I'll just rename it to match your Ricky account once you sign up tonight. I only added that 2 to the forum account because you can't create a hosting account if a forum account with the username exists already.
-
Just a heads up, Ricky allows more accounts than Tommy, so unless you need Java or ASP.NET, Ricky is easier to get an account on. Also, I've renamed your forum account so you can reuse your username too. Once you sign up, let me know and I'll rename it back for you.
-
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. If you still see the suspended page, please clear your cache.
-
If you're able to donate, we can move your Johnny account instead of a sending a Tommy invite. Otherwise you have to delete it and sign up again at midnight when the registrations for Tommy and Ricky reset. http://wiki.helionet.org/Moving_your_account
-
First, try clearing your cache. I've seen CF do some weird things due to stale browser cache. However, your particular issue seems to be fairly common with CF. I've noticed this on one of my sites as well. CF doesn't always play nicely with immediate redirects in the root. Try removing the index.php redirect and doing it using .htaccess instead. If that doesn't help, my next recommendation would be to move the content into the root so the redirect can be eliminated entirely. By the way, unless for some reason really don't want people to know you use our services, there's no reason not to post your domains. Every domain hosted on our service is indexed by Google (regardless of whether it's mentioned on the forums) and several other search engines, so the additional linking actually serves to improve search visibility. By not mentioning them, you're actually hurting your site believe it or not, and you're also making it more difficult for us to support you too since I now have to look them up.
-
The public_html folder should be 750. All folders inside should be 755, unless the folder is the root folder for a subdomain or addon domain (in which case it should be 750 like public_html is). PHP files should be 644 (be aware that SFTP uploads are 664, which won't work until you change them...Apache does not like PHP files being writable by the group).
-
We changed the outbound IP for Johnny yesterday due to an issue with Softaculous. Escalating to have the RDNS updated. Thank you for pointing this out.
-
Could be script failure too. The deployment script is a beta feature. We'll see what Krydos says.
-
Unblocked. There's no way to disable the IMAP that I know of. You can pass a completely random username that doesn't even exist in, it'll still block you. The most I can think of is not setting up any device to get mail from us and instead using the webmail. I've always thought the blocking for bad mail passwords was a bit harsh, but it is effective. It's meant to help mitigate the risks associated with bots vs. weak passwords
