Krydos

I should be able to eventually enable "Options -Indexes" on Plesk. My main focus right now is getting new account creation implemented because there are hundreds of donors waiting to create a new account. Once those other top priority issues are fixed I can spend some time working on .htaccess. This issue is very low priority right now because it has such a simple workaround of being able to place an index.html file.

I found this on StackOverflow regarding that error: Source: https://stackoverflow.com/a/48468294/2336864 It sounds like maybe it's a client issue maybe? How long does your PHP script take to finish?

Ownership has been assigned to daskunk_php2.

You can only issue SSL if you change the A record. The whole point of the hosts file is to test your site before you transfer the A record over. If you don't want to test your site first you can just skip the hosts file entirely and edit the A record.

The donation has been linked to the murilo account now.

Have you tried this? https://docs.moodle.org/400/en/Installing_Moodle

That donation is already being credited to a Johnny account named ffvii. https://www.heliohost.org/eta/?u=ffvii Did you have two accounts?

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.