Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,715
  • Joined

  • Last visited

  • Days Won

    662

Everything posted by wolstech

  1. You have to do this in your scripts. I think it can be changed with set_ini...can't test though since I'm on my phone at the moment. We can't change it in the ini because it there is only one php.ini that affects everyone on the server (There isn't an ini for each user).
  2. That page is long outdated. Stevie crashed, and the repaired hardware became Ricky. Tommy lives on a third server we purchased last year. The server comparison is in the signup process after you validate your email address last time I checked. Ricky and Tommy have much better performance. Both servers have all versions of php from 5.4-7.2, you can pick which one you want. Tommy also offers asp.net and Java hosting if you want them (Ricky does not).
  3. SFTP on Tommy is port 1342, not 1373. Also, we generally recommend tommy.heliohost.org as the host name, though the one you're using should also work. FTPS has never worked reliably on any of our servers, it works for some, doesn't for others. We recommend SFTP for this exact reason (not to mention its more secure). Worst case is "Only use plain FTP (insecure)" which definitely works on port 21, but is just that...plain, unencrypted transmissions.
  4. This support request is being escalated to our root admin.
  5. Our system requires the domain's NS records be pointed to us at the registrar to add the domain. Adding an A record to us on cloudflare won't work. Please remove cloudflare, set your NS records to ns1.heliohost.org and ns2.heliohost.org at the registrar, add the domain, wait for it to start working, then set up cloudflare from scratch, letting it copy the records from our servers.
  6. You can't edit or override php.ini. That particular value should already be on for all php versions though, so if you're seeing one that's off, we can fix that. What version and server you using?
  7. It's not even removed by an admin. The server stops showing that on its own when Apache restarts. Short of manually restarting Apache (which causes downtime), we can't remove it either. Your account did take longer than many do though, because Johnny's Apache restart got stuck last night and never happened like it should have. Krydos will move you to Tommy when he sees the post.
  8. Thank you for the donation. Escalating to have your account moved to Tommy. The FTP issue is sadly a result of the overloading of the server. I agree this could be improved, but it would mean us accepting fewer users. Fewer users means our ad and donation revenue won't cover our colo bill, and we would eventually go out of business As for the lack of information on the redirect, it's because you can't remove the redirect. It's there because the server isn't fully configured. This reason is explained on the page you get redirected to. Do you think an additional message on the account creation page would be helpful for new Johnny users?
  9. Do they seriously do that? That's absurdly long. No, we don't have any daily maintenance window like that. It does go down once or twice a day, but just for a few minutes while Apache restarts so we can get rid of queued pages for people. The server you're on (Johnny) does get very slow at times though when it's busy creating and archiving accounts. Ricky and Tommy have significantly fewer accounts due to them being limited signup, and as a result they don't have the performance issues and downtime Johnny does. You can take a look at the performance for all the servers here: http://heliohost.grd.net.pl/monitor/
  10. The queued page exists only because Apache has to show something when it doesn't know what account the domain belongs to (which is the case between the time you sign up and the time Apache restarts to load the new configuration that contains information about your domain...Apache only restarts about once a day on Johnny). It's not an intentional redirection, just Apache saying "I don't know what to do with this". Since it seems to be working now, the point is moot. Donation information can be found here: https://heliohost.org/donate/ Invite can take up to 24 hours to arrive. If you prefer to move your existing account instead, please post the transaction ID and the name of the account after donating and we'll move the account instead.
  11. This support request is being escalated to our root admin.
  12. Please clear your cache to fix the queued page. Your site is working for me. As for the FTP issues, you're on Johnny...Johnny is meant for testing and not hosting a production website. Because Johnny signups are always open, the server is severely overloaded, which means he often suffers from major performance issues and downtime. I would recommend moving to Ricky or Tommy if you want an account with good performance and uptime. Signups open at midnight UTC every day and fill quickly. Alternately, you can donate $1 or more and either have your existing account moved, or get an invite for Tommy that works even when it's full for the day.
  13. @bh7: https://www.helionet.org/index/topic/29876-queued-bh7/
  14. This support request is being escalated to our root admin.
  15. It can take a few minutes to a few hours for it to start working again.
  16. Unblocked.
  17. WHM is for root admins only, users don't have access to that. If you were trying to sign into WHM, that's you were blocked. cPanel for your site is located at https://ricky.heliohost.org:2083/ Unblocked.
  18. Done. Please post from each of these to verify you own them.
  19. You either need to delete your account and sign up when registrations open, or donate and provide the donation transaction ID to move your account without deleting it. Take a look at http://wiki.helionet.org/Moving_your_account As for Java, Tommy takes a few hours for a Java request to become active (compared to the months on Johnny), and you can also deploy your own WAR files on Tommy (which usually take a few hours from when you request their deployment to when they start working).
  20. @Krydos: That's actually his email address, not his username. The account its attached to is banned for phishing.
  21. Gone.
  22. This support request is being escalated to our root admin.
  23. Did you manually edit his skin through the AdminCP?Bingo. He was set specifically to mobile for some reason. I just changed it to the HelioNet theme, but system default probably would've worked too.
  24. Unblocked. Try resetting your password here: https://johnny.heliohost.org:2083/resetpass?start=1 If that doesn't work, I'll escalate this for you. The account does exist and is active, but your account is different from most. You have a username that exceeds 8 characters (the normal limit)...I wonder if that could be related to this issue.
  25. It's archived. Escalating to have it restored.
×
×
  • Create New...