Krydos

Ok, some progress was made. The problem was with the linking of the libraries which can always be a little tricky in linux. Especially when the system has several thousand users. There is still an error, but I think this one is in your court now. I'm going to mark it as solved for now, but let us know if you're still having issues.

You said it yourself. clovisd 5309 0.0 0.0 10580 852 ? S 06:17 0:00 /usr/lib/courier-imap/bin/imapd /home1/clovisd/mail/clovisd.com/timur clovisd 7830 0.0 0.0 12668 948 ? S 05:37 0:00 /usr/lib/courier-imap/bin/imapd /home1/clovisd/mail/clovisd.com/timury97 clovisd 7874 0.0 0.0 12668 944 ? S 05:37 0:00 /usr/lib/courier-imap/bin/imapd /home1/clovisd/mail/clovisd.com/timur clovisd 7963 0.0 0.0 10580 852 ? S 05:37 0:00 /usr/lib/courier-imap/bin/imapd /home1/clovisd/mail/clovisd.com/timury97 clovisd 8017 0.0 0.0 10580 768 ? S 05:37 0:00 /usr/lib/courier-imap/bin/imapd /home1/clovisd/mail/clovisd.com/timury97 clovisd 18151 0.0 0.0 10580 856 ? S 10:42 0:00 /usr/lib/courier-imap/bin/imapd /home1/clovisd/mail/clovisd.com/timur Close some of your mail clients and you'll probably see a lot less 500 errors on php.

The problem seems to be that one of my predecessors upgraded postgresql to a version unsupported by cpanel, and didn't upgrade the software that creates backups of databases. Try creating a backup of your database yourself with phppgadmin and let me know if it works now. Otherwise, at least I can keep manually creating postgresql database backups manually for anyone who needs it.

Ok, http://raxsoft.tk/temp/fsock.php works now. We don't publish a publicly visible list of open ports for security reasons. Generally if someone has a legitimate reason to need an open port we PM/email it to them privately.

Please set your custom dns nameservers to ns1.heliohost.org and ns2.heliohost.org http://byrondallas.heliohost.org/php/tools/dns_records.php?domain=bakielani.tk&rec=NS

Just from experience it seems like proxy scripts, and abusers of php curl cause a lot more load and tend to get suspended quite often. This is probably why a lot of web hosts disable curl and disallow proxy scripts and other high load scripts that accomplish the same type of thing. Here at Heliohost you can use whatever scripts you want as long as they aren't illegal such as a phishing site, but we do suspend users that cause too much load. Curl can be quite useful and I use it a bit on some of my own personal pages, but you can't overuse it just like you can't overuse anything. Proxies are kind of silly because the internet is already full of literally millions of them, so I don't really understand why people risk having their hosting account suspended just to host one of their own. Heliohost doesn't have an age limit, but where ever you live might have laws preventing you from doing certain things. For instance if you live in the US and are under age 13 you might need your parents permission to do certain things on the internet.

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. If you still see the suspended page, please clear your cache.

The domain mazix.heliohost.org appears to be working fine, and cocbonds-noisok.org looks like everything is set up correctly as of the time of this post. I recommend waiting another 24 hours without changing anything from the time of this post and if it's still showing queued let us know. Sometimes Johnny accounts can take a little longer than 24 hours to come out of queued status due to higher server load. The solved flag just means that Heliohost staff knows that there isn't anything more than can be done on this issue. If the issue still isn't resolved 24 hours from now the solved flag can easily be removed.

Please post the following information: Your cPanel username Your main domain The server that you are on

Payment confirmed. Dedicated IP granted.

The domain example.com is not hosted on our servers. http://byrondallas.heliohost.org/php/tools/dns_records.php?domain=example.com&rec=A If you're using incorrect domains to be intentionally vague then I'm afraid no one can help you because no one can understand what your issue is.

Why not?

For clarity, running a cron job every five minutes would result in 288 cron jobs in a day which greatly exceeds the limit of 2. You can run two cron jobs each once every 24 hours, or one cron job every 12 hours. Either will result in 2 cron jobs in a day.

Check out the file mrty_ttrssp.sql in your home directory. Let me know if it looks like it dumped properly.

I am unable to find any logs referencing any visits to your site during the time frame determined above.

I'm unable to reproduce the "libpng16.so.16: cannot open shared object file: No such file or directory" error. Can you post a link to the script that causes the error? Also I'll let you in on a secret, it might seem a bit counter intuitive, but I always try to work on the topics that are the oldest first. So, when you "bump" a post it actually moves it to the bottom of my todo list each time.

Your normal email sending limits have been restored.

Granted.

What do you need two accounts for?

The account in question has been suspended.

I'm still in contact with gmx.com customer support. They are rather slow (slower even than me) but they're trying to figure out what the problem. I'm fairly certain the problem is on their end anyways. I'll update this thread once they figure out what the issue is.

No amount of domain changing will ever work, whether it's using the main domain change script or an admin trying to change the domain for you, if the domain already exists in the system. Since you already have the domain blacktempest.net parked on your account it blocks anyone from changing your main domain to it. The solution to this is to delete all traces of blacktempest.net from your account prior to trying to change your main domain. Since you've been struggling with this for a while I went ahead and made the change for you which you can verify in cpanel.