wolstech

Postgres uses port 5432, not 3306.

@baileyjm: He did provide it. He's on Johnny, which is famous for this issue, escalating so it can be corrected.

You can make changes while you wait for a domain change to take effect. You just won't be able to see them until the changes finish processing. The only time you can't do this is if you're moving servers (which you're not doing).

That account is suspended for Phishing. For security reasons, phishing accounts cannot be unsuspended, backed up, or deleted. You will need to create a new account and restore any backup you may have. Please be aware that you will not be able to reuse any domains on your suspended account, and will need to pick a new username. We apologize for any inconvenience this may have caused.

The link he posted is how you change that: http://www.heliohost.org/classic/support/scripts/domain Put your username in the first box, password in the second box, and the full domain in the third box (e.g. newsubdomain.heliohost.org). Submit it, then wait an hour or two for the DNS changes to propagate, and it should work (you're on Tommy, so it will take effect on our end very quickly).

Django is widely considered to be the most difficult-to-use thing that we offer. The wiki article is the only working tutorial that I know of. The rest of your program is up to you. If you're having trouble with the tutorial, how far have you gotten and what specifically do you need help with on it (Krydos knows the most about it, I've never personally tried django, I'm a PHP developer almost exclusively)? PHP is a much easier language to develop in, at least in my opinion. It's not picky about things like whitespace, and it doesn't have any format or framework you're constrained by (unless you choose to use one of the many that exist). As long as your syntax is correct, it just works. PHP's flexibility can be seen as a bad thing in many people's eyes though since it can promote the production of bad code.

This support request is being escalated to our root admin.

Since you're on Tommy, you can do this yourself now: https://www.helionet.org/index/topic/29658-servlet-deploy/ Please be aware that it takes several hours to deploy. The URL to your servlet will be shown next to the upload field when the deployment is finished. If a WAR deployment already exists, it will be removed and replaced with the new one.

Can you provide a link to the script in question?

If you're talking about it being slow or throwing 500 errors sometimes, that's probably due to load (typically when Apache restarts). You can see the blue and red spots (which likely correlate to your problems) on the HTTP line of Ricky's monitor here: http://heliohost.grd.net.pl/monitor/ This is normal. The only recommendation I usually have is to try using different software that needs fewer resources, but the fact your site is a very basic template makes me suspect it's just the server being slow. You could try moving to Tommy since uptime is slightly better there (and the server is much faster), but I'm not sure how much of a benefit you'll see.

Unblocked. You were blocked for too many failed SFTP logins.

That account is archived, escalating so it can be restored. As for the domain, you have to point the domain to us at least initially (cPanel requires this to prove you own it). Once it's added and working, it can be moved back to CF and will still work.

Couldn't have said it better myself. For what it's worth, none of us here are WP fans. I'm amazed it's still as popular as it is, especially considering the number of security holes it has and the amount of malware extensions and backdoor'd themes available for it. For a while it was the leading cause of spam and malware suspensions here, though it seems to have tapered off lately (I can only recall 1 or 2 in the past six months). Nowadays they seem to prefer just mass-creating accounts and setting up phishing instead.

We usually recommend http://heliohost.grd.net.pl/monitor/ as an external monitor. It definitely doesn't provide the mail server numbers though. The details of what's running can be seen in cPanel on the status page, but it doesn't provide history, just whether various things are currently up and the current disk space available.

The password reset only changes your cPanel password, so it will only affect cPanel, FTP, and similar services that we provide. Software you installed on your website won't be affected by a password reset. If you want them to match, you need to go change your software's passwords to match.

That IP is not blocked. If you can't sign in, try resetting your password: https://tommy.heliohost.org:2083/resetpass?start=1

OK, that's weird. Escalating to a root admin can look at this further.

Can you try the settings shown in the picture that's attached and post the logs? https://imgur.com/a/6Vkrh (Use your cPanel password when asked)

If you're not able to sign into cPanel, try resetting your password: https://johnny.heliohost.org:2083/resetpass?start=1 The log you originally posted shows you tried using either admin or admin@syngmod.heliohost.org as your username though. The username for your default FTP account is just syngmod with nothing after it. The password is your cPanel password (though as I said above, if it doesn't work for cPanel either, reset it first).

The username and password for FTP is the same as for cPanel. Hostname looks correct (johnny.heliohost.org). For protocol, use SFTP on port 1373 (most secure), or if you really have to, plain FTP on port 21 (insecure). FTPS (sometimes called "FTP with Explicit TLS") sometimes gives us trouble, so we don't recommend it.

I'm not seeing any database problems when I visit that site, though its hard to test that site since every single link I clicked on was broken. It also appears you have something on that site that makes it perform very slowly (probably either your theme, or whatever extension you're using to get the news content). Other sites on Ricky are running much faster, so it's a software issue on your end. I'd recommend just tossing WordPress entirely and replacing it with something else. It's infamous for being a security risk, and can also very easily cause high load when misconfigured or when too many extensions are installed.

It only affects PHP files because PHP files are executed through CGI (Apache passes them to PHP, PHP handles processing and tells Apache what to send). Not sure exactly why Apache does this for PHP (I'm assuming not allowing this provides security of some form), but it just really does not like PHP scripts when they're writable by the group. All your other files (images, CSS, HTML, etc.) are just read from the hard disk and sent to the client. EDIT: Beaten to it.

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. <br /><br />If you still see the suspended page, please clear your cache.

Unblocked again.

Escalating to have this restored.