hussam

env looks for 'python' in PATH variable (/usr/bin/ doesn't need to be in PATH to work) then looks in the standard /usr/bin. This works around situations where python is not installed in /usr but instead in /usr/local/ but /usr/local/bin is defined in PATH. env prints all currently defined environment variables.

your website opens fine. it shows the mybb page. you really did not need to delete wordpress, just secure it while you update it.

For the record, all your visitors are going to show up as cloudflare IPs in error logs because you are behind cloudflare proxy.

Go to cloudflare control panel and under basic security protection, select "I am under attack". Wait a few minutes and go to your website. There is a major DDoS targetting XML-RPC in Wordpress and Druapl right now. Upgrade to Wordpress 3.9.2 to fix the bug causing the DDoS. Then remove the "I am under attack" setting and your website should be back to normal.

I worked around this problem by pointing my .eu.org domain to cloudflare DNS and then add a A record on cloudflare dns setting to heliohost IP (found in your heliohost cpanel account). just create a free cloudflare account and you will be up and running in 5 minutes.

There apparently is an xml-rpc attack in the wild targetting random websites since around the 20th of july, two weeks ago. From what I understand, they use yourwebsite.com/xmlrpc.php to gain access to your website by bruteforce username/password cracking attempts. http://blog.sucuri.net/2014/07/new-brute-force-attacks-exploiting-xmlrpc-in-wordpress.html Unless you need the ability to post using mobile applications or some desktop applications like bloglio, you may not need the xmlrpc.php functionality (correct me if I am wrong here). If you find yourself under attack, adding this to .htaccess seems to help: RewriteRule ^xmlrpc\.php$ "http\:\/\/0\.0\.0\.0\/" [R=301,L] It redirects the bot's requests to xmlrpc.php to http://0.0.0.0 on the machine the bot is running at. Update: The denial of service vulnerability has been fixed in Wordpress 3.9.2 so the above workaround is no longer needed.

host eaglezaptech.heliohost.org eaglezaptech.heliohost.org has address 64.62.151.109 eaglezaptech.heliohost.org mail is handled by 0 eaglezaptech.heliohost.org. Sometimes these things take time to propagate.

Which language? If php, read the php manual.

Ummm...I wasn't suggesting you remove your heliohost account and recreate it... I was thinking remove entry from http://dot.tk/ and recreate it. But if Yashrs spotted where the problem at your heliohost account, please let him handle it.

well right now, there doesn't seem to be any A, or CNAME records for photoncoin.tk. There is only the Nameserver record pointing to NS2.HELIOHOST.ORG and NS1.HELIOHOST.ORG So this is either a glitch at dot.tk or heliohost. Cloudflare *might* fix this if it is not a dot.tk problem because heliohost is responding if I hardcode ip to host in hosts file but it is better to know where the problem is first. Will deleting photoncoin.tk and recreating it at dot.tk be an issue?

I have been thinking about this and I have no idea what is happening. Out of personal interest, can you place a test file in your account called test.html with "this is a test file" text inside it? I want to place an entry in my hosts file: 64.62.211.131 photoncoin.tk www.photoncoin.tk and see if I can open http://photoncoin.tk/test.html That might rule out a glitch from heliohost's side. Edit: I just tried that anyway. This is what I get when I open photoncoin.tk with the ip address hardcoded in my hosts file. http://i.imgur.com/j8cq6x8.png Is this your website? If that is your website, then we can try using a 3rd party dns service like cloudflare (I use that on my website) and just point the domain through it to heliohost ip.

Sql connection error is common on stevie although less now than before. 500 error can happen if you are logged onto cpanel or phpmyadmin. It usually clears out on its own in a few minutes after you log off cpanel (that is at least what happens on my account).

Under firefox, ctrl+F5 bypasses cache. Try if it works under chrome as well

If this an addon domain or the the domain you registered your heliohost account with? I'm out of ideas, sorry. This looks like something that Heliohost staff may want to take a look at.

It works. Thank you Byron

Hi, I was trying to wget --mirror my website using my backup script and it started refusing all ftp connections. I also cannot connect to stevie.heliohost.org:2082 either now. I suppose I triggered some firewall alert with the concurrent connections from the backup script?

No idea why. Do this instead: Try selecting "Dot TK DNS Service" instead of custom dns and point the A record to your hosting account's IP. So: A Record | photoncoin.tk | IP Address of your website. The IP address of your website should be somewhere on the left side in your heliohost cpanel account if you scroll down.

Yes, whois photoncoin.tk says: Domain Nameservers: NS1.HELIOHOST.ORG NS2.HELIOHOST.ORG Maybe remove ns2.heliohost.org so that it defaults to the first one.

The best advice I can give you is don't spam. Post good comments that are on topic. Look for blogs about things you understand. For example, if you like games, look for blogs about games. Comment on games you know or play. If you like cooking, look for blogs about cooking and comment about the recipes....things like hat. Akismet is smart enough to identify generic comments such as "i visit your blog from time to time. really informative." as obvious spam. Note: If you don't already know, Google bot also identifies spam. When your website address is submitted to google, it is crawled, and all words are added as keywords. A heuristic assessment is automatically done and your website ranks as high as the system assumes your site may be useful to users. For example, if your website is mostly about cooking, a comment or post that contains the word SEO will cause a lower rank for that page. Google will assume the existence of the word SEO (off topic to the website) (sudden appearance of the keyword SEO) (low keyword rate of SEO) is an indication of spam. If a page ranks too low, it may even get purged after 90 days if it not crawled again. That means no one will find your backlinks. Google follows internal links and not backlinks anyway. Even if Microsoft.com links to your website, you won't actually rank higher.

Did you point your domain nameserver to ns1.heliohost.org? Go to dot.tk and check that the name server settings.

In terms of bandwidth and disk space, you will need a dedicated server for something as large as Deviantart. It will probably cost you over 200 dollars a month. But start with something smaller like good shared hosting. It will only cost around 10 dollars a month. Then upgrade as needed. You will need a php script. If you can code one yourself, it may take a week or two and you will need to maintain it. You can always hire someone to do so but make sure your contract with that person includes a clause for at least 2 months of support because bugs will show up. Another choice for a script is to check for existing advanced photo gallery scripts.

Is there really any needed feature in 5.6 anyway? I know 5.5.3 brought 4byte characters in utf8 charset which johnny already has. But most scripts are fine with 5.1 and will continue to be so for the foreseeable future. On my own computer, mariadb 10 (based on mysql 5.5 with mysql 5.6 patchset) uses around 30% more memory than mysql 5.5. The best database server in terms of memory and efficiency that i have seen is postgresql but sadly wordpress doesn't support it.

I second that request too for Stevie. While I understand that Stevie is in freeze status when it comes to updates for sake of stability, the state of mysql server is less than stable right now. This is mostly because it was pointed that newly (non corrupted) innodb tables can crash the server as well. This indicates a corrupt installation (corrupt innodb driver library or configuration). As this is a minor update, php's mysql module won't need a rebuild (no ABI change). This all may warrant the risk of an upgrade. And this is assuming it is actually physically possible to do so as /usr on stevie appears to be completely full. Administrators, please think about it for a few days. Thank you.

So this is very likely simply a corrupt mysql installation, correct? That would explain why creating new (non corrupt) innodb tables crashes the mysql server. Have you guys tried recompiling/reinstalling mysql?

If you SELECT from the tables, it works fine. If you UPDATE/INSERT/DELETE data in such a table, it fails with "Got -1 from storage engine" but generally won't crash. Creating/altering/dropping the tables themselves (or databases containing them) seems to frequently cause a crash. So a script trying to create a new InnoDB table can cause a crash as well?