wolstech

You install it like any other application. It needs a folder inside of public_html so you can access it from the web. After that, follow the instructions it comes with to configure it. I'd also recommend password protecting that folder in cpanel.

Perhaps the webdisk or FTP client are using an old password saved somewhere? Those types of applications will often try over and over to connect when they fail. The brute-force should clear on its own with time. If it doesn't, an admin can reset it for you.

As yashrs said, you can run your own copy if you prefer a different version. Database server is localhost, use your cpanel credentials as the username and password. As for the 4.1+ PMA versions in general, I actually don't like them. 4.0 was OK although not great, and then it became very bloated when everything in it started using AJAX. 3.x has an option to disable all that javascript junk and have a traditional post-back-based application...I much prefer it over AJAX any day. They removed that option in v4 for some reason. Also, please stop asking us to upgrade things. We're aware of the newer versions. So far, you've asked us to upgrade mysql, php, apache, and phpmyadmin. While the concern about old versions is appreciated, we're using them for many reasons, the biggest of which is because some programs are not backwards compatible (PHP 5.5 is a good example), and upgrading requires time to make sure things won't break and to fix the things that do. If you like newer versions, you should consider Johnny since that's where new stuff will usually appear first when we get it. All of them are somewhat newer over there now, although by rather minor versions.

I keep getting malware warnings from 2 different AVs (AVG and Malwarebytes) when trying to open either of those. Alert is a connection to malicious IP address 31.170.163.172 from malwarebytes and malicious JS file from AVG. Please look into this. Homebux.com.br is not queued though. In fact, it's not even be hosted here. Homebux.heliohost.org does not appear to be valid (it won't resolve).

That periodic MySQL downtime sounds like Stevie in general these days. My site does that too...spitting out "FATAL: cannot connect to database server" half the time. No fix except to wait, and there's no estimate on the repair time as far as I know. I'll agree it is very frustrating.

The 500 error could be a lot of things. The most common causes are errors in htaccess, hitting your process limit (usually being logged into cPanel does it), or high server load. The database error could be the db server being down, which it is quite a bit these days, or a configuration error like a bad password. If it comes and goes on its own, odds are the server is just down. The domain mapping issue is odd...did you change your main domain and include the www by mistake, then change it again to correct it? If so, you need to recreate the subdomains.

The downtime and inability to edit your posts are related to the database crash in February. The database server downtime is unfortunately normal on Stevie for the moment, but the inability to edit posts sounds like InnoDB tables. You can check for InnoDB tables by going into phpmyadmin and selecting your database. In the list of tables, see if any of them show InnoDB in the "Engine" column. If they do, you should convert your database tables to the MyISAM engine. To do that: Make a backup of your database through cPanel or phpmyadmin. You want a plain text (.sql) file. Open backup file in a text editor, then do a find and replace. Find all ENGINE=InnoDB and replace them with ENGINE=MyISAM Save and close the backup after editing. Create a new database in cPanel, then import the edited backup into it using cPanel or phpmyadmin. Assign your website's database user to the new database in cPanel. Edit the config file for your website to use the new database name. Ignore the old database. Do not attempt to drop it. Also, for what it's worth, right now that account's main domain won't resolve for me. Is that the site you're referring to?

That error is likely because you're creating an InnoDB table or importing a schema that includes InnoDB tables. InnoDB does not work on Stevie due to damage from a crash in February. Modify the schema to use MyISAM tables and the error will go away.

Johnny is really slow or down a lot, usually due to excess load. Uptime is only like 80-85% compared to Stevie's 99+%. Johnny is often down multiple times per day. If you check the server monitor site, you can see the difference in load and uptime. It's due to the fact we offer more features on it, allow each user to use more resources, and have more users in general on it since the sign ups aren't limited. On the upside, MySQL isn't broken on Johnny. If you need any kind if reliability or uptime, which it sounds like you do, do NOT move to Johnny.

Good to see the FTP issue is cleared up. As for the database issues, the connection issue and inability to drop databases are all related to the crash Stevie experienced in February. Unless you want to move to johnny, there is currently no fix for any of them. You will need to not use innodb, ignore the extra databases that won't drop, and tolerate the MySQL server downtime.

The database issue has no fix right now. Just ignore the extra database in phpmyadmin. Once Stevie's MySQL is fixed, an admin will need to drop it for you. The FTP issue sounds like either you using the wrong host, or port 21 being blocked on your end. What settings are you using (host and username)?

That site is working fine. I see this: http://imgur.com/YjXrjP3 Clear your cache again, and if it still does not work, try a different internet connection.

Not sure what was up with this one. It was showing as active but was actually suspended... Your account has been unsuspended.

Error 1045 is Access Denied, so likely a password or suspension-related issue. Try it again now. If it still doesn't work, try changing your password in cPanel. When you change it, be sure the box for "allow MySQL password change" is checked. After that, log out, then back in and try again. .

@yashrs: actually it's the other way around. A records do NOT work if you use it as an addon or parked domain (it won't let you add it). You need to set it as your main domain to use an A record. Also, proudlyb, please do not TYPE IN ALL CAPS, do not repeat the same thing 6 times, and please use proper grammar. It is quite difficult to understand you. If it is not working, it isn't set up right. What are you seeing when you visit your site, what is your username, and what is your domain?

CSS is another language used for describing the appearance of elements on a website. It sounds like your book should cover it. Font tags are commonly used in books for beginners because they are easy to understand and eliminate the complexity associated with CSS. They technically shouldn't be used anymore on published sites because they are from an older HTML standard, but that's not to say they won't work, as all major browsers still understand them. Since you're a beginner, you might just want to keep the font tags for now.

Our name servers are ns1.heliohost.org and ns2.heliohost.org. Do note though that NS2 is often slow to respond (or down entirely) because it is located on the same server as Johnny. Some people have reported trouble adding it to a domain because their registrar verifies it's availability. If this happens to you, your website will work fine with just NS1, and you can try adding NS2 again later.

Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/home/support/scripts/renew. To prevent this from happening in the future please remember to visit http://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.

The innodb tables are read-only, so you won't be able to remove their records. If you have any MyISAM tables mixed in with the innodb tables though, you can remove the records from those particular tables (or drop the MyISAM table entirely.)

There are a few issues that doing the above won't fix, but those cases are few and far between. The above is thorough enough for many people. Some things to add: In step 6, you can't drop any databases that have InnoDB tables if you are on Stevie. Doing so will bring down Stevie's mysql sever for a few minutes, and will also leave them in a state where they are gone from cPanel, but still exist in phpmyadmin. Also, if you use cron jobs, be sure to delete them by going to the cron job page of cPanel.

Aside from the very outdated HTML (<font> tags are obsolete, use CSS for fonts), some code comments I have after a very quick look are these: <h1 align= "center" class= "blueshadow"><font color= "red" size= "8" face= "Comic Sans MS">Save a Pet</h1></font> You opened the <h1> first, but closed the <font> last. The first thing opened should be the last thing closed. Move the </font> inside of the </h1> so the header is closed last. <a/> Typo for the closing tag on your pet finder link. <td><img src= "images/shelterdog3.jpg" width= "200px"</td> The closing > is missing on your <img> tags for all of the images in that table.

That account is not suspended. If you are seeing the suspended or queued pages, please clear your cache.

The page renders fine in my browser when I copied it to an html file. The images are missing, but I expected that since I don't have them. What problems are you having with it?

I'll assume you reached that from the features page...it should be http://www.heliohost.org/home/features/databases Fixed.

InnoDB tends to trash itself more frequently when MySQL crashes. MyISAM can crash too, but it is more stable than innodb is, and repair is often easier if something does happen.