Krydos

There you go https://www.sslshopper.com/ssl-checker.html#hostname=pusuluri.heliohost.org

Thanks for the donation. There you go https://www.heliohost.org/eta/?u=kr4cher

We've already reached the rate limit for new Let's Encrypt certificates for domains being transferred to Plesk. This means if your account is transferred to Plesk right now it will not automatically get an SSL certificate. We've contacted Let's Encrypt to request a rate limit increase, but it will likely be several weeks before we hear back from them. Hopefully they grant the rate limit increase, but it's a possibility they will deny the request and we'll be stuck with this ridiculously low limit forever. You can of course install a free 90 day ZeroSSL certificate or a free 90 day Comodo certificate or any of the other free options out there, but they will not be installed automatically for you. This rate limit generally doesn't affect renewals, so once your domain is secured using Let's Encrypt it will continue to be renewed without any work on your part. We figured this would be an issue, but hopefully Let's Encrypt will grant the rate limit increase this time unlike last time we tried to use their service.

Yeah, we'll make a news post. You can follow us on Facebook, Twitter, Discord, RSS news feed, our homepage news feed, or just check the forum news section occasionally.

No, you don't have to login at all for the first 30 days, but most people are eager to try out the new control panel so they login as soon as they are transferred.

Sorry about the email not getting posted. We use google for our mail provider, and they flagged your email as spam. I try to go through the spam emails every week or so and look for legit emails, but I don't check every single day. The reason there is no position number for you is because you were on Johnny. I don't know if you read any of the recent news Your account and a lot of other accounts were hacked and phishing sites were uploaded to them. Our standard policy for dealing with hacked accounts is we permanently suspend the affected account with no backup, and give a new empty account to the user. The reason we don't provide a full backup is because a lot of the time with phishing sites the passwords and credit card numbers and whatnot that are stolen are saved to files on the account, so obviously we can't send you stolen credit card numbers or whatever junk is on the account now. If there are a few files you don't have backed up we can inspect the files manually for tampering and back them up for you, but we're not going to manually read through 10,000 files. Since we aren't currently able to create new accounts you need to wait for new account creation to be implemented before we'll be able to get your website back online. We hope to have this done in the next few days. As soon as new account creation is implemented your position number and estimated date will reappear on the ETA page. When it's your turn to recreate your account you will receive an invitation email with a link that will allow you to create a new account on Plesk. Sorry for the confusion, and thanks for the donation. Let us know if you have any other questions.

I just got a report that cgi files that had 755 permissions on cPanel got transferred to have 644 permissions. Obviously you can just edit the permissions after you're transferred to fix it, but it's something I may try to fix in the transfer script.

Those subdomains have been created. Not sure why they didn't transfer. The DNS was actually set correctly already. Let us know if you find anything else that isn't working right.

Wolstech sort of answered this already. Wildcard certificates require DNS validation. Since Plesk can't edit DNS zones yet it won't work. If you use http validation for a regular certificate it will work because Plesk has access to write files to your domain. I already answered this Yes, all domains get transferred now. Alright, those should be set. Let me know if it's still not working.

We aren't deleting the cPanel accounts so if you can't get something working on Plesk it only takes 5 seconds to edit the A records back to the old account. We have had some issues with .htaccess files that worked under cPanel not working anymore under Plesk. I'm still investigating why that might be. So far the common .htaccess commands like rewrite seem to be working fine, but some like enabling indexes throw a 500 error. The solution so far is just to comment out the certain lines, and no one's website functionality seems to have been affected so far. SFTP works on both cPanel and Plesk so where ever your account is you can manage the files through SFTP. Plesk has the advantage of having a browser based file manager as well. We will start monitoring inactivity again once you're on Plesk so we can archive unused accounts to keep space available for active users. cPanel has no inactivity monitoring, but we will take the whole server offline eventually once everyone has had the opportunity to move to Plesk so you can't stay on there forever.

There you go root@tommy2 [/home/krydos]# dig +short A @ns1.heliohost.org keibee-it.com 65.19.141.77 root@tommy2 [/home/krydos]# dig +short A @ns2.heliohost.org keibee-it.com 65.19.141.77 People who were transferred early on, only their main domain would get moved to Plesk. That has been fixed now and all domains get moved to Plesk when your account is transferred. Now that your .com is hosted on Plesk you should be able to install a Let's Encrypt certificate for it as long as it's not a wildcard certificate. Let us know if you have any problems with anything else.

Plesk uses both Nginx and Apache at the same time. Nginx is a reverse proxy sitting in front of Apache and handles all of the static content and html and caching. Apache handles all the heavy lifting in the background. It uses a bit more memory to have both enabled like this but it should give much better performance. We'll see how it scales up to handle hundreds of accounts though.

Thanks for the donation. There you go https://www.heliohost.org/eta/?u=tdm

Plesk has these PHP versions: https://php52.krydos.heliohost.org/ https://php53.krydos.heliohost.org/ https://php54.krydos.heliohost.org/ https://php55.krydos.heliohost.org/ https://php56.krydos.heliohost.org/ https://php70.krydos.heliohost.org/ https://php71.krydos.heliohost.org/ https://php72.krydos.heliohost.org/ https://php73.krydos.heliohost.org/ https://php74.krydos.heliohost.org/ https://php80.krydos.heliohost.org/ https://php81.krydos.heliohost.org/ Plesk has CGI: https://krydos.heliohost.org/python27.py https://krydos.heliohost.org/ruby.rb https://krydos.heliohost.org/perl.cgi Plesk has PostgreSQL 13.6 and your databases and users should be transferred over. If they don't let us know and we can take a look.

Yeah, we've had a few problems with .htaccess like this. I'm still looking into why exactly. I've tested FTP, FTPS, and SFTP and they all work for me. One difference that might be messing you up is SFTP is on port 1373 now. On the old Tommy it was port 1342. The reason we changed it was because the SFTP port was a constant cause of confusion for people because all three servers had a different port Tommy=1342, Ricky=1312, and Johnny=1373. So people would search on the forum and find the port of a server that they weren't on and it would obviously not work. To simplify things going forward with adding more and more servers we're just going to keep SFTP on port 1373 for all the servers. Let us know if you find anything else that doesn't seem to be working right.

Closing due to inactivity.

I checked all of your domains, and subdomains. The ones that were showing 500 errors were because of .htaccess files. If you go to Websites & Domains > domain > Logs you can see the error log and see why the 500 error is occurring.

I deleted all the disabled domains, and changed the IP address of the remaining domains. It looks like the transfer script only changes the IP of the main domain, and not any addon or alias domains. Just another thing to fix. This is why we're only transferring a few accounts per day until we get all the issues worked out of the transfer script.

Sent.

Thanks for the feedback.

It looks like your main domain got transferred, but not your dopplerdave.info domain. I updated the DNS for you. root@tommy2 [/home/krydos]# dig +short A @ns1.heliohost.org dopplerdave.info 65.19.141.77 root@tommy2 [/home/krydos]# dig +short A @ns2.heliohost.org dopplerdave.info 65.19.141.77 Let us know if you need help with anything else.

If there is a cryptocurrency that you want to use that isn't listed it might be possible to add it to the list. Just let us know.

Here is the log file entry for your email. It was definitely sent. 2022-05-06 21:18:22 1nnBtd-0007mI-Te <= root@cody.heliohost.org U=root P=local S=11261 T="Are you ready for Plesk?" for skullythepirate@suddenlink.net 2022-05-06 21:18:22 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1nnBtd-0007mI-Te Since then it's just been trying to send the email over and over, but suddenlink.net is just timing out and errors. Is there another email address we can try? Our mail server isn't blacklisted by any of these 82 spam email lists. https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a65.19.143.5&run=toolpage

There you go https://www.sslshopper.com/ssl-checker.html#hostname=appstursoft.com

As we said earlier, Johnny was shutdown due to a large number of accounts getting hacked. Therefore we will be giving all existing Johnny users new accounts on Plesk rather than transferring the compromised accounts. Last night we went through the ETA database and changed all of the existing Johnny accounts to be new accounts. This means that there won't be a position listed currently since we haven't implemented new account creation yet. Once new account creation is implemented, which should be soon, we will readd the Johnny accounts and donors without existing accounts back into the ETA database. Unfortunately, it looks like changing the Johnny accounts to new accounts seems to have messed up the donation totals for some people. If your donation amount was affected please let us know so we can get it fixed. Thanks.