Krydos

You picked the Johnny server, which is the experimental server. What experimental means is it isn't suitable for production websites or production scripts. High load is common on Johnny, and is most likely causing your script to timeout. When you're done experimenting and testing you script you could consider moving to a production server like Tommy, or purchasing a VPS to host your script.

# ls -la /home/djboutit/public_html/|grep htaccess -rwxr-----. 1 djboutit djboutit 2750 Sep 11 13:25 htaccess -rw-r--r--. 1 djboutit djboutit 0 Sep 11 12:54 .htaccess -rw-r--r--. 1 djboutit djboutit 1730 Aug 7 00:00 htaccess-nginx.txt You have an empty file named .htaccess, and you have an incorrectly named file htaccess. You can't rename htaccess to .htaccess because .htaccess already exists. Please delete .htaccess before trying to rename htaccess, or just copy/paste the contents of htaccess into .htaccess.

You can donate as much or as little as you want, but in order to get double storage space you only need to donate another $1 USD because you donated $5 already.

That domain isn't hosted with us. You'll need to change your nameservers on that domain to ns1.heliohost.org and ns2.heliohost.org if you want to host it here. You can check your current nameservers with this link https://dnschecker.org/#NS/phabricademoda.com.br

Moving to Tommy is a minimum donation of $1. Getting storage increased from 1000 MB to 2000 MB is a minimum donation of $5. To get both is a minimum donation of $6.

You get a 404 not found error, because that file 403.html doesn't exist: # ls /home/djboutit/public_html/403.html ls: cannot access /home/djboutit/public_html/403.html: No such file or directory # cat /home/djboutit/public_html/.htaccess # Your .htaccess file doesn't have anything in it.

Alright, it looks like you're all good to go. One thing I noticed is /usr/sbin/ isn't on the path. So when you said fsck isn't installed, it actually is at /usr/sbin/fsck, but running the command fsck can't find it. The command /usr/sbin/reboot isn't on the path either, so issuing the command reboot won't work either. Something to look in to, or keep in mind for the future when commands don't work as expected. I was able to log in and fsck your hard drive. It looks like it fixed all the errors. Then I was able to cleanly reboot your VPS. The reboot took about 30 minutes though because one of your processes really didn't want to die, but I just waited it out and eventually it shut down. Not sure if all reboots will take that long, or that process was just having a bad day. I installed open-vm-tools package so if we need to shutdown or reboot your VPS in the future for maintenance this won't happen again. That doesn't happen very often though.

Thanks for the donation. You're on Tommy now. Your login information is the same. You can log in exactly the same as before with your username or email address at https://www.heliohost.org/login/ or you can login directly with your username only at https://tommy.heliohost.org:2083/

You can check Johnny's load with this image:

Unarchived.

Unblocked.

Unarchived.

Your username is sla25m9. Unarchived.

I think I found the reason that Ricky has been doing this occasionally. It looks like the malfunction happened on August 15th, and has been affecting apache reboots occasionally since then. Thanks for reporting it. Hopefully it's fixed now.

I tried logging in with the default password that I sent you, but it said it was invalid. Did you change the password? If so I'll need the new password to do anything. Obviously don't post it on this forum, but you can email it to me if you want. The other option is I can just yank the power cord out of the wall and then power it back on. That's unlikely to do anything other than maybe cause more filesystem corruption. I think this was actually all my fault in the first place now that I think about it. I was kind of in a rush to get the VPS done and I forgot to install vmware tools. That package allows my to cleanly shutdown or reboot a VPS through my admin control panel. Without vmware tools when I needed to power your VPS off for the maintenance I just had to yank the power on it, which is probably what caused the corruption in the first place. Sorry about that.

Remote access enabled.

Remote access enabled.

It's possible to get an invalid login message even if you have the right username and password if the server that your account is on is down or has high load. Johnny, the server that you picked, has high load fairly frequently so don't panic if it says invalid login. Check the server load, and if it's high you can just try again later when the load has dropped.

Your account has already been renewed, and your domain appears to be working. If you can't login try resetting your password. Let us know if you're still having any issues, but I'm marking it solved for now.

Sure, what is your transaction ID?

Remote access enabled.

Ricky was scheduled to be upgraded and rebuilt in March or so of this year, but it got delayed due to the pandemic. Once it's safe to travel we'll get someone to the datacenter in California for some long overdue maintenance, and then upgrading Ricky is the top priority after that. If you need a newer cpanel before then you'll have to switch to Tommy or Johnny which are both running cpanel 84. Is there any feature in particular on the new cpanel that you need?

You'll need to run that command on your development system and then upload the results to the server. If that doesn't work or you still need shell access you will have to get a vps https://www.heliohost.org/vps/ where you will have full root shell access. SSH isn't available on our free shared hosting accounts.

Do you get an error message?