Krydos

When you need support please post in the customer support subforum. When you want to comment on a news post please comment on the news post. If you post support requests on news posts they're liable to get lost, closed, ignored, etc. If you need a module installed let us know what the name of the module is.

The best way to do https on flask or go scripts is to proxy the connection through Apache or Nginx and have the webserver handle the SSL certificate.

Your invite was originally sent on May 10th. Resent.

When an account is transferred to Plesk the worthless transfer script sets all of the PHP versions to a disabled executable. Since the executable is disabled it will give a 503 error. My upgraded transfer script changed the PHP version to one that will actually work. I'm guessing that Apache and Nginx hadn't been restarted so it showed a 503 error for up to 2 hours after you were transferred and then it fixed itself. I've upgraded the transfer script to restart Apache and Nginx so it won't do a 503 error for up to 2 hours anymore.

On cPanel you can install Perl modules yourself and then you put this code in your script to load the modules. Obviously since you're not on cPanel anymore it's not going to work.

This is just trash from cPanel that got transferred over. Since you were transferred over early on you had an older version of the transfer script. On the newer versions of the transfer script it deletes that junk automatically now. I deleted it from Plesk so it won't bother you again.

I didn't turn it off. At least not on purpose. Feel free to turn it back on. I have a cover photo on my profile.

For a VPS it's probably easier to just expose the flask port directly to the internet through the firewall rather than proxying it through apache or nginx. If you want your flask app to have https then it's best to proxy it though. I wouldn't use wsgi at all on a VPS honestly. The main purpose of wsgi is to reduce the cpu and memory usage of your app while it's not running. On a VPS you have all the memory and cpu you want so you may as well leave the flask app running 24/7. So the first step is to open your port in the firewall. "sudo ufw allow 20000" Then start your flask on the command prompt with something like "/usr/bin/python3.8 server.py" Then use your browser to go to the flask app "http://vps76.heliohost.us:20000/"

The explanation is in the latest news post. https://www.helionet.org/index/topic/53328-first-phase-of-plesk-migration/ Everyone will be moved eventually. We're moving the donors first is all. If you're a donor that has given between 2020-07-14 through today and your ETA page doesn't list the right amount let us know so we can find the donation and get it linked.

It's ok. I found it after a few tries.

Your site is working for me. If you changed anything please share so we can all learn.

There's many different ways to configure things that will work, but what I recommend is: Use a hosts file to make your browser think that your domains are hosted on 65.19.141.77 (Plesk), and then make sure all your domains are working correctly on Plesk. With the hosts file only your computer will think the domain is on Plesk, and the rest of the world will continue getting your website from the VPS. Then when everything is working correctly on Plesk log in to Cloudflare and change the A record from 65.19.141.197 to 65.19.141.77. This will make everyone's computers go to Plesk when they go to your domain. I recommend continuing to use Cloudflare for now because the DNS connection in Plesk isn't fully working yet so if you switch to our nameservers an admin will have to make changes for you. If you continue to use Cloudflare you can make the changes yourself and save us some work. If you're using Cloudflare's DNS you can use their SSL too. For mail you'll want to make an MX record in Cloudflare pointed to 65.19.141.77 if you want the emails to go to Plesk. You'll need to copy/paste the DKIM that Plesk provides and the SPF value mentioning Plesk's IP into Cloudflare to make your email sending work though because you'll have terrible spam scores without them. Let us know if you need help with any of that.

The domain kaayoutfits.com has been added to your account. You can use our nameservers, ns1.heliohost.org and ns2.heliohost.org, or you can use any external DNS such as Cloudflare if you create an A record pointed to 65.19.141.77.

Can you see the data now? Another user had this same issue where the ownership wasn't set right on their PostgreSQL database.

Thank you for the donation. I have credited towards your af96 account. For future reference, and for anyone else who might read this post, screenshots are great, but I can't copy paste a transaction ID out of a screenshot and into PayPal. So I have to tab back and forth typing a few characters in at a time and still not find it because some of the Os are 0s and some of the 0s are Os and whatnot.

You did have an existing account, but it was on Johnny. So many accounts were hacked on Johnny that we just powered him off rather than waste our time trying to sort it all out. You can read these two news posts if you want. Our policy for hacked account is we give you a brand new empty account. You'll get your brand new fresh account as soon as we're able to.

Thank you for the donation. I found it and credited it to your stewguy account.

You can log in to Plesk and delete the mysql user and recreate them. Probably just changing the password will work too. Make sure to update your config files if you change the password so your software can continue being able to connect.

Yep, that's the plan. Here is your ETA page that you can watch https://www.heliohost.org/eta/?u=quataofr

If anyone who has an existing account donates as little as $1 right now you'll get an invite to move to Plesk within 24 hours. I just don't feel it's fair to move free accounts, or accounts that donated so long ago, before we allow a donor to have a new account who has given $360. The main issue is our servers can't hold an unlimited number of accounts at once. We're not sure how many accounts Plesk will be able to support with reasonable uptime so it would be a shame if we moved a bunch of free users over, and then donors end up on Johnny or something because there is no room for them anymore. Thank you for being so understanding.

No, it's not a joke. We added the donors without existing account back into the database like I said we were going to all along. Do you think it would be fair for us to move your account before we allow our donors who have given over $300 onto Plesk? Everyone will get moved eventually, we're just making sure we do it in the fairest way possible.

The transition to the Plesk control panel is going great, but there's a lot of work left to do. The first phase of the Plesk migration has been completed. All of our donors with active accounts have now been sent an invite to move to Plesk. If you've made a donation any time after 2020-07-14, and aren't on Johnny please let us know so we can get you moved over. As we've said before in previous news posts all of the Johnny users will be receiving new accounts so they don't count as existing accounts. The next phase of the migration is to send invites to all of our donors who don't already have existing accounts, and the Johnny users who were hacked. The new account people have been added back into the ETA page https://www.heliohost.org/eta/ so you can see your position number again. We will begin sending out invites soon once new account creation has finished being tested. If you have any questions let us know.

Once PostgreSQL is installed you can enable remote connections by editing the pg_hba.conf file and adding a line specifying the database name, username, and the IP that should have access. Here's a guide on how to do that https://www.bigbinary.com/blog/configure-postgresql-to-allow-remote-connection You can host your Flask server and your database on the same server without any issues. As far as backups go yes, we recommend taking frequent backups of your important files and storing them somewhere safe. We've never lost data on a VPS, but it doesn't hurt to make backups. You could even automate the backups using a cron job and SFTPing them off to another server. We don't currently have any backup plans for VPS, but that is something we've considered doing in the future. For now you're responsible for your own backups. Let us know if you have any other questions.

Thanks for the donation! There you go https://www.heliohost.org/eta/?u=gtom You're currently #150 in line to create a new account. New account creation hasn't been implemented yet, but as soon as we're able to create new accounts that page will show your position number and estimated invite date.

It was a different issue now. Since Plesk doesn't have access to DNS yet you can't issue wildcard SSL certificates. It's the same reason you can't add domains on your own right now. Eventually you will be able to add domains on your own and use wildcard certificates. For now I just issued a regular certificate and it worked fine.