wolstech

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).

It's because your account was deleted during the Johnny disk crash. Backups of any recoverable data can be downloaded from https://heliohost.org/backup/, but the server itself has not been repaired yet (will probably another few weeks). In the meantime, your options are to move to Tommy, buy a VPS, or wait until the server is repaired so you can be set back up on Johnny. (Once the server is fixed, users who had a Johnny account will be given the option to either automatically restore their backup if we were able to create one, or to create a new account without waiting for signups to open if there is no backup available). Please see the News section for more information. https://helionet.org/index/forum/1-news/

The server is still broken and has not been rebuilt yet. We just recovered the data and made it available in backup form. The server will likely take several additional weeks to rebuild. Once that’s done, the plan is to replace that message when logging in with the option to either restore your backup into an account, or reinvite yourself without waiting for open signups if there is no backup available for you.

The execution time limit cannot be increased to prevent overuse of resources, and to be honest, if a page needs to run this long, the user is going to be long gone before it finishes anyway. If this is for Wordpress, you're better off finding different software...it's known to get people suspended without increasing any limits. The memory limit was already set to 128M, the max_input_time was already set to 60. The max_input_vars, post_max_size and upload_max_filesize have been increased for the domain plj.my.id. The domains mails.papale.my.id and papale.my.id have been removed. The domain plj.my.id has been made your main domain. Note that the document root has changed as a result of this (it's now ~/httpdocs instead of ~/plj.my.id). I configured SPF for you, but am unable to configure DKIM because the server fails to generate a key for your domain. Krydos will need to take a look at why the DKIM key will not generate. The bubble that usually lists the DNS record to use has nothing listed even after I turn it on and refresh the page...

Space increased. Thank you for the donation

Do you want a control panel installed on it? Many users ask for a free control panel product like Hestia so it comes preconfigured for web hosting and they can control the VPS from their browser (VPSes come with SSH only by default and you'd need to install Apache, PHP, mysql, etc. yourself, but a control panel includes all of that stuff).

That account is on Johnny so it's not worth fixing at this point. It's also no longer over a quota due to the rollback...

Your account was on Johnny and was lost in a recent disk failure. We were only able to recover accounts created prior March 8, and even then, we were only able to recover the data as of March 8. Please read the News section for more information.

This issue appears to have resolved itself. Webmail is now working on your account and I was able to issue a certificate for webmail on your account when I tried.

That account was deleted in the recent Johnny disk failure due to being created after March 8. However, you are one of the lucky 16 users who has a backup newer than March 8 available. You can download your data as of June 12 from https://heliohost.org/backup/