Krydos

These two lines have to reference the same file name. In the top line you say the file is named api.wsgi, and in the second line you say it's flask.wsgi. Which one is it actually? The logic behind these two lines is the first one says "Is the request going through api.wsgi? If so stop processing rules and leave the request as is." The second line basically says, "If the request isn't going to flask.wsgi already redirect the request and process it through the .wsgi file." Since the two lines don't reference the same file name it just endlessly loops.

/usr/local/bin/php should work and on Johnny it's php 7.2 Here's the errors your script is showing: PHP Warning: fopen(../../cgi-bin/div_radar_cgi/curl_log_updateStocks.txt): failed to open stream: No such file or directory in /home/ckuo/public_html/div_radar/tools/updateStocks.php on line 15 PHP Warning: curl_setopt(): supplied argument is not a valid File-Handle resource in /home/ckuo/public_html/div_radar/tools/updateStocks.php on line 17 d1 = 2020/02/11 d7 = 2020/02/18 PHP Warning: fclose() expects parameter 1 to be resource, bool given in /home/ckuo/public_html/div_radar/tools/updateStocks.php on line 25

Unarchived.

Unarchived. Your username is skab33 now.

Your backup can be downloaded from https://www.heliohost.org/backup/

I added that email address to the blacklist so even if they send another email it won't start a loop again.

Remote access enabled.

Probably. Every two hours mysql closes all the connections so that helps clear out the people who might be abusing the server. I have seen error logs showing the too many connections error, but I've never been at a computer when it was happening. For now I doubled the number of total available connections so that should help a little, but if someone is determined to try to crash the server they will still be able to since we don't have a per user limit. If you see this while it's happening run the command ./mysql_connections and it'll print them all out for you. I can set up automated logging if neither of us are able to run that command while the server is maxed out on connections.

When I originally created my first HelioHost account I had to stay up until 2am three nights in a row to get an account because I was too slow the first two days. Back then there was no option to donate to get an account on the best server so you're lucky that that exists.

Remote access enabled.

Remote access enabled.

Merged threads about the same thing.

Unarchived.

Unarchived.

I already deleted his domain, and re-added it once. It didn't help last time. Back to the original point of this thread, AutoSSL isn't going to work as long as your nameservers don't show up for 50% of the world, but you still may be able to manually install an ssl certificate using our instructions here https://wiki.helionet.org/Installing_a_Let%27s_Encrypt_SSL_Certificate

Removed.

I summed, created, signed, and sent a receipt for Roy's 2019 donations.

I would consider switching registrar's then. This is what namecheap's coverage looks like https://dnschecker.org/#NS/krydos.com

Be sure you delete your extra accounts since this one is unarchived now. You're only allowed to have one active account. If you fail to delete the extra accounts we will be forced to suspend them all.

Enabled. Do you still need the port open to 31.186.250.8?

Done.

Unarchiving...

All of those modules are already installed (or default and don't show up on the page.)

Thank you very much for the donation. Your storage space has been doubled.

Autossl is working on vidon.phink.heliohost.org now, but there is something wrong with the vidon.net domain. Take a look at https://dnschecker.org/#NS/vidon.net The nameservers are only showing up right at like 50% of the checks. Once that gets to 100% then autossl should work on that domain as well. Maybe check with your registrar and ask why the nameservers aren't showing up for everyone?