wolstech

Unarchiving...

Yes we do Lily supports ASP.NET Core 3.1. Please keep in mind that Lily is experimental and has no real user interface beyond FTP and PhpMyAdmin, so I have to make changes for you if you need certain things done like registering applications. If you're interested, please let me know your hosting account name and I'll set up a second account on Lily for you.

Tommy has no limit at this time, but that's subject to change if someone abuses the mysql server.

The account rebal155 has been removed.

Which account are you trying to delete? I see two accounts, rebal15 (active on Ricky), and rebal155 (inactive on Johnny).

Tommy ran different software before the crash. Most notably, the default versions of PHP were different (it used to be 5.6 default, now it's one of the 7.x versions). PHP 5 and 7 are not backwards compatible with each other. Another thing to consider: Gmail will not deliver a message if you spoof the From header to make it appear as being sent to from itself. If you use Tommy to send an email to your Gmail account, be sure you set the From to something that's NOT a Google account. Have you tried writing a test PHP script that just mail()'s a test message to you? Try this script (edit the email address in the $to variable): <?php // the message $msg = "First line of text\nSecond line of text"; $to = "someone@example.com"; // use wordwrap() if lines are longer than 70 characters $msg = wordwrap($msg,70); // send email mail($to,"My subject",$msg,"From: noreply@tommy.heliohost.org"); ?> If this works, your software is just broken or incompatible with what we run now. I would start by changing the PHP version back to whatever you used before the crash (if you never set one before, try setting it to 5.6). You can do that in cPanel under MultiPHP Manager. If that doesn't help, you'll need to find new software for your contact form. iCloud and GMX are email providers like Google or Yahoo. Both are known for refusing our emails entirely without delivering them.

Johnny was down from load earlier again: http://heliohost.grd.net.pl/monitor/ Is it working now?

The folder assets was owned by a non-existent user 8355 and has been corrected. Try deleting the assets folder now. Also, your trash had the same issue (owned by non-existent user 8355). The permissions have been changed on the .trash folder and the contents have been discarded. Try using your trash can again and let me know if it still doesn't work. Also, I made you the owner of the backup file davidbb.tar.gz that Krydos left for you, so you'll be able to delete that now as well if you want the space back.

There's a limit of 4 concurrent connections at a time. You can try something like this in your connection string to limit them. Also, be sure to explicitly close your connections when finished with them. jdbc:mysql://localhost:3306/database?max-connections=4

When the account is removed, the domains will go with it automatically. If you get an error about dns records needing removed when adding them back, let us know and we can clean them up for you.

Unfortunately I can't check the reason since it's already been unblocked. If it happens again, let me know and I'll get the reason for you.

Unblocked.

Krydos should be able to point you to the files causing the issue. In the meantime, I've blocked your website with an .htaccess file and unsuspended you.

Cloudflare is well known for breaking a lot of things on our service. Please keep in mind the following: DNS Zone Editor - Doesn't work with CFDomains pointed to CF cannot be added to your account - You must set CF up after adding the domain.Subdomains - Requires manual DNS entries be made on CF's website for each domaincPanel on port 80 - Doesn't work with CFWebdisk - Doesn't work with CFMail client configuration - the hostname shown in cPanel will be incorrectFTP client configuration - the hostname shown in cPanel will be incorrectWe do not provide any technical support for CF users. You will be asked to remove CF before we assist if you ask for help. (We can't see what DNS settings users are using if they use CF, and in most cases, the act of removing CF itself ends up fixing the problem...). That said, it can and has been used successfully. In fact, we offer a button in cPanel to set it up. Most issues with DNS that we've seen with CF are fixed by deleting the site from CF, pointing your domain back to us, and letting CF copy the zone records again. Mail and FTP will work if you use the server hostname (e.g. tommy.heliohost.org) instead of your own domain in those clients, and most users don't use Webdisk or cPanel on port 80.

The archive for this account is missing. Krydos somehow finds it usually, but I don't know where he's getting the data from, so I'll have to let him do this one.

Unarchived.

@yashrs: You make a good point...200 is an absurd amount of headers to need for a request. Even 100 is quite ridiculous when you consider a typical page request has <20 entries in the header...I suspect he may need to rewrite his code.

Krydos is the one to ask about this.

That account is not suspended. If you're seeing a suspended page, please clear your cache.

Fixed. When an account gets recreated the space goes back to 1000MB by default. The same would happen if you deleted your account and made a new one. If that happens, just let us know and we can add it back

Discord is best for real-time stuff. An ongoing attack is likely to be discussed in Discord (or possibly a forum help request) first, and assuming it subsides quickly, will never make it to the News forum or other media channels. Planned events such as migrations, server updates, maintenance, etc. are always announced in the News forum, as are unplanned events with an extended impact (extended DoS attacks lasting longer than a day or so, disk failures, etc.) Twitter and Facebook are managed by a bot and will post the same announcements made in the News forum. They aren't manned.

Something/someone was overloading Tommy earlier. It looks like it was a DoS attack, which isn't terribly uncommon...we sometimes get hit with these, usually as retaliation for things like banning someone's phishing site. If it were internal (software malfunction or abusive user), they'd end up suspended, typically within a few minutes. The fact it lasted for hours alone suggests external causes. That's backed up by Tommy's firewall log having a ton of new blocked IPs from China today... Notice all the orange and red betwen 1500 and 2000 UTC): http://heliohost.grd.net.pl/monitor/ During such events, it's not uncommon for connections to fail or for things to randomly hang or crash. If you're logging in using our website, an Invalid Password message will be display if the server is down and cannot be contacted to verify your password (it really should be modified to report that the server timed out verifying the password). The event in question has since subsided and service should have returned to normal. If your account is still not working, please let us know and we'll get it going again for you

I know Krydos was messing with Tomcat on Tommy recently, and if I had to guess, it was cancelled for lack of use. I'll let him confirm that, but if that's the case, no we can't activate it again because someone else has already been given your slot. Tommy is more restrictive when it comes to non-use because we allow fewer accounts over all to keep the server stable. Java service is automatically removed if you have insufficient or no traffic to your Java app for any period of time (more than a few days). For Tommy, this is usually the only way the line gets to move since suspensions/inactivity aren't terribly common on Tommy (as opposed to Johnny, where numerous people end up suspended every day for a myriad of reasons).

I’m not sure if this is possible or not. I suspect a permission issue would be the cause if it’s not. I’ll pass this to Krydos, but is there a reason you can’t just run the sql queries in a php script or something and call the script from the cron? That’s what I do for database maintenance on my systems (though I use MySQL).

Unblocked. It can take up to 10 minutes to be effective. It was for failed cpanel logins. If you use https://heliohost.org/login/ , this won't happen.