wolstech

I see the same thing when using pgAdmin, so it's probably just how they have it set up. I feel like it could be a security issue, but the data in the databases isn't accessible, only the structure is, and read-only, so its not too much of a risk. Almost every database has GRANT CONNECT, TEMPORARY to PUBLIC, which won't let you do much. I've seen far worse.

I see the hello world post in a new install of WordPress. If you still see the Queued page, please clear your cache.

I've had issues with using cP's file manager for .tar.gz archives in the past. In my case they'd just stop mid-upload. Try uploading it via FTP then just extracting it from the file manager. That worked for me when I had the issue. Alternately, you could just unpack it and upload the files inside via FTP.

This happens every few weeks. Both servers seem to be working now. I just logged into both without issue.

That domain is showing a directory listing "Index of /". If you still see the queued page, please clear your cache.

The sign ups on Stevie are limited per day. They open again everynight at midnight Pacific, so try signing up again just that time. When you go to sign up, select the free (non-SSL) account since you already paid. Once the free account is created and active (it takes a day or so to become active after you sign up), post in Customer Service so an admin can verify the payment and give you the dedicated IP address to use SSL. As for the system letting you pay anyway despite the account signup limit being reached...I'll agree that it is a bit silly.

Was showing Queued earlier for me, but now seems to be working normally. Odds are you simply hadn't waited long enough for the domain to become active. We say 24 hours which is usually accurate, but it can take longer sometimes, especially on Johnny where high load can be an issue at times. Anyway, if you still see the Queued page, please clear your cache.

As Sove said, this domain is now working. If you still see the Queued page, please try clearing your cache.

WordPress is almost certainly the cause. Was it up to date? Many of the minor updates to it are to fix issues like these, but a lot of people don't realize that or forget to install them. Also, even if plugins are legitimate, they can have vulnerabilities that can be used to hack your site. There are lots of legitimate plugins and themes, both paid and free, whose newest version has security holes. Using paid plugins or themes will help reduce the risk of vulnerabilities or intentional back doors, but there is no way to eliminate the risk entirely. The more popular the software is, the more likely it is to be targeted by hackers. WordPress and popular plugins are such a target because they are heavily used. Odds are extremely good (I'd say 99.99%) that it was NOT Heliohost's fault. If it were, everyone else would be having the similar problems with their site. WordPress is easily the most common CMS I see "hacked site" posts for, and it's almost always due to someone using outdated software, outdated plugins, plugins with security holes, or themes with malware. I'd recommend you get the latest version of WordPress and whatever plugins you use and update everything. You might want to make a backup and antivirus it as well.

If you think your cPanel password is compromised, change it first. The more likely problem though is vulnerable software installed on your site. It happens a lot. You didn't post a link to your site so I don't know what software you're using, but software vulnerabilities are common. WordPress and Joomla are two well known programs that are infamous for being easily hackable, especially if you install random plugins/extensions. Also, many of the "free" WordPress themes you find online at random websites are actually backdoors designed with to let in hackers. If you use such software on your site, make sure to keep everything updated. Also, remove any themes and extensions you installed, and only install ones trusted sources.

Not sure what that is, but it is not Heliohost's suspended page. If your Heliohost account was suspended, you would be seeing this page instead. You might want to try flushing your PC's DNS cache. Also, can you try another computer on the same network? An admin might have some more ideas as to what's going on with this.

Have you tried clearing your cache? You also are using Cloudflare, so it's possible that it could be a problem. Also, like Sove said, your account doesn't seem to be suspended. Reizn.com is working fine for me.

Something might still be wrong with that domain. I can't resolve it to anything meaningful. Nslookup gives "server failed" whenever I try. If it still won't let you add it saying your nameservers are wrong, talk to your registrar. It sounds like they didn't do something right on their end after you changed them.

Dubbels.co.uk is showing a directory listing. If you still see a suspended page, please try clearing your cache. Also, dubbels.co.uk looks like it is on Stevie.

The easiest and recommended way to get to cPanel is to visit www.heliohost.org and log in using the username/password you chose during signup. The log in form is at the bottom of the page. If you haven't signed up yet, you can do that here: www.heliohost.org/home/signup.

You can create a database here: http://rentersguild.com:2082/frontend/x3/sql/wizard1.html Enter a name for the database, click Next Step. On the next page enter a username and password for the database and click "Create User". On the final page, check "All Privileges" at the top of the list, then click "Next Step". Wait for it to say it was created and added successfully. That's all there is to it. Just a note: Your database user and database name will both start with your cpanel username and an underscore, even though you didn't type that part in when you create them. The names will look something like guild83_DBNAME and guild83_USERNAME.

An admin would need to add the extra software for you if you wanted it in softaculous. As for Open Real Estate, you can install it yourself quite easily. The developer's website for Open Real Estate is here: http://monoray.net/products/6-open-real-estate There's a link to an English download and an install guide on that site. It's pretty much a matter of uploading the files, setting permissions, creating a database and DB user for it through cPanel, then visiting it in your browser to configure it.

I see this: http://i39.tinypic.com/bwrxi.png You said you've cleared your cache already...perhaps try another browser or another PC?

Uproo.tk seems to be working. If you still see the queued page, try Clearing your Cache.

Use this to change your main domain: http://www.heliohost.org/home/support/scripts/domain

That subdomain is queued. Did you wait 24 hours after creating it? All domains and subdomains take up to 24 hours to start working after you add them.

Totally missed the username here. If you make a DB user called ix-c and your HH account is gagetboy, it will look like "gagetboy_ix-c". The password will be the DB user's password, not your Heliohost password. The hostname...I didn't even pay attention to it since his original error showed "gagetboy@localhost". Oops. Honestly, I can't recommend one since I ended up making my own. I faced a similar issue back when I developed my site. I started with a very basic (as in, so basic it was 3 files, and like 4 functions) system from the net for a framework and coded a bunch of things to fix the major security issues. If you do what Shinryuu suggests and fix host and username, it should work. You can get away with using this one as long as you don't use it to protect anything that's very sensitive.

Assuming that there's a DB called gadgetboy_ix-c and an SQL user added to it called gadgetboy, then yes. I looked at the code for that reg system last night...it's not you I don't think. The registration system isn't the best out there...it took me an hour to get it working, and then I managed to break it easily. I didn't bother testing it, but a quick look reveals a lack of protection against a variety of attacks as well (not sure how secure you need this to be). I'd go find a different registration system rather than try to get this one working...

You need a database user. It sounds like you're confusing database users with the user accounts that people will create through your website. They are entirely different. I can't tell if you did this or not so try this: Visit http://ix-c.heliohost.org:2082/frontend/x3/sql/index.html (log in with your cpanel username and password). Create a user on that screen called gadgetboy if it doesn't already exist. Then add the gadgetboy user to the database using the form at the bottom of that screen. Make sure the password for the user you create there matches the one in the PHP file. If you did this already and are still seeing the error, something might just be wrong with that registration system.

That looks like a user or permission issue. Did you create an SQL user called gadgetboy? Did you add that user to the database you are using for the login system? Is the password correct for that user in the php script?