masthst

When you put it like that, it makes a lot of sense. That does add some urgency to the matter. Thank you for explaining that, I've forked over a few bucks.

I think this is an important point you raise, which potentially also influences how many accounts go inactive each month. I don't know who your target audience is. Probably not me. I'm severely underusing my instance due to continuously shifting priorities and lack of time. But when I'm working on it, it's in bursts. If a burst (of time) gets frustrated because I need something relatively simple done that I have no access to, it's dropped for that time and priority for the project goes down a few spots. Raising a ticket on a forum for something technical nobody but an admin can help with, can be a threshold for some people. Considering what I paid for it I'm definitely not complaining, but a new server does not fix any of that. As for the list of items you potentially 'should', we can't see which of those are going to be the most work. If any of those can be implemented without too much work for yourself and the rest of the team, it would be a quick win. If a couple of quick wins can significantly shorten the list, that would be a big win.

That worked like a charm, thanks!

I've received the invite and have recreated the account. I'm currently at the "We are still setting up your account" stage, so I'll check back in the morning (it's close to midnight here).

Did you move it? That site doesn't connect for me.

Something has gone wrong with the ownership settings. I don't know what, I don't know why but a reset or re-install usually fixes things for me offline in such cases. I have offline copies, not that there was anything of value running yet anyway... Please wipe it clean so I can give it a last shot. Account: masthst

I don't know about your webmail and control panel, but your site (infantex.com.mx) seems back up. Just an expired security certificate, you may have to update that.

While I was first getting Python set-up, I followed the krydos.gitbook.io documentation a bit too literally. Very easy to follow, except there's a minor bug in it: Python 3.7 is specified. This is too specific, since Python 3.7 is not installed by default (at least not on Tommy). The provided example will return a 500 Internal Server Error because it won't resolve properly. Consider replacing 3.7 by 3 in the documentation. The Modules section should probably be updated to mention 3.10 instead of 3.7. Debug: #!/usr/bin/python3 import sys print("Content-Type: text/html\n\n" f"Heliohost rules!<br>\n" f"Running Python {sys.version}" ) Naturally, using #!/usr/bin/python3.10 works as well. But that would require updating the code/documentation again when 3.11 becomes the default. If Python 2.x is no longer supported, it may be time to retire this from the documentation as well.