Krydos

It doesn't seem to have disappeared yet. I created my account probably about 7 or 8 months ago now so it's probably about time I introduced myself: Hi. I'm Krydos. When I saw the feature list of heliohost and it was all for free I just kept asking, "What is the catch?!" So far the closest thing to a catch is having to set an alarm to log on and create an account at midnight PST, but that wasn't really a big deal. Amazingly quick and helpful support staff too. I'll let you all know if I ever discover the catch.

Hindsight may be 20/20, but this is why I have krydos.heliohost.org and then use parked/addon domains. If I point the nameservers somewhere else I can still access all my sites even if it isn't as pretty as a nice .com url or whatever. I remember when I signed up for the account having the choice of making a url that you can addon to as many domains as you want, or just having a non-heliohost.org type url. I also seem to recall the walk through text strongly recommending the first option for just this reason. Perhaps the admins can add the heliohost type address after the fact? I wouldn't know.

Yeah, I looked at those scripts many times and never even considered that they could look better. I was just impressed with what they could do, not how they looked. I guess some people are just more concerned with functionality than appearance. That said, they look very nice now that they have been spruced up. Great job jje!

This is due to a problem with mono. Please see the topic in escalated requests. I'm pretty sure Geoff is referring to http://www.helionet.org/index/index.php?s=...ost&p=63726

You can use: ntpdate -u <ntp_server_you_want_to_update_from> The package can update times automatically as a service and you can have johnny and stevie sync time from each other at a higher frequency, etc. ntp.org

I think nuclear energy is fairly safe. In the case of Japan it seems like they had plans for if there was a huge earthquake the reactor would be fine. If there was a tidal wave the reactor would be as safe as it could be. If there was a power outage the reactor would be safe for months as they restored power. They hadn't really counted on all of the above occurring at the same time though. Even with all of the above happening in a sort of perfect storm of messing up the reactor they always had the safeguard of being able to dump sea water on the reactor. The main problem I think that occurred with the Fukushima reactors is they are owned and ran by TEPCO which is a private company. Capitalism is all great and fine; hell we've all been brainwashed since birth -- especially here in the USA -- that capitalism is the most amazing thing since the concept of freedom, but in this case it might be the problem. TEPCO knew that if they dumped sea water on the reactors they would be ruined forever and they would no longer ever be able to produce electricity and therefore wouldn't ever produce anymore revenue for them. I wonder if the disaster would have been a lot less horrible if the reactors were overseen by the government instead of a private company. With anything capable of causing so much destruction the first concern always has to be the safety and health of human beings, not money. I will almost always advocate the reduction and size of any government, but do large corporations that have been built from the ground up with the primary focus on profit really ever truly have the good of the general public in mind? Just my opinion.

All working again. Many thanks byron. This happened because I forgot to log in (as you are supposed to) once a month. I think people like me need to setup a recurring Outlook/Notes reminder to log into cPanel when website development work is on the 'back burner' in excess of a month. I get an email reminding me to log in if I haven't for a month. You might want to check the email address that heliohost has for you or your spam filter settings if you aren't getting your reminder emails.

I think it's safe to say that every account on stevie is showing account queued. I can log into cpanel and see all my sites and files perfectly but trying to access any of them through a browser just shows the queued page like the account is still being created. And of course as soon as I post the problem fixes itself again. This is what happened yesterday when I posted about cPanel login issues too. I'm starting to see a pattern. Perhaps I should post more often?

I can't speak for anyone else, but for me: heliohost.org (cpanel login at the bottom of page) --> Doesn't work. cpanel.heliohost.org --> Does work. krydos.heliohost.org/cpanel --> Doesn't work Earlier, when I originally posted my thread, none of the options I could think of would work. Let me know if you want me to try any other urls/ports.

Yesterday, I could log in to my cpanel. Today I cannot. Perhaps a password reset will help? username: krydos domain: krydos.heliohost.org server: stevie False alarm I guess. Now it suddenly starts logging in. I was using browser cached uname and pword so there isn't any chance I was typing it wrong. It did give some messages about brute force prevention, but I disregarded that because I was so adamant that I knew my username/password that I tried a few times in a row. Perhaps someone was trying to hack my account and caused me to not be able to log in. Summation: It seems I don't need a password reset after all. Thanks for looking. False alarm I guess. Now it suddenly starts logging in. I was using browser cached uname and pword so there isn't any chance I was typing it wrong. It did give some messages about brute force prevention, but I disregarded that because I was so adamant that I knew my username/password that I tried a few times in a row. Perhaps someone was trying to hack my account and caused me to not be able to log in. Summation: It seems I don't need a password reset after all. Thanks for looking. I'm guessing, based on the sudden multiple requests for password requests due to not being able to log in in the last ~30 minutes, that someone was trying to brute force their way into accounts. I would recommended everyone make sure they have a very strong password. Especially those who have posted their account names in this forum recently.

Thank you. Everything seems to be working now. Was this caused by something that I did, or was there anyway for me to fix this issue myself in the future if it appears again?

.htaccess contents: # -FrontPage- IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti* <Limit GET POST> order deny,allow deny from all allow from all </Limit> <Limit PUT DELETE> order deny,allow deny from all </Limit> AuthName krydos.heliohost.org AuthUserFile /home/krydos/public_html/_vti_pvt/service.pwd AuthGroupFile /home/krydos/public_html/_vti_pvt/service.grp In addition I tried removing the .htaccess file completely, and still no change. Still get the 500 Internal Server Error.

Created and located at http://krydos.heliohost.org/jje_test.php Still gives 500 Internal Server Error.

domain: krydos.heliohost.org username: krydos server: stevie All of my .php files have been giving 500 Internal Server Errors for over 48 hours now. Out of curiousity I renamed my index.php in the root of public_html to index.html and it displays perfectly with no error. As soon as it is renamed back to a .php file the 500 error comes right back. I have cleared cache, used several different browsers, and several different computers on several different ip addresses. No .php files on my entire site show anything other than 500 Internal Server Error while anything .html displays fine. I haven't changed any settings in months so it's very unlikely I caused this. This might be the same issue as http://www.helionet.org/index/index.php?sh...=8932&st=15 but since he is using all cgi and I am using php I thought I'd make a separate thread. Feel free to merge them if you need to.

I have also been having the internal server error a lot on my pages, and came to these forums to try to figure out what was going on. I am using mostly php files that I have written myself. Is there anything I can do to reduce the amount of errors or the length of time that these errors are being displayed to anyone trying to look at my page?