Krydos

Your invitation email was originally sent on May 8th. I resent it just now. Let us know if you still didn't get the link.

The cPanel cptrash domains have been deleted.

There you go https://murilo.eu.org/ and https://nnidlt.murilo.eu.org/

Do you want your main domain changed, or do you want to add murilo.eu.org and have both domains?

Ownership of the database luanreis_afiliate_data has been reassigned to the user luanreis_luan.

I've been using Visual Studio Code a lot lately, and it does Linux line endings well too.

Create an .htaccess file with the contents Options +ExecCGI AddHandler cgi-script .py

All of the donors are already in the ETA database so your position is unlikely to change much at this point.

Someone probably donated and moved ahead of you.

First of all the working link has "nnidlt" and the invalid link has "niidlt" so that's why it's giving a 404 error. The problem is this line http_response_code(400); I commented that out and now it gives the expected JSON response. https://murilo.heliohost.us/nnidlt/api.php?env=production&user_id= It seems like Plesk is trying to give some custom error page for 400 errors for some reason. Not sure why. Does that script need to return a 400 error or is 200 response with the correct json error enough?

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/"