wolstech

Correct. That command makes windows forget all the looked up addresses in its cache. If you run that, the next time you visit the domain, it will have to ask a DNS server instead (typically one run by your ISP unless you've changed your settings manually). A DNS server can either be the one that holds the records about the domain (the "authoritative" server), have the answer cached already from previous lookup, or look up another server that might know and pass on the request. Eventually it'll reach the authoritative server and get the address it needs. A complete look up from end to end for domain.com would be something like this. In reality, these servers will have caches of their own and may not actually need to ask the next one in line because they remember from before (this was your problem...either your PC or the servers remembered from before, not realizing the answer had changed in the meantime). The below is simplified quite a bit, but explains the general process. PC checks if its cached. If yes, use the data in the cache.PC asks the configured DNS server to for information for domain.comDNS server doesn't know where it is, so it starts working down the chain, starting with ".", also known as root. This is to the right of the .com, but that period is generally not written. The internet root servers are asked where the servers for ".com" are (most servers will generally have such information already and not actually need to ask the root servers).DNS server then asks the servers for ".com" (of which there are VERY many) where domain is.The ".com" DNS servers return NS records pointed to ns1.heliohost.org and ns2.heliohost.org. NS records basically say "these servers are the ones responsible for the answer for domain.com. Ask them."If an A record was found here instead of the NS records, the IP listed in the A record would be returned as the answer and the lookup would be complete.This step is one of the reasons you have to wait for DNS propagation when you change your nameservers. Because there's many DNS servers that handle answers for stuff under .com, they all need to know the answer to this question. Lookups can fail if you get one that hasn't been informed of the answer yet.Assuming an NS record was returned, ask the name servers listed, and they respond with an IP for domain.com. The response is passed back to your PC.PC connects to the IP given and asks for content.

Do you know what the username or email address was?

It's not suspended for me...I see the 500 error, which could be caused by many things. Broken code, invalid .htaccess files, or incorrect file permissions are most common. Check that your permissions on your index file are 644 (not 664, which they upload with if you use SFTP). Rename your htaccess to disable it. If none of those help, your code is probably broken. If that's the case, you can try renaming your index file so it doesn't run and verify that your account shows a directory listing.

The account ragua070 has been unsuspended.

Unsuspended. Please delete the file listed above immediately and fix your wordpress issue within 24 hours.

Your WordPress theme has malware...WordPress is infamous for its security. We recommend not using themes and extensions for random websites because many of them contain backdoors or other malware. We recommend that you delete your entire wordpress installation and reinstall using up to date components from reputable sources only. Also be sure to keep everything updated after you reinstall, as WP itself and its extensions receive security fixes regularly. My personal recommendation is to just not use WordPress at all (WP is a leading cause of malware suspensions here at HelioHost, and is probably the most poorly written CMS available in terms of security). Whatever you do, do not use your theme again. Are you ready to fix the problem?

That account is permanently suspended for phishing.

Multiple accounts, same user as http://www.helionet.org/index/topic/28015-suspended-ragua070/ Please refer to the above topic for assistance.

Multiple accounts, same user as http://www.helionet.org/index/topic/28015-suspended-ragua070/ Please refer to the above topic for assistance.

You're suspended for having 10 accounts. You're only allowed one. Which account do you want to keep?

@flpcarv, you have 24 hours from now to move your account contents to your new account and delete your old one. You're only allowed one active account at a time. The easiest way to get everything from the old account is to download a full backup. That way you have all your files and databases. The forum account will stick around regardless of what he does to the hosting account. If he wants to continue using the flpcarv forum account he is welcome to do so.

What error do you get when you try adding it?

Yes. You need to delete your account, then sign up again on the new server and set everything up again. The information is a little outdated though. The deletion usually occurs within an hour of you requesting it (if not instantly), so no need to wait 2 days. Once that happens, you can sign up again assuming registrations are open. Just be sure to not reuse the same username (it will fail since the matching forum account already exists), or ask us to rename your forum account before signing up again if you really want to reuse it. We currently can't move accounts.

Krydos would be able to tell you that. Escalating and un-[solved] so he looks at it.

You were indeed suspended for causing high load. Please fix your script quickly. You've been unsuspended.

That would need to be implemented yet. It's just an idea we've been floating for a while. We haven't decided officially if this is a route we want to go, or what the prices would be if we do (the numbers I gave were based on your example). I'll move this over to Escalated so Krydos remembers to look at it again since there's interest here

That'd be another alternative. Basically the same principle but paid up front. Could also offer a discount for doing that. $2/month, or $20/year.

The login form there uses the cPanel login system, so you can reset it using cPanel's reset feature as well (many have reported that the cPanel password reset works more reliably too, so I usually suggest doing it this way). If you forgot your password: Johnny: https://johnny.heliohost.org:2083/resetpass?start=1 Tommy: https://tommy.heliohost.org:2083/resetpass?start=1 If you know your password and want to change it: Johnny: https://johnny.heliohost.org:2083/frontend/paper_lantern/passwd/index.html Tommy: https://tommy.heliohost.org:2083/frontend/paper_lantern/passwd/index.html

This might be a DNS issue related to recent changes we've been making on Cody. Krydos will need to look into this further. Normally we would leave HelioNet issues down here in this forum, but since the wiki is down entirely, I'll move it to Escalated for you.

Some people have issues with using the heliohost.org site to log in too. If that doesn't work for you, sign in using https://tommy.heliohost.org:2083/ instead

This support request is being escalated to our root admin.

The way krydos does it, I believe it needs to be runnable in a browser, so it will need to be inside public_html somewhere.

It may be, especially if you have multiple domains that point to the same cms install (say, a .com, .net, and .org...I run such a site, though currently on another provider). Similarly, we have several users here who successfully run 10+ sites on a tommy account with no issues. The question I'm posing is more "Why bother with the other limits if the disk space and CPU/RAM use ultimately dictates how much you can fit on an account anyway?"

Bdistler: If we severely crippled it like that, nobody would use it. It would basically make the server as useless as they are on competing providers who try to later upsell you. One of HelioHost's main goals is to not have all that nonsense. In fact, we'd be competing with ourselves...if I have to wait until midnight either way, and can pick a severely crippled server or one with more functionality and not crippled, where am I going to go? Remember registrations will be limited on Ricky like they are on Tommy The server is fully capable of being stable while allowing unlimited domains/bandwidth/etc. It used to host 10,000 accounts with only a limit on disk space and cron and 30 day inactivity suspensions, and it was perfectly fine.

We're in the process of setting up a new server named Ricky, which will act as the replacement for the crashed Stevie server. Ricky is a Virtual Machine that lives on Stevie hardware (much the same as Tommy lives on Eddie). We would like to know what PHP version you all want to see him run. Stevie ran 5.3.x, and some have asked for the replacement to run 5.3 to offer a server for legacy application support. While PHP is often backwards-compatible, it's far from perfect. A lot of older software that is no longer in development doesn't work properly on 5.4 and newer and will never be updated, and thus cannot be run on our service. In addition, finding a web host that still offers 5.3 for these applications is becoming more difficult every day, and finding a free one is rapidly becoming nearly impossible. Others think we should provide a multiple PHP setup like Tommy. This would basically provide us with additional capacity for stable accounts. The limitation here is that MultiPHP Manager and PHP 5.3 are incompatible with each other. If we offer MultiPHP like Tommy, we cannot offer 5.3. It will have the same versions of PHP as Tommy (5.4 - 7.1, your choice in cPanel). It's also possible that we could offer a single, newer version of PHP such as 5.6, like we do on Johnny. What do you all think we should do? Feel free to post comments in this thread, and be sure to vote in the poll.