wolstech

The domains do not fit on your account as there is a limit of 5 domains on Johnny. If you want these added, you'll need to either upgrade to Tommy (which has a 10 domain limit) or remove 2 domains from Johnny first.

The specified backup has been discarded and your account has been unsuspended. The domains can take up to 2 hours to function again.

That username is already in use. Also, keep in mind that hosting account usernames cannot be changed without resetting your account, which deletes all of your data. We can change your main domain though if you would like, as the domain is available.

This is a quirk with how Plesk calculates space. The main domain's space meter includes the entire home folder, which includes all of the domains on the account. The space meters for added domains usually only show non-file stuff specific to that domain (like mail and logs). All of your files for the telenove and salt subdomains are being counted under the lia.helioho.st's space.

See https://helionet.org/index/topic/67060-hh431164-new-vps-account-request-aapanel/#comment-298850

Domain added. It can take up to 2 hours to function.

DKIM, SPF, and DMARC have been set up for the domain cvsbtech.heliohost.us. We recommend sending a real email (not just the word "test" or a blank email) to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.

Krydos can assist with this...

Is this issue still a problem? It looks like you got your wiki working on the domain, so not sure the directory listing is still important... (I also responded to your Mod Security issue in your other topic for you).

Glad to hear its working for you Please let us know if you need anything else.

Indeed it is mod security. You can see the error in Plesk in the Logs for your domain. ModSecurity: Access denied with code 403 (phase 1). Pattern match "\\\\D" at TX:1. [file "/etc/httpd/conf/modsecurity.d/rules/comodo_free/30_Apps_OtherApps.conf"] [line "4530"] [id "240950"] [rev "2"] [msg "COMODO WAF: XSS & SQL injection vulnerability in Pragyan CMS 3.0 (CVE-2015-1471)||salt.wiki.gd|F|2"] [severity "CRITICAL"] [tag "CWAF"] [tag "OtherApps"] [hostname "salt.wiki.gd"] [uri "/User:Lia"] [unique_id "aZnLyrW2MUbixOOUfFzWWQAAAok"], referer: https://helionet.org/ You can actually whitelist these yourself in the Web Application Firewall page of Plesk. I went ahead and added rule 240950 to the exception list for you. The changes will take 2 hours to take effect.

Domain added. It can take up to 2 hours to function.

Domain added. Please be sure to configure DNS either using our name servers (ns1.heliohost.org and ns2.heliohost.org) or by using A and AAAA records pointed to the IPs shown in Plesk. The domain can take up to 2 hours to function.

Your account has been reset. When the reset finishes, you'll receive an email with a link to create a new account. Please let us know if you need anything else.

Those domains are all working properly for me at the moment. The "redirect" (which was probably the domain setup page) and the certificate errors suggest you didn't wait 2 hours after having domains set up before trying to use them. During that 2 hour period, Apache isn't fully configured. New domains won't work properly until Apache restarts. Note that the 502 error is normal on Johnny and occurs approximately every 2 hours due to the Apache restart. https://wiki.helionet.org/502_Bad_Gateway It usually lasts a few minutes. As for the FTP connection, try using SFTP instead of FTP/FTPS to access your account: Hostname should be johnny.heliohost.org, port 1373, and use your plesk username and password. Most users find that this works much better than regular FTP, and it's also more secure.

Krydos can assist with this.

Yeah, that's a major reason we recommend manual configuration using the server name (tommy.heliohost.org). Mail clients today check that the server name you enter against the name that the server identifies as when you connect, and the name on the certificate if applicable. The mail server on Tommy always announces itself as tommy.heliohost.org regardless of user, so when you use javalan.helioho.st as the host name, the client connects, gets a "Hi I'm a mail server called tommy.heliohost.org" and the client goes "WTF that doesn't look like javalan.helioho.st, I'll show a warning about it". The tommy certificate is always renewed automatically and using the server host name means the server HELO announcement matches the host name. That said, I just ran the renewal for your SSL certificate manually for you. You can do this yourself in the future in Plesk under SSL/TLS certificates->Reissue Certificate->Install under the Lets Encrypt option->make sure to check the box that says "Secure mail on this domain"->Get it free.

Your account looks fine on our end. Is there a specific error you're seeing? (Note that while accounts can send email right after creation, most email providers will not accept the emails unless you request SPF and DKIM... these email security features are not set up by default).

The domains do not fit on your account as we lowered the domain limit on Johnny accounts to just 5 back on January 28. https://helionet.org/index/topic/66787-domain-limits/ You're allowed to keep your existing domains as-is (you have 8), but if you want to make any changes, you must comply with the new limit, which for you would require removal of at least 3 domains to bring the total down to 5. If you want these two added, you'd actually need to remove 5 domains (so you have 3 + the 2 new ones). If you need more than 5 domains, you will need to upgrade your account to Tommy (which still has a 10 domain limit), or Morty (15 domain limit), or more (by having more than one Morty account).

You can renew the certificate in Plesk under SSL/TLS certificates (select the option to secure mail when reissuing the certificate). That said, the supported mail configuration is to use tommy.heliohost.org as the server for IMAP/SMTP instead of your domain. Doing that will prevent this issue (as well as several others).

You can often see the errors in the Logs section of Plesk. Otherwise the errors should just show when your application runs (display_errors is on by default, but you may need to modify your code to see them if it's set to prevent displaying errors).

NodeJS has been turned off on your account and you've been unsuspended. Please fix your code quickly. Unsuspended. It may take up to 2 hours for the account to work again.

You're suspended for high server load. Something went very wrong with your node app it looks like...it suddenly used some absurd amounts of memory, caused Johnny's load to skyrocket to over 130 (which caused downtime), and subsequently got you suspended for excessive memory usage (graph shows usage Monday at 1600 UTC to Tuesday 1600UTC) Can you explain what happened here?

That topic (and the wiki guide, which has long since been written) is only applicable to accounts on our Plesk servers. It looks like you have a VPS. You'll need to find a guide for setting up Flask on a VPS and follow that instead (there's many online), or you could create an account on one of the normal Plesk plans (you can have both a Plesk account and a VPS) and use Flask on that account.

That guide is only applicable to Plesk accounts, because we installed Flask and its other requirements on the Plesk servers. VPSes don't have Flask by default, so you would need to follow a guide for a VPS to install it yourself.