Krydos

Done. You should now be able to log in and your website should be working again.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

That wordpress install was hacked, and used for illegal activity. I have removed your domain and your email address from the hacked account and sent you an invite to create a new Ricky account. You'll need to use a different username though. Click the link in that invite and it will allow you to create a new account even though the server is full for the day. Once you create your new account you're welcome to restore your latest clean backup of your site that you may have, but we strongly recommend NOT using wordpress for this very reason. Wordpress is incredibly easy to hack, and a lot of the time hackers will start hosting phishing websites on your domain once they get access. This gets your domain flagged in all major browsers as a malicious site, and visitors to your site will get a giant red warning. The easiest way to prevent all that from happening is to not use wordpress at all. If you insist on using wordpress anyways please be aware that most free themes and plugins are actually infested with backdoors that hackers can use to easily upload whatever they want to your account. So only use themes and plugins that you know are clean. Let us know if you have any questions.

The people over at hostingadvice.com actually went to the effort of contacting us and asking for a phone interview. He called exactly when he scheduled it and we talked for 30-45 minutes, and wrote a pretty decent article. The second source, top10-webhosting.co.uk, basically just read the other article and copied it. They at least asked for a trial account so they could test things out first hand, but yeah. Pretty lazy. After wikipedia deleted my first article I did actually contact a few "news" type sites pitching the non-profit web host angle, but I didn't get any replies. Anyone is more than welcome to try to find websites that want to write about us. Hostingadvice and top10-webhosting both happened organically though. They found us, and thought we were interesting enough to write about.

Done. You should now be able to log in and your website should be working again.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

You last logged in on December 18th, which is less than 30 days, and your account is active. Your domain is working and is definitely not queued. If you still can't login, have you tried resetting your password? https://www.heliohost.org/reset/

Mcrypt is already installed on Tommy's PHP 5.4, 5.5, 5.6, 7.0, and 7.1. Mcrypt isn't available for php 7.2.

Press F12 in your browser. The reason the padlock isn't showing up is because you have an http link to an image when it has to be https. Mixed Content: The page at 'https://radioretroperu.com/' was loaded over HTTPS, but requested an insecure image 'http://rc1.nobexinc.com/AlbumCover.ashx?SongID=28326398&Size=300&FallbackStationID=42913&likeID=28326398'. This content should also be served over HTTPS.

Which version of php are you using?

Unblocked.

That transaction ID has already been used to create a Tommy account. Just be sure to delete your Johnny account with http://www.heliohost.org/classic/support/scripts/delete when you're done copying stuff over otherwise you run the risk of getting suspended for having more than one account.

I still see cloudflare nameservers https://mxtoolbox.com/SuperTool.aspx?action=dns%3aprofessorparticular.info&run=toolpage You're welcome to use cloudflare, but while you are you won't be able to get much support from us other than "use ns1.heliohost.org and ns2.heliohost.org" because cloudflare blocks us from being able to see anything about the domain by design, and we don't have any access to their system. The way we recommend using cloudflare is get everything set up the way you want so it works, and then switch to cloudflare and have them copy our working settings. If you're unable or unwilling to use our nameservers you'll need to contact cloudflare for support.

The problem is with cloudflare, not us. Set your nameservers to ns1.heliohost.org and ns2.heliohost.org. After your domain is working you can have cloudflare copy the working settings.

Yeah, if you can't get access to gmail account we have on file anymore your old account is lost. The reason you can't use a whatever@vinws.org email address is because that domain would be hosted on the account. If there was a problem with the account we wouldn't be able to send you an email about it because the account that hosts the email address would have a problem. Just use your new gmail account to sign up again. I changed the domain on the archived account so it shouldn't block you from using that domain now.

Remote access enabled.

They must not have liked the two news articles that have been written about us recently. The next time someone writes another news article we'll try again I suppose.

Done. You should now be able to log in and your website should be working again.

Once you've added the domain to cpanel you're welcome to change your nameservers to whatever else you'd like though. This is the way we recommend people set up cloudflare.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Thanks for trying!

The directory would need to be 777. Directories have to be executable. 755 is a standard directory, and public_html is special and gets 750. /home/cridus10/ is also special and actually has 711 permissions. All of the directory permissions I've listed are executable though.

It looks like there are some plugins that would maybe do that https://plugins.roundcube.net/search/?tags=calendar Keep in mind you won't be able to install a plugins on the cpanel version of roundcube, but you can install roundcube into your public_html directory and then install plugins there.

Cpu usage = Unlimited on all three servers. If your account starts to cause significant performance degradation or downtime for the other accounts due to overusing the cpu it will be suspended to keep the other accounts online. Memory usage = Unlimited on all three servers. If your account starts to cause significant performance degradation or downtime for the other accounts due to overusing memory it will be suspended to keep the other accounts online. Bandwidth = Unlimited on all three servers. We have multiple accounts that regularly transfer around 100 GB per week each. You probably don't need to worry about bandwidth. Download/Upload speed = I tested it on all three servers, and the lowest I got was 9 MB/s, the highest I got was 31.6 MB/s. It will depend a lot on server load and how much bandwidth other accounts are using. The answer to this question is always Tommy. However free daily signups on Tommy generally fill in 5-10 seconds. So your best bet if you want a Tommy account is to make a donation of $1.00 USD or more to get an invite. Ricky is next best, and Johnny is out worst, slowest, and lowest uptime server. The only reason I can think of where you wouldn't pick Tommy is if you wanted to use Django or Flask with python 2.7 instead of python 3.6. There are very few people which that applies to though.

Create the log file manually, and then make sure the file is writable by other. 777 is a little bit of overkill, but it'll get the job done. If you want the application to be able to create the file itself you'll need to set the permissions on the directory the log is going to be written in to 777 or so. Obviously you can't change the permissions on /home/cridus10/, but you could create a directory like /home/cridus10/javalogs/ and give tomcat the permissions to write to that directory.