wolstech

A VPN for family/friends to use would be fine, but I wouldn't recommend hosting a public offering like Tor (especially an exit node), because all it would take is someone to be connected through your VPS and engage in illegal activity while connected for us to get an abuse report. Abusive VPSes get turned off until you can correct the issue, or if the activity in question was intentional / user refuses to correct it, the VPS can get banned without a refund. As for other content, you can host basically anything on a VPS so long as it isn't illegal. Game servers are a common use for them, as are private VPNs as above. Things you are not allowed to host on our VPSes include things such as: scams, phishing, spambots, malware distribution or control servers, torrent seed boxes, crypto miners, porn (we prohibit adult content), infringing content like pirated movies, or stolen content such as from a data leak.

I've gotten that before. Gmail requires you have either SPF or DKIM set up. Your domain appears to have neither at the moment. Since you're using our NS, Krydos needs to fix this for you since you can't edit your DNS zones yourself.

The email goes to the address on the hosting account, so in this case it would have gone to a h...@...maps.com address.

It's easy to use, has been around forever, and has tons of integrations and extensions available for it...the same reasons it's widely used are also the reasons it should not be used. The code base is ancient, a lot of those extensions have backdoors or are abandoned and have unfixed security issues, and it's easy to use it to do nearly anything...including phish.

Wordpress gets attacked because it's so widely used. Spambots and even dedicated cybercrime groups exist that specialize in attacking WP. Spam comments are just an annoyance considering it's extremely common for a WP site to get hacked and replaced with phishing content. WP can't really be made secure in any sensible manner just due to how badly it's written. They find new security holes all the time. Keeping it updated and not using dubious extensions makes a big difference, but even then it's not uncommon to see it suddenly get hacked out of the blue. Security extensions can also help, but some of those are famous for bloating it to the point where it causes high load and has 30+ second load times.

Unfortunately Moodle 4.x is not available through Plesk's application installer yet. I just ran the update check on it, and the latest offering for Moodle is 3.10.10-156. These application installer tools sometimes take a few months to catch up when applications update, and I know back with Softaculous on cPanel, sometimes it never caught up at all. You'll need to either use 3.x through the installer or manually install 4.x from their website.

His WP install was reaching out to that CDN despite the fact he doesn't use it. May or may not be malicious, but I don't know of many legitimate Wordpress plugins that would use something like that. Google didn't find any prebuilt integration for WP for it either.

Yeah, it's a dubious blockchain CDN.

I'm curious to what Krydos thinks about that error, but considering WP loves to get infected, I wouldn't be surprised if it was. That said, since it seems to be basing that error solely on the fact it timed out, I'd be more likely to believe that server load caused the error.

Plesk on Lily is going to be a nightmare considering the custom stuff running on that server (insomuch that my stuff will likely need to go elsewhere in order for it to eventually get Plesk, there's way too many custom modifications and insecure settings on it to let it run wide open as a Plesk server...for example, I have 4 custom daemons and exec enabled in PHP...). I kind of use Lily as a VPS with the understanding that users needing ASP.NET can share it. We have very few ASP.NET users, I think we have like 4-5 active ones at the moment. It supports .NET 4.8, .NET Core, and even Classic ASP (I have one user running a classic site). If you want to try running your stuff there, let me know and I could create an account for you. There's no UI as Krydos said above, just FTP for files (and phpmyadmin for database access). You can configure a lot of IIS's settings using web.config files in your folders, but I'd need to set certain things up for you like server-wide changes (if they don't conflict with other users). You'll need to provide your own DNS since cPanel is gone (Cloudflare works fine with Lily). If you need email, you'd need to provide a mail server as well. Back in the cPanel days, I had Tommy configured to send Lily's mail, but I haven't figured out how to make that work with Plesk Tommy.

You're still in line: https://www.heliohost.org/eta/?u=microst0 At number 2072, you've likely still got a few months to wait. You're in the free account group, which is scheduled to go last behind all donors, including those getting new accounts. The line is currently not moving at all since the next person in line is a donor needing a new account, and new accounts aren't implemented yet. If you want to move quickly, you'll need to become a donor. Since all donors with an existing account went first, you'll be sent an email to let you move within 24-48 hours if you donate. If you're a donor already and your donation is not showing on that page, post the transaction ID and we can get that fixed so you can move. Please note that only donations made after July 14 2020 will count. If the donation is older than that, you'd need to re-donate.

Python on Linux requires unix line endings. Your line endings were in Windows/DOS format. I changed them to unix endings and it works now. If you're editing on Windows, my suggestion is to use an editor like Notepad++. You can author files using Unix endings using Edit->EOL Conversion->Unix in that editor.

Both of those scripts work for me. I see a hello world message from the first "ola mundo" from the second.

If we turn them off globally, people who want them won't be able to see them. As it stands, users who don't want the listings can just put an index.html in the folder to effectively turn them off.

Options -Indexes (and a few other directives) is not supported on Plesk. Just put a blank index.html file in the folders instead.

It's because you're a non-donor: https://www.heliohost.org/eta/?u=jio We're working on moving donors for the time being, including new account donors which haven't even started yet (hence the 0 per day moving, all donors with existing accounts were moved already). Free users aren't being moved yet. I believe Krydos has been moving new donors though (we had another free user like you donate, he moved within 24 hours). If you donate, please post the transaction info and I'll escalate this to see if we can get you moved. You can donate as little as $1, though more is appreciated if possible.

I'm not sure if that could be made to work or not. The domain and those two mailboxes is all I would need to put on the server, Krydos would need to add +65.19.141.70 to the SPF for your zone. I think from there you'd be able to send email from them by using localhost as the SMTP server. I'll see if I can set this up when I have a free moment...

You should be able to use whatever SMTP service you wish. If you can't, we can fix that Lily actually has a local mail server itself, but it's restricted to sending notifications for the server at the moment. Lily was meant to be used with the defunct cpanel mail servers so I never bothered to fully set up a mail server on Lily. If you want I can add your domain as an allowed sender on the local mail server, but I need to know what domain will be in the "From" field of your emails. Also, you (or Krydos if we host your DNS) need to edit your domain's SPF record and add Lily's IP as a server allowed to send mail for your domain.

This has been turned on with a max size of 2MB for the pictures. @sylvain See if you have a button for uploading a cover photo on your profile now

The ability to do this is turned off on our forum. I don't know why it's turned off, but my guess is either abuse or disk space... (Normally there's a button next to Edit Profile that says "Cover photo" that you use to do this...)

Try changing your domain's PHP version to something else (then change it back if you need to, it seems to be the act of changing it that fixes things). I had weird errors like this with my site when my account first transferred, and changing the PHP version fixed it. Another thing to try is to rename your .htaccess file. There are a few directives that cPanel supported but Plesk does not (Options -Indexes is one known one), so renaming the file to disable it will tell if this is the issue. If it is, you'd need to go through the file and determine which lines need to be commented out to make it work.

Yeah, the indexes option is one of the known causes of this. Krydos hopes to figure out why these don't work and restore them at some point, but right now getting account creation working is a higher priority. In the meantime, you can just put an empty index.html in the folders instead to suppress unwanted directory listings.

That's my mistake. I re-read the announcement (I posted at 6AM earlier before my coffee...), and it's specifically states only all of our donors were moved. You're still in line because you're a non-donor and we haven't moved all of our free users yet. We did add the new account users back to the ETA tool though, which pushed you back due to donors in that group. From here (https://www.helionet.org/index/topic/53328-first-phase-of-plesk-migration/#comment-219645 )

It's because the 187 ETA was based on different data. Krydos updated the ETAs last night to include people who are from Johnny or otherwise are getting are otherwise getting a new account instead of a transfer. Since those people are now included, and many of them are donors, they were added ahead of you. If you have an existing account that is both: NOT archived or suspended, AND is NOT on Johnny, you should have received a plesk transfer email already. You say you may have donated. If you can find the transaction ID, we can check the date and add it to your account if it's new enough to qualify.

The ETA tool doesn't show a user's position for new accounts because we aren't currently creating any new accounts. Once the account creation is implemented the positions will show up again.