Jump to content

lancersupraskyline

Members
  • Posts

    25
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by lancersupraskyline

  1. You should have checked the server's capabilities before developing your website. In addition to Django support, the Python versions in HelioHost are stated in this page. Some users have been able to install Django 1.5.1 in HelioHost, but nothing about 1.6.1 was posted, as far as I know.
  2. I do hope that you know that you are breaking the rule of having more than one account per person. As to why the script did not work, it would help if you would tell which forum you were trying to install. Have you checked that the file exists in the directory before accessing it? Also, have you made sure that the forum is compatible with whatever server side language that HelioHost provides? I have not tried Softaculous, and therefore, could not comment any further.
  3. CPanel has an interface that shows the files/folders which take up the most space. You can find it in Files > Disk Space Usage, and try to look for the culprit. Since you are confident that your data does not exceed the limit, I'd recommend you to review your coding thoroughly, especially on uploads and data entry. Lastly, I'd suggest you to change your passwords, for FTP and CPanel. Someone may have gained access without your knowledge, and misused the space.
  4. mysql API has been deprecated. Please consider mysqli or PDO instead. The first parameter of mysql_connect is the MySQL server. Since PHP and MySQL resides on the same server, you should have used the string localhost instead. From tizag: In other words, <?php mysql_connect("localhost", "someday_someday", "CorrectPassword") or die(mysql_error()); mysql_select_db("someday_Database") or die(mysql_error()); ?>
  5. Just wanted to point out that the page for Python and Django, has dead links for the snakecharmer.py. Additionally, if possible, HelioHost should upgrade to the latest versions of Python.
  6. It applies to all accounts. From http://wiki.helionet...activity_policy,
  7. Making an exception for you alone would be unfair to the other users. As for the competition, you know, you could search the forums... But it has been quiet for quite some time now. http://www.helionet....ebsite-contest/ http://www.helionet....oting-now-open/
  8. 1. Did you read the error message? It does give a number of possibilities. 2. As stated in the wiki
  9. To quote HelioHost, If you really need more space, I'd suggest looking for a paid solution.
  10. No, seriously. Have you made any research regarding the matter? Have you made a Google Search on storing images in database? Do you know how many times this question has been asked in StackOverflow? And how almost all of the accepted answer is against storing images in database? If you do realize this, and still wish to proceed, then by all means, go ahead.
  11. Not sure if this answers what you want, but from HelioHost's System and Software page
  12. In my opinion, it is not a concern, because: Your index.html precedes index.php, so it only runs when user types in <url>/index.php specifically. The JavaScript file has been removed from Google Code, which means the JavaScript won't load. I have tried accessing the JS file directly, and I got a 403 error. If you are still afraid, here's a link to how it looks like with a online screenshot. The whole index.php file do not seem to have any dangerous elements, except for the JS file. Only some psychedelic NyanCats with a YouTube background music. There's a link at the bottom, which leads to a list of hacked websites (I think?), which shows the websites hacked by "Lulz53c", in which Mr. hacker here claims to be a member. Of course, to be safe, clean up your index.php, or remove it totally if you don't need it.
  13. Into the database? Seriously? Have you made any research regarding this matter?
  14. Well, from some light Googling, it appears that your site is not the first. The JS file was hosted at Google Code, which was already banned/removed, as of October 12. A user reported it to be a keylogger, and Mr. hacker here has a personal blog.
  15. Three cheers for HelioHost. Seems like the server is back up! http://www.helionet.org/index/topic/17401-stevie-downtime/
  16. Well, lots of things are going down in HelioHost today. http://heliohost.grd.net.pl/monitor/
  17. Stevie server is down. Gee, check HelioHost server status first before firing claims.
  18. Well, not saying that they will never fix it, but these things are to be predicted and tolerated when we are literally getting free ice-cream here.
  19. Since there is no official news about Stevie being down yet... thought I'd start a small discussion. I was doing some work on my website when I noticed that the server load spiked to over 40%. I stopped my work and double confirmed it with this site, which appears to be down now as well. Came back after 30 mins or so to find Stevie down. *panics* Dear mods/admins, any news about it? And other members, what are you all doing in the mean time?
  20. I'm sorry, but it didn't work. I tried your suggestion, and provided the full path for 403 Error Document, but it still did not redirect me to error.php. The error page is same as the above. Maybe my .htaccess can shed some light. Most of the parts were taken from H5BP. In case you're interested to try it out, the URL to the said protected folder is http://altbdoor.heli...org/admin/frame
  21. Hello all, I'm in the midst of making my website work, and I ran into a problem with error documents. To begin with, here's how my directory structure looks like: + www (root) | +- foo | | | +-- bar (750) | +- .htaccess | +- error.php I want to prevent user access into /foo/bar, so I changed the permission of the folder (bar) to 750, and 640 for its contents. In my .htaccess, I have specified as below: ErrorDocument 400 /error.php ErrorDocument 401 /error.php ErrorDocument 403 /error.php ErrorDocument 404 /error.php ErrorDocument 500 /error.php Attempting to visit /foo/bar, I have expected to be redirected to error.php, as it is 403 error (or is it not?). However, I am getting a usual 403 Forbidden page instead. Forbidden You don't have permission to access /foo/bar/ on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Any ideas?
  22. Hello there, Have you read this page? http://www.heliohost.org/home/features/languages/php As far as I know, all scripts are allowed, but you will need to check if the current PHP supports them (version, specific functions, etc)
  23. ...what are you trying to say? It's hard to understand without any punctuations here.
×
×
  • Create New...