Krydos

I have absolutely no idea. I've never installed Plesk before. I'm going to get it done as quick as I can though. That's literally the only HelioHost related thing I'm going to be doing for quite a while. If you want to go month to month it's only $4. Hopefully I can get Tommy rebuilt in less than a month. Email is definitely the hardest part of setting up a VPS without a control panel. I believe @Unknown025 did it on his own personal VPS without a control panel though. He might be a good person to ask how he did it.

On a VPS you get the entire server to yourself. By default it's just a bare operating system with SSH command line access, but you can install any web based control panel you want except for cPanel. If you install cPanel and pay those bastards a single cent I will delete your VPS myself. One popular configuration is Ubuntu 20 operating system and Hestia free control panel. You can of course do everything from the command line too without a web based control panel. In that case you would just install a web server, such as Apache or Nginx, and then you would need to install Postgresql and import your databases in, and you would need to install a php version as well. Control panels can make all that easier to manage by installing it all for you. Feel free to do some research on control panels before you submit your vps request. Some control panels only work on certain operating systems so you would need to select the custom option, and choose your os. Ubuntu 20 with Hestia does support Apache, Postgresql, and PHP which you use now.

I've actually been looking at Plesk for years ever since we set up Lily, but obviously the control panel is the foundation of an entire web hosting company so switching is a massive undertaking. There are very few control panels that run on Linux and Windows. Some run on just Windows, and most run on just Linux, but not both. Plesk will allow us to have both Linux servers and a Windows server and it will tie everything together. I would love to go with free and open source, but as far as I know only a few open source projects have experimental support for Windows hosting so far. As soon as I contacted Plesk asking them if they could help us, they literally dropped everything they were doing to get us a contract to sign before I changed my mind and looked elsewhere. Plesk, unlike cPanel, realizes that a verified and experienced non-profit with the purpose of providing free hosting is a gold mine for public relations. It's actually part of the contract that I signed that we have to let them put our logo and story on their website. This will make them look really good, and they know it. Plus as a free host we attract a lot of people who are new to hosting, and have zero experience with any control panel. Over the years we have gotten literally hundreds of thousands of people hooked on cPanel. When they move on to paid hosting they make sure that cPanel is available before they signup because that is what they know and love from using it here. Now we can get all those people started on Plesk instead. 100% without a doubt cPanel thought that we couldn't survive without them, and we would just give up and hand over the $1442 per month to keep their licenses. Absolute pure greed. If the reason was anything other than money they wouldn't have just said "you can buy full licenses".

Sorry about that. The VPS signup page is really new, and only 2 people have used it so far. I added NO_SHIPPING to the code which should fix that issue. Let me know if you're still having issues. Thanks for letting me know about it. Thanks for testing our Facebook donations. No one has ever donated via Facebook before so I'm not sure how the fees will compare to Paypal. However, for VPS it would be best to use the actual VPS page because it sets up a subscription that autobills on it's own. With a Facebook donation it doesn't automatically update the expiration date in the database, and I'll have to manually track it.

It's not a typo. I actually changed it to moneybroz, but I thought it would be funny to say I changed it to moneygalz. Apparently not.

Unarchived.

This map might be interesting for you https://www.gp-digital.org/world-map-of-encryption/ Some countries you can get fined or go to jail for using encryption.

I don't know where you're getting this OpenDNS/Cisco stuff from. Neither of them have anything to do with your ssl certificate, nor did they have anything to do with your old Let's Encrypt certificate either. This is the certificate that the rest of the world sees https://www.sslshopper.com/ssl-checker.html#hostname=daskunk.heliohost.org

Alright, you've been switched back to the Comodo certificate.

Your domain had a Comodo certificate just like mine when you originally started this topic. Since you were having an issue with it I switched you to Let's Encrypt to see if it helped. Do you want to switch back to what you had before?

Hmmm? What was it supposed to be? ?

Your main domain has been changed to moneygalz.heliohost.us

Try changing this line subprocess.Popen("/home/ar7/bot.py") to this subprocess.Popen("/home/ar7/bot.py", shell=True)

Yes, after the Ricky rebuild a lot of people switched to Tommy and he ended up getting pretty overloaded. As you can see here https://www.helionet.org/index/topic/43675-no-free-tommy-signups/ free signups have been closed on Tommy for over a month to help reduce the load. It's slowly getting better. When we release the new server hopefully in a few months a lot of people from Tommy will move to the new server and it will help Tommy's stability too.

Oh, I thought he was talking about actual subdomains, not the special proxy subdomains.

Put this in the .htaccess file in the webroot of each domain and subdomain to force https: RewriteEngine On RewriteCond %{HTTPS} !=on RewriteCond %{REQUEST_URI} !^/.well-known/ [NC] RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] Are you trying to remove www from the beginning of your domain too?

The ip you posted from is not blocked. If you provide some other ips that you think are blocked I could check them too. Is there any error when you try to FTP? Are you using FTPS, FTP, or SFTP? We recommend SFTP. FTP is insecure, and FTPS rarely works right. Does this help? https://unix.stackexchange.com/a/164093 It seems like the topmost directories lose their timestamp, but all files and subdirectories should keep them.

Are you only using firefox? Does the same error come up with other browsers? I viewed your site with chrome, safari, and edge and it works on all of those. Maybe it's something specific to firefox? I don't have firefox installed so I can't test that.

There you go https://krydos.heliohost.org/cgi-bin/modules37.py

WHM allows you to edit and delete all the accounts on the server, so no you don't have access to that. We use Apache not Nginx, but you can easily do redirects using modrewrite in your .htaccess file.

I deleted your Comodo certificate and generated a new autossl certificate using Let's Encrypt instead. Does that one work any better for you?

We don't actually offer heliohost.org subdomains anymore. Since you created your account prior to us getting the heliohost.us domain you're allowed to keep your domain, but no one can have new ones. As far as setting up a separate domain probably the easiest would be to register a domain for free at freenom and add it as an addon domain to your account. Addon domains are completely separate from your main domain. If you think it's somehow related to heliohost.org subdomain you can try going to https://krydos.heliohost.org/ It uses the same autossl certificate on the same server as you.

Python 2.7, or Python 3.7?

Your ssl certificate is valid, and it appears as if autossl is working fine. https://www.sslshopper.com/ssl-checker.html#hostname=daskunk.heliohost.org The CA error means that it is the "cPanel, Inc. Certification Authority" or the "COMODO RSA Certification Authority" chain that is the problem. Neither of these CA's have revoked their certificate, and both are valid until 2025+. The certificate that domain is using was issued on June 7th, so it's strange that it start happening on July 4th. You went almost a month using that same certificate before anyone noticed any issues with it. Anyways, here is an article for understanding that error and some ideas of how to fix it https://geekermag.com/error-code-dlg_flags_invalid_ca/ One that is really simple that stands out to me is simply clearing your browser cache.

Your main domain has been changed to rickalmeida.online. It looks like your software is still trying to redirect to the old domain though so make sure you edit the config file and update the domain there too.