Jump to content

Krydos

Chief Executive Officer
  • Posts

    24,137
  • Joined

  • Last visited

  • Days Won

    847

Everything posted by Krydos

  1. That account was created and has been active since 12:24 pm PST on January 29th and you should have been able to login anytime after that at http://heliohost.org/ What does it say when you try to login? What happens when you try resetting your password at http://stevie.heliohost.org:2082/ ?
  2. I guess we misunderstood what your question was then. It appeared (to me at least) that you wanted to know if it was possible to access apache web logs. The answer was given to you, which is still "no" and you were given the reason why too which is still "because it causes high load on the server", and as if that wasn't already enough you were even given some ideas of other options that you could use to get information about who is visiting your site. No. It's not possible. It doesn't matter if you can log into it or not because if you did log in there is nothing there to view because logging is disabled to reduce load. If you don't like google analytics you could use pwik or something else. There are hundreds of options. You might also want to read this http://wiki.helionet.org/Site_statistics
  3. Brute force protection was not enabled on this account. Your account password has been reset, tested, and emailed to your contact email address. Keep in mind that both the password and your username are case sensitive and must be typed exactly as they appear in the email. Let us know if you are still unable to log into your account.
  4. That's just a 500 error and it's just as uninformative as the error before it.
  5. You should enable remote error messages temporarily so we can see what the error is.
  6. Glad your problem got solved! Please spare a few minutes to take our brief survey: http://feedback.heliohost.org/ Your participation in this survey is greatly appreciated.
  7. You actually have it set to ns1.heliohost.COM and ns2.heliohost.COM which doesn't exist (or if it does exist it has nothing to do with us.) You typed it right in your above post though; you just need to type it right into your registrar's website.
  8. Is this still occurring, or is everything working now?
  9. It shouldn't really matter if you delete folders. The url roots of each of your domains will automatically be recreated once every 24 hours. So, if you only have the one main domain that each account starts with it will be /home/username/public_html. If you have any addon domains these will also automatically be recreated such as /home/username/public_html/addon. If you want to run cgi you might have a bit more of a problem because the cgi-bin directory probably won't recreate itself, and if you just create a directory called "cgi-bin" it might not work to run cgi in because it needs to have special permissions and apache has to recognize it before it will work. Anyways, if you have any specific problems or errors let us know and we can help you with them, or if it really bothers you that your account isn't perfect anymore I suppose you could always delete your account http://www.heliohost.org/home/support/scripts/delete and recreate it http://www.heliohost.org/home/signup
  10. It sounds like you're trying to deploy a .war. When java is activated on your account .jsp files should start working within 24 hours, but .war files have to be deployed by an admin on your account for you. Here is the process.
  11. This is the process I use to deploy a rails application. Click http://johnny.heliohost.org:2082/frontend/x3/ror/index.html Type the app name into the box. Check (or leave unchecked) load on boot. Choose your application path. Default is /home/[username]/rails_apps/[appname] Choose the environment type: production or development. Click create. Wait for the rails app to be created, and then once it is click "go back." Now your new application should show up under the "Available Ruby on Rails Applications" heading, but it will say "Not Running" so click the "Run" button under the Actions header. cPanel will start the application, and give you a "go back" link. Click this. When the page reloads a lot of the time it will still say that your application is still not running, but if you reload the page again it should show up shortly. Locate your new rails app under the "Create a Rewrite" header, and click "Create Rewrite." Here you can create a subdirectory for the rails app to run under, or you can select whatever subdomains, parked domains, or addon domains you have previously added. When you have the location you want your rails app to run from click "Save." Now when you go to the domain you selected/typed above you should see a brand new default rails app with the "Welcome aboard, you're riding Ruby on Rails!" If you see a 500 error, or a 503 error or 404 error, or something else it might mean you messed up on the above steps. Open up cPanel file manager, or FTP, or your favourite way of getting your files onto the server, and navigate to /home/[username]/rails_apps/[appname] or wherever you put your rails app in the above steps. Upload your files, and have fun developing in RoR. Let us know if this process works for you. There may be several valid ways to get a functional RoR application working on Heliohost, but this is the process that I have used and is proven to work.
  12. That's probably because palac-du.heliohost.org is not the domain for the account pdu.
  13. That account is not suspended. Don't forget to clear your cache.
  14. Try adding your domain again now. Let us know if you're still not able to park your domain.
  15. That domain is not hosted on our servers. http://byrondallas.heliohost.org/php/tools/dns_records.php?domain=sprite-cs.tk&rec=NS you would have to ask 000webhost.com why it's offline since that is where you have your name servers set. If you want to host that domain with us you need to log into your http://dot.tk/ account and set your nameservers to ns1.heliohost.org and ns2.heliohost.org
  16. Thank you to vogelserver for posting a test file that I could check while I tinkered with things. I think I've got the gdiplus.dll stuff working now. Is it working for everyone?
  17. That domain was added about 2 hours ago. 2 hours is less than the 24 hours that one can expect all newly added domains to show up as queued. Please wait an additional 22 hours, and if you still see the queued page try clearing your browser cache. If clearing the cache doesn't make the queued page go away let us know and we can take another look.
  18. Try resetting your password now. Let us know if you're still unable to log into your account.
  19. /home1/toast/public_html/Hall_of_Mirrors.exe
  20. Your account was suspended for the following reason: Malware. 1 file(s). Win.Trojan.Agent-127903 FOUND That means that there are some malware files found on your account. For your safety and to protect your website from potential further corruption the account has been suspended. To find the infected files we recommend making a backup of your site, download the backup file to your computer, and scan the backup using a reputable virus and malware scanner. If you're having trouble locating the offending files please ask and we can provide more information. If you are you certain that it is a false-positive, we strongly encourage you to file a false positive form here: http://cgi.clamav.net/sendvirus.cgi Your account should be unsuspended now, but keep in mind that this is a temporary unsuspension. You have 24 hours starting at the time of this post to clean your account of any and all malicious files or your account will be resuspended.
  21. Your account has been manually unsuspended. If you still see the suspended page then you should try clearing your browsers cache.
  22. Well, your account is causing the most load on your server so far today, so no I don't think you have it fixed yet.
  23. That .war could be deployed, but it wouldn't start. Here is the error message it produced: FAIL - Application at context path /EPP could not be started
  24. I just wish more people were willing to try to fix high load problems. It seems most of the people who get suspended for high load just say something like "thanx for u halp" and then cause twice as much load the next day. The point of high load suspensions and second chances are to alert webmasters to problems and then get those problems fixed which you have done. So thank you.
×
×
  • Create New...