Krydos

60 seconds was the same timeout that cPanel had. The reason the limit is there is to help prevent load from getting too high if people run insane php scripts that run forever. This value can be raised for just your one domain if you want, but it might cause your load to get too high which may cause your account to be suspended. Let us know the domain if you'd like to proceed. Eventually you'll have graphs and warning emails to alert you that your load is high. For now I've just been pinging people on Discord or emailing them manually if there's an issue. If they don't respond and don't fix it then we suspend them. The PHP function proc_open is a security vulnerability on shared hosting. It has never been enabled on cPanel either, and it won't ever be enabled on any of our shared hosting servers. If you need this function you have to host it on a VPS.

You may have noticed some downtime off and on over the last few weeks. Someone on Tommy has been getting targeted by some intermittent DDoS attacks. Due to the nature of the attack it's not possible to tell which of the about 2000 websites on Tommy is being attacked. These attacks have caused short downtimes for Ricky, all of our VPS, our main website, and forum as well, until the DDoS protection kicks in and takes the targeted IP offline. We've been moving accounts around between different IP addresses to help narrow down who is being targeted, and mitigate the downtime for domains that are being attacked. If you use HelioHost's nameservers, ns1.heliohost.org and ns2.heliohost.org, your A record will be automatically updated to follow the move, but if you use Cloudflare or some other external DNS we have no way of updating it for you so your website will show the Plesk default page until you update the IP manually or your account gets moved back to the original IP that it was on. If your website is currently showing the Plesk default page please let us know so we can get it fixed as soon as possible. Our ISP has been working with us to help keep everything online, and we have been moved to a new upgraded network hardware that should help reduce congestion during an attack. We've also purchased a bunch of new ipv4 that we can use to split users on Tommy into groups to help narrow down which group is being attacked. This should all result in better uptime for everyone. If you think you are being targeted, or may be targeted in the future please contact us so we can work with you to help keep your website online, and eliminate the number of innocent accounts that are experiencing downtime because of this. Let us know if you have any questions or comments.

That's pretty funny. You can test if your outbound port 1342 is open by going to this website http://portquiz.net:1342/ If you see text then it's working. If it times out in your browser it means your computer's firewall, or your router, or your ISP, or something is blocking that port.

Remote access enabled. Note to self: We might need to set a limit to the number of remote access per account until we implement a way for users to enable remote access themselves. ?

That is a known issue if you change your main domain. I intend to fix it eventually. Does it work now?

This is what I see Maybe try clearing your browser cache?

Remote access enabled. I know for cPanel PostgreSQL usernames had to be different from database names. So when I saw a database named tomaszrozko97_db I just assumed it wasn't possible to have a user with that same name. Maybe Plesk doesn't have that limitation anymore.

Yes, just let us know the PostgreSQL database and the database username and we can enable remote access. Remote access to MySQL databases can be enabled yourself through Plesk, but Plesk doesn't provide any way for you to do that yourself for PostgreSQL databases so we have to do it for you on the command line.

The old cPanel version of Tommy is still online and files can be changed via SFTP with the host 65.19.143.6 and port 1342. The new Plesk version of Tommy can also be accessed via SFTP with the host 65.19.141.77 and port 1373.

Thanks for letting us know. It looks like it locked up, possibly due to the DDoS since it had been running for like a year without locking up prior to that.

Your domain was pointed at the wrong ip address. It should start working in the next hour or so.

For now just put an index.html file on any directories you don't want a file listing to show up for. Eventually when I'm not busy with a million other things I'll see about getting options to work in .htaccess.

There is no database user with this username. There is a second database with that name though. Before I can enable remote access you need to create a database user.

Hmmm, that's really weird. I tested this same thing on my account and it doesn't show a directory listing. It must be some strangeness that copied over from cPanel. I'm seeing a 404 error when it redirects to admin.

Gmail has been delivering our emails fine for a month or so now so it's safe to use it again.

Done. It can take up to 2 hours for your domains to start working right after a change like this.

Directory listings are disabled by default on Plesk. If I enabled Options permissions in .htaccess it would be for people who want to enable directory index.

Here is the error we're getting when the forum tries to send an email to Zoho: 2022-12-06 00:20:49 1p2LhX-0003r3-IX ** <removed>@fasouza.eu.org R=dkim_lookuphost T=dkim_remote_smtp H=mx.zoho.com [136.143.191.44] X=TLS1.2:ECDHE-RSA-AES256-SHA:256 CV=yes: SMTP error from remote mail server after RCPT TO:<<removed>@fasouza.eu.org>: 541 5.7.1 Mail rejected due to antispam policy We're not listed in any of these 82 blacklists https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a65.19.141.66&run=toolpage so Zoho must have their own blacklist or something. Sometimes these error messages have a link to their website where you can request your IP to be delisted, but Zoho doesn't provide that apparently. You'd have to contact Zoho support and ask them why the email isn't being delivered. Perhaps you could change your Plesk email to match your forum email instead?

Done. It isn't letting me make a subdomain of an alias domain. I can delete fasouza.eu.org and readd it as a normal domain and then I should be able to recreate the blog subdomain. Make sure you have a backup of all of your files before I start deleting and readding domains. We had one person's files get deleted when we did this before. Just edit the .htaccess file and comment out any lines that start with "Options". I plan on enabling this eventually, but most of the time the Options lines aren't needed anyways.

Your account has been wiped, and you have been sent an invite via email to recreate your account. You can change your username, and domain during account creation if you wish. Let us know if you run into any issues.

You subscription has been canceled, and you won't be charged again. Thank you for using our VPS service.

Yep, another DDoS... I just booked my flight to Russia. I'm going to start punching faces until the DDoS stops.

Another DDoS is happening right now.

There is another DDoS happening right now so that would explain the emails.

There was a DDoS so we skipped a day because if we had sent out invites they probably wouldn't have worked while the server was down anyways.