Unknown025

This means another account logged in from the same network as you did. Common triggers include logging in from a corporate/school network or using a VPS. Krydos can probably provide extra clarification if you'd like. I'll cancel the pending suspension for your account in the meantime.

Your account has been reset. You should receive an email to recreate your account shortly. Also, it doesn't look like you have any subdomains...

A VPS admin will be able to help with this in the morning (i.e. in about ~7 hours).

Domain added, it'll take effect in about twenty five minutes. Unfortunately, Plesk does not allow for setting a target directory for a domain.

Domains added, they'll take effect in about 25 minutes. Even though they are subdomains, they still count towards the 10 domains limit.

Looks like Wolstech added those domains for you. Let us know if you need help with anything else.

Unfortunately, we don't offer *.heliohost.org domains anymore. I can add industriasabal.heliohost.us or industriasabal.helioho.st instead.

An administrator will be able to help with this.

Domain name changed to worksyncpro.helioho.st. Also, if you want to still add worksync.helioho.st, a staff member can set that as an addon domain for you.

An admin will be able to do this for you.

A VPS admin will be able to do this for you.

Wolstech can do this for you once he's free.

Domain added, will take effect in about ten minutes.

Domain changed, will take effect in about an hour. You'll need to update your nameservers to "ns1.heliohost.org" and "ns2.heliohost.org".

Domain added, will take effect in 20 minutes.

Your account was suspended for hosting nulled software, which is against our terms of service.

A VPS admin will reach out to you. Just as a heads up, I believe that additional IP addresses cost an additional $1 each.

Domain added, it'll take effect in a little under an hour.

Domain added, it'll take effect in about an half an hour.

Unsuspended.

Domain added. You'll need an AAAA record/HelioHost's nameservers configured for it to work.

Domain added.

We traditionally don't whitelist certain IPs, so if you have a service connecting over FTP from an Azure server, as long as it uses the correct credentials, it shouldn't get blocked.

This is something an administrator can do, but mail quotas are changed on a case by case basis. I'll escalate your thread so an administrator can comment.

Glad it works for you now.