wolstech

These are two unrelated issues. The email issue is actually normal unless you request we set up SPF and DKIM for a domain. I've gone ahead and set that up for you and email from your domain should now deliver. We recommend sending a test 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. I cannot reproduce the insecure connection issue. The domain works fine for me.

It’s probably because of the known issue with ipv6 on Tommy at the moment. Use the ipv4 address of the domain as the host name instead (you can find it in Plesk) and it should work.

You can switch to Morty here : https://heliohost.org/dashboard/move/

Unsuspended. It may take a few minutes to work again.

I see your donation in there and have added the 1000MB space for you. The extra $1 can't be used for space though as it can only be bought in $5 increments. I'd suggest a refund but that will lose $0.50 in transaction fees and its only $1 to start with...

The domains we offer for free end in either .heliohost.us or .helioho.st. That said, you can get a domain anywhere and simply point it to our service if you don't want to use ours.

Krydos will need to assist you since you both want Hestia installed and because Paypal is not available in your country. We do have Stripe as well (which is what Donorbox uses behind the scenes), but I'm not sure whether there's a way to manually accept a single payment through that. Note we do require VPSes be purchased in 6 month intervals when manual/non-Paypal payments are used due to the required manual labor needed to process them. Escalating.

It is temporarily disabled due to a spam issue.

If you're referring to UCEPROTECTL3, that one can and should be ignored. The list's own publisher basically says "don't use this for spam filtering" because it's so wildly inaccurate (their L1 and L2 lists are the "normal" blocklists most think of). They almost never remove entries from L3 and also do not accept delisting requests for L3, so it is basically useless. The list seems to include most data center IP ranges that aren't one of the giant tech companies. You're welcome to use the VPS for email services, however keep in mind that you, as the subscriber, are responsible for ensuring proper use of our services. This includes ensuring that your users do not send spam, phishing, or other abuse, and promptly addressing such abuse if it occurs. We typically pass spam complaints for VPS IPs along to the email address on the VPS account. If you receive abuse reports, you must fix the issue quickly (e.g. change compromised passwords, ban the user if it was intentional, etc.). Failure to address abuse, intentionally allowing abuse, or HelioHost receiving an excessive number of abuse reports for your VPS may be subject the VPS to suspension or termination.

Krydos will need to update the firewall for you.

We have to add them for you. Please let us know what domain you want added and we can do so.

The shell is restricted via chroot, so when you run commands in your account, the system views your home folder as if it were / . This makes it so you cannot see files and binaries outside your home folder. If you create a folder inside your home folder called bin and place a program called runme in it, you would call it using /bin/runme. The passwd error is because of missing symlinks. Follow what I mentioned in that article about creating a scheduled task and running it. Once you do that, your home folder will have a bunch of folders like bin, usr, etc inside containing symlinks to essential system files and binaries. That should resolve the error you're seeing since running a scheduled task will create the missing passwd file mentioned in the error along with the symlinks.

The commands for git deploy actions are jailed to your home folder, which can pose issues like this. Someone else has successfully implemented Plesk's Git deploy actions using a CGI script to run commands during deployment. The method I described here and the responses from that user describing the final solution may be relevant: https://helionet.org/index/topic/63231-run-npm-script-in-git-deploy-actions/#findComment-285189 and should be adaptable to Rails instead of Node. Note the requirement to create and run a scheduled task at least once first to set up the needed symlinks in your account.

Specifically, you need to remove the below MX record to fix this issue. Johnny has to be the only MX on the domain. _dc-mx.d30c4fbcdaba.orcagroup.top

Krydos will need to take a look at this. The system is supposed to leave domains active if the MX is hosted here (you aren't the first to only use the service for email). Escalating.

Duplicate request. (Not that it matters, the account and domain in question are also banned for phishing...)

That cannot be installed on the shared hosting since Inkscape looks to be GUI desktop software... It could technically be run on a VPS, but you'll need a decently powerful one as you'd need to install a desktop on your VPS to use it, which we don't recommend for a server environment.

Deleted. (Normally you can delete your account yourself, but in your case you would have had to restore it since it was archived, then delete it again). Do you want the forum account removed as well?

SSL is already working on your account. I did reissue it so it would cover the webmail subdomain, so if you plan to use webmail that feature will take 2 hours to have SSL support. When a domain is set up, the SSL certificate won't issue until DNS is set up and working because the domain needs to resolve in order for the domain validation to work, and then it takes ~2 hours once issued for the certificate to take effect.

This is a Krydos question. Basically nobody else uses RoR, support for it is rather new, and there is no log available on your end if you set it to production.

Domain added. It can take up to 2 hours to start working.

The extra space has been exchanged for $5 in Morty credit.

AH01276: Cannot serve directory /home/daneesv.heliohost.us/httpdocs/lumos/: No matching DirectoryIndex (planet.py) found, and server-generated directory index forbidden by Options directive, referer: https://helionet.org/ It is indeed is .htaccess file. He had set a custom index file that didn't exist in his .htaccess. I commented out the below line since the file doesn't exist in any folder except ~/httpdocs/planets, and everything works now. As a reminder .htaccess files affect subdirectories, so an .htaccess in ~/httpdocs will affect ~/httpdocs/lumos. If planet.py should be the index for ~/httpdocs/planets, create a new .htaccess inside the planets folder and set it in there so only that folder is affected. DirectoryIndex planet.py

Sure. Domain added. It should start working within the next 2 hours. You'll see a new folder on your account for the domain where you can place the files for Laravel.

A domain configured for Ruby (or Node...anything using Passenger) cannot run PHP at the same time. You'd have to disable Ruby to run Laravel on the same domain. If you want to run both at the same time, you can do that using 2 separate domains on your account. Do you want a second domain added? If so, what do you want it to be?