wolstech

Both root admins are in the USA, so when you were asking for this, we were asleep. Support requests can take 24 hours or longer in many cases. As for actually removing this, I'm working on it. It's a bit more involved than just deleting the files since you look to have used laravel toolkit and git. Laravel toolkit messes with the document root for the domain (so I have to change that back), and git will break your domain if the repo folder goes missing due to manual deletion.

So you would like us to delete all content inside of the app and learn subdomains, but leave the empty domains so you can reuse them? Correct?

You'll need to be more specific as to what you want deleted. There wasn't any meaningful amount of logs to remove. The bulk of your space is used in the app.ppblk.space and learn.ppblk.space domains. You can also purchase more space if you want. $5 for an extra 1000MB, one time charge. The max is 6000MB per user. Also, you have a bunch of unused domains (ml, lms, social, chat). While removing these aren't going to solve your space issue, do you plan to use these empty domains (you don't have any space for content...) or can we remove them to improve performance?

Krydos can set this up for you.

You do realize we only have about ~5 continuously active staff total to handle several thousand users right (Krydos, myself, Moneybroz, Kazvee, Unknown025)? Two of us have root access (Krydos, me). There's also Ashoat (our founder), but he is rarely active on the forum or support channels. We also have other moderators who help out from time to time but aren't as active as the 5 above. The staff group is a lot smaller than you think, and we rarely come across people who: Don't have ulterior motives Have the skills to actually handle this line of work. The moderator position is mostly a customer service job that understands how websites and servers work, but a root admin has to be capable of understanding the inner workings of the server, be able to program in several languages such as PHP, SQL, Shell Script, and Python, know how to administer linux, be able to tolerate abusive users and identify lying ones, etc. Are willing to work for free. Don't leave. Only #2 is reasonably easy to determine (can be tested for and/or taught). #1 is why we have the policy about not asking for promotions, very few people are willing to do #3 (most who ask for promotions expect something in return, whether it be special treatment, money, or otherwise), and #4 happens quite a bit if we manage to find someone who qualifies for the first three. We also don't have a large pool to pick from. More than half of our users never even look at the support offerings because they didn't need them, let alone help out on them. Others can barely figure out how to build a website without using Wordpress, let alone qualify to support the platform its running on. Another chunk is cybercriminals who come here looking for abuse hosting and get banned, and we often have moderators who end up leaving after a few months because of real life getting in the way. I wouldn't be surprised if we pick up an additional moderator or two over time as Morty rolls out, especially if there ends up being the demand we expect. If we do, odds are it'll be someone from the discord support channel.

I have a feeling you hadn't waited the full 2 hours for the domain to set up after you created the account. The 404 errors are normal for the cgi-bin folder on new accounts until the domain finishes configuring and Apache restarts. This is working for me and https://pyknite.helioho.st/cgi-bin/test.py is showing the expected result now.

Oops...I must've sent that from the dev environment (I have both bookmarked and hadn't had coffee yet this morning when I responded to this)...yeah that won't work. Sorry about that. The new invite Moneybroz sent you should work.

Invite sent. Thank you for the donation.

Donation is verified. Can you please provide another email address for the invite to be sent to? Email addresses attached to a broken Johnny account cannot receive the invite, which is why it didn't come automatically.

We don't insert or inject anything into the websites we host. Odds are you have either poisoned ads, a malicious script on your site, or possibly even a malicious browser extension on your PC. When I view your site, I don't see any cookie for yadro.ru, and also didn't encounter any redirects, so my guess is it's malware on your PC...I see these cookie domains for your site.

At the moment, you would need to donate to get a Tommy invite. If you already donated and didn't receive the invite, please create a topic over in customer service with the donation transaction info and we can get that fixed for you. Morty will be a faster, paid version of Tommy that doesn't have load or inactivity suspensions. It will be a subscription product with a minimum monthly fee of I believe $1, and the price paid will increase based upon your load. This offering isn't even released yet. I think Krydos is still working through some licensing and server prep stuff, but the server itself was finally finished being built yesterday. The tasks being worked on most recently involved cloning the empty Morty to expedite the rebuilding of Johnny...

You're on Johnny, which is broken due to the recent disk failure and is awaiting a rebuild. Your data as of March 8, 2024 is available via https://heliohost.org/backup/ Your choices for the moment are to either: Move to Tommy by donating then creating an account via the invite you get. Move to Tommy by donating then requesting we restore your backup from March 8 to create your Tommy account (ignore the Tommy invite email if you get one but want the backup restored instead), Wait for Johnny to be rebuilt, at which time you'll have the option to restore your backup or create a new account without waiting. Buy a VPS.

It hasn't opened for users yet (still in development), though I'd expect it to be available pretty soon provided everything goes smoothly. It's just about done, but we're working on a few other things involving it before we open it to the public, such as cloning it before it has users on it to simplify rebuilding Johnny, some licensing and billing stuff, etc.

It will recover the account in the state it was in on March 8, so if you had a migrated account, your restored account will also be a migrated account. If you want to avoid that, you would want to be reinvited with an empty account instead, and then manually restore the data from the backup file.

The 2022 expiration date is the default Plesk certificate. I just reissued it for him, it should work again within the next 2 hours.

We have some form of either scheduled rebuild or a disaster requiring a rebuild every 2-4 years it seems. This is I believe the third or fourth time we've had a disk failure in my 11+ years, and the first where we've just flat out lost a bunch of accounts, though in past failures the accounts were often recovered in pieces that didn't necessarily restore cleanly (e.g. plain zip archives instead of a self-restoring archive, and I think we lost some databases one time due to InnoDB crashing). This is also the first disk failure for a Plesk based server. There were some lessons learned here, because this failure occurred on a server with disks that actually had redundancy. In all prior incidents there was no redundant storage. This time around we had a mirror volume, but also a policy of disconnecting the idrac management interfaces on our servers for security reasons (that decision was a relic of the days when we didn't have redundancy and as such had no need for them). As such we had no way of knowing one of the two disks in the mirror had failed, so it was never replaced before the second one also failed. That policy has since been changed as a result of this incident. It's worth noting that we rebuild servers every 3-4 years anyway for preventative maintenance. Even with no failure, users would likely see their account either moved to another server, or archived while the server is rebuilt, then unarchived again upon completion. The servers tend to develop strange issues just due to clutter from account churn over time even if they don't outright fail, and software needs updating too (the OS especially, and they don't always update gracefully) so its easier to rebuild them to ensure they're clean and current. Once Johnny is fixed and Morty is out the door, Tommy will likely be up for a rebuild to update it since its OS will be obsolete soon, and it has a lot of weird quirks that developed as a result of recovering it from ransomware incident in early 2023...

$0. Plesk donates the licenses, it would be uneconomical to offer service at no cost if we had to pay for it.

Krydos can check on this donation for you.

Duplicate request and also wrong forum. See https://helionet.org/index/topic/61483-remote-access-for-postgres-dbs/

The domain cospi.top has been cleaned up. As above, the account it was attached to was already deleted.

Yeah, that looks like an expired softaculous license. Escalating...

Both of those errors are because your account was on Johnny, that server is broken due to a disk failure and is awaiting a rebuild, which may take several weeks. Your account was created after March 8, so it was deleted during the recovery process. Please see all of the recent Johnny announcements in the News section for more information.

MariaDB and Postgres are two entirely different database systems and aren't compatible with each other. You created a MariaDB database but are trying to connect using a Postgres tool. You need to do one of the following: Create a postgres database instead, then have Krydos enable remote access on it, then connect to it. Use software designed for MariaDB to connect to the database you already created. Which one you do will depend on what database type you actually need... Also, the server hostname should be tommy2.heliohost.org, not your domain.

504 Gateway timeout for this can be a few different things, I'd bet in this case the installer needs too much time to install. Nextcloud is just heavy software. Krydos might be willing to temporarily extend the execution time limits so the installer can finish, but it would need to be reduced again after installation completes. Escalating.

Interesting. It works properly when I do "login as customer". I would start by clearing cache, and if it continues to malfunction, try another browser (I've seem browser extensions cause weird behavior in plesk before).