Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,717
  • Joined

  • Last visited

  • Days Won

    662

Everything posted by wolstech

  1. Actually, thinking about how IIS sites work, it'd likely be closer to how RoR works on Johnny than how Java works, and speaking of RoR, I'm now tempted to see if that would run on Lily...being able to offer RoR on another server would mean Johnny can finally get a long-overdue upgrade.
  2. You can do that here: http://www.heliohost.org/classic/support/scripts/delete
  3. No. This server will be its own thing. We have no plans to replace the linux servers or cPanel. We're trying to avoid Plesk because of cost and complexity. I'm most likely going to end up developing a barebones back-end myself. IIS doesn't really have a great web-based front end, so odds are users will need to install the Windows RSAT and manage that aspect with the conventional MS tools if the web tools MS provides don't cut it and free ones don't already exist. Recent research suggests one good (and relatively easy) solution would be to configure the Windows server as a "slave server" for the existing linux boxes. IIS/.NET would be offered like Mono and Java are now on Tommy...you'd just sign up for a Tommy or Johnny account like always, and "request IIS" in cPanel. You'd get an FTP folder and a user account on the Windows server where you upload your ASP.NET stuff and configure IIS. Then you visit it through your existing cPanel account's website as if it was a subfolder, kind of like what a Java WAR does now (upload, configure/deploy, and it appears as a virtual folder) This would mean everything except IIS/ASP.NET is handled by our already-proven cPanel servers, so we don't need to reinvent the wheel implementing DNS management, user management, and the tons of other things cPanel does. PHP and other languages could be made available through IIS as well if there's demand for it. Also, stock IIS has very little functionality for shared environments. For instance, it has no capability for user management except by site (and each needs to be on a different port I believe). Plesk cheats by using one IIS site for all users and just having its own user management system outside the Windows one to control access. I suppose I could develop a user management solution if need be.
  4. This issue with gmail and other mail providers has been fixed.
  5. I doubt it. We're not even sure if we can make this thing work the way we want since we've never tried offering a Windows server before, let alone any support for cloud stuff. Worst case is we end up with Plesk.
  6. Firewall was misconfigured. It was set to only allow it to work for root. We ran all the tests as root, which is why our tests kept passing and left us confused why it failed for everyone else. Your scripts run as your user account, which didn't have permission to communicate on port 587.
  7. That happens sometimes. Usually it's a stale cache deciding to come back from the grave. I've seen it happen a week+ after unsuspending (or creation for queued pages).
  8. That account is not suspended. Please clear your cache.
  9. Gmail SMTP (and Outlook.com SMTP) are a known incompatibility with our servers. Java and PHP don't work with Gmail and Outlook.com, and we have no idea why. The ports are open and we can receive the EHLO from their servers just fine, yet you can't actually send mail. There's nothing we can really do to fix this. Something on these two services doesn't comply with standards and will not work with the standardized SMTP implementations we use. You can try turning on support for "Less secure apps" in Gmail, but even with that on, the only language that I know works is Django, when using Django's own SMTP library. Even with the security setting enabled, PHP still doesn't work, and I don't know about Java.
  10. That was fast, I literally banned him 10 minutes ago...he had phishing for the Royal Bank of Scotland on his account.
  11. That account is suspended for multiple accounts. You're only allowed one. Because the account seen here: https://www.helionet.org/index/topic/31602-suspended-josemi05/ was already unsuspended, this account cannot be unsuspended unless that one is suspended again.
  12. You're suspended for creating 7 accounts. You're only allowed one. The account josemi5 has been unsuspended.
  13. As Bailey said, it doesn't even exist yet because we haven't raised enough money to buy it, let alone the time to install it (which will likely take a month or more after we buy it). When it does become available, we likely won't support account moves anyway, because the platforms are dissimilar (Lily is supposed to have Windows).
  14. @Krydos: Can you check the content when done restoring it? The domain makes me wonder something....
  15. Unblocked.
  16. It is not. They have to be created by cpanel. Cpanel does have an api though...
  17. The malware file attached to your post has been deleted. Also, your account cannot be unsuspended.
  18. There's irony in this one...we usually recommend a VPN or proxy as a solution for this. It's especially helpful for people on mobile because cell phone data plan IPs change very frequently (tower to tower, or even just if the time between communications is long enough).
  19. Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...
  20. Maicol pretty much has it. If it's AutoSSL, it didn't renew because it was inactive during the time when it would attempt renewal and when it expired. It should renew itself now that you've restored your account, but it may take 24-48 hours for AutoSSL to realize its expired and renew it for you.
  21. Unblocked. It was for failed SFTP logins, so make sure you have the right password set in your FTP client.
  22. Unblocked.
  23. Nothing wrong here, that error is the session hijack prevention working as designed. That error is actually caused by your ISP, not us. You need to find out why your ISP keeps changing your IP address, or use a vpn or proxy so it stays the same. Note that this is very normal if you're using a cell phone data plan and moving around.
  24. Glad to see you figured it out. Let us know if you need anything else
  25. You need to change the nameservers for those domains to ns1.heliohost.org and ns2.heliohost.org. You can do that in Freenom's website.
×
×
  • Create New...