wolstech

Unsuspended. It should work again in a few minutes.

We only provide support in English. Topics merged because they're the same person. Users are only allowed to have one account. Which one do you want to keep?

It was for high server load, specifically for using 102GB of memory. Please fix the issue quickly. If this happens again, we're going to need more information about how you will fix it in order receive a second unsuspension. Unsuspended.

A look in his account shows: #EXTM3U x-tvg-url="https://www.tsepg.cf/epg.xml.gz" #EXTM3U Tataplay M3U Playlist by CoolXtreamIPTV :) #EXTINF:-1 tvg-logo="https://i.ibb.co/0MxkfK8/coolxtream-logo.png" group-title="???? ??? ????????",?????????? ???? It's a tool for watching video streams for free. That file in the first line is a list of available channels in the form of a compressed ~40MB XML file. Looks to be mostly India-centric stuff, but there's definitely some stuff from the USA like Comedy Central, Nick Jr., and MTV on the list too. Copyright infringement, considering there are channels in the list that are typically only available on paid streaming or cable, and this tool contains code to let you view a decrypted .mpd file without paying.

No idea on why automatic doesn't work, but you're the first to ever even mention it. Most people just use SSL which is the recommended setting. Reverse DNS will never match for accounts on a shared IP address and is normal. This is not unique to us, but is the nature of shared web hosting. Email servers receiving mail from a shared IP generally see the server hostname for reverse DNS (johnny.heliohost.org or tommy2.heliohost.org) instead of the domain in the From address.

SPF and DKIM need to be set up if you need to send emails. If it's going to be receive-only and you won't be sending from this domain, there should be no additional action needed beyond creating mailboxes. Do you want us to set up SPF and DKIM for you?

Your account has been reset. Please look for an email shortly to finish the process (it may go to spam).

Also, while we don't offer a decent free node option due to the cost of our servers, we're cheaper when you compare the paid plans: Them: $98/year for '5 projects' and 2GB RAM, presumably node only. HelioHost: $75/year for Venus VPS running Node with 2GB RAM (same as them), root access (unlike a container in a shared AWS environment), has no project count or other limits, and you can also run other non-node things on it if you want.

I mean that the amount it costs them to provide that paid plan is likely a lot less than what they're charging for it. They sell it for $98/year, but it could be costing them a fraction of that in AWS bills. If they're making, say, $50 in profit on that plan, they could just use some of that to cover the cost of the free plans (i.e. they spend $20 to host the free users, and just consider $30 to be profit instead of $50). To them, that $20 spent on the free plan would be considered a marketing cost since it likely converts people into paid users quite a bit.

The margins are probably so large on the paid plan that they can eat the cost of small containers. It’s also completely possible that they require a crapload of information to sign up and then they sell it for marketing purposes. We also own our hardware so don’t have the scale that someone reselling AWS would which is why we can’t afford to offer more resources for this.

That's more than 7x what we provide considering they almost certainly measure it as continuous usage (our 100GB/day is a cumulative sum that translates to only about 70MB continuous). An empty node app can use 60+ continuously on a good day to sit there and do nothing, depending on what modules you load.

Domain added. It can take up to 2 hours to work. You'll need to point the domain to our name servers (ns1.heliohost.org and ns2.heliohost.org), or use A and AAAA records on external DNS pointed the IPs shown in plesk to actually host it here. If the domain isn't pointed to us, it will disable itself after a week or so.

Krydos can install this for you.

No. Lily is the only windows server we have, everything else runs Linux for cost and compatibility reasons. Lily has a classic asp website on it already so it is supported, it’s just not user maintainable. This site is classic ASP running on lily. http://claudemifsud2.heliohost.org/ (he has a proper domain for that site as well, but I don’t remember what it is on top of my head and can’t look it up since I’m on mobile). Other than an inability to send email through localhost (you have to use Johnny’s SMTP to send email instead), the application should run but I would need to install it for you.

So, Lily is...weird. It runs Windows Server 2016, and has no control panel. It does not run Plesk or anything else, all you get is FTP. Some options can be controlled via web.config, but I have to configure many things for you. Eventually Lily is going to be rebuilt to run plesk like the other boxes, but we don't know when that will happen as getting Morty out the door has a priority. Lily requires you have a Plesk account already on Johnny or Tommy, and sort of acts like an extension to a Plesk account. It lacks things such as a mail server so it depends on the Plesk account for those functions. However, Plesk can't actually control Lily, so you can't use Plesk to manage files or the like. As of now, Lily supports: .NET 4.7 - 6.0 PHP 5.6 - 8.0 MariaDB SQL Server Express

Krydos can cancel your VPS for you.

DMARC has been added since it was missing.

One of those is because dmarc needs to be fixed (says its missing), one is because the body of the message was empty, and the rest is simply because .space has a poor reputation due to frequent abuse for spam and phishing. There is no fix for the TLD issue other than buying a new domain with a “normal” TLD like .com/net/org or similar. You can fix the empty body error by sending test emails that actually have content. The only one we can check on is the dmarc record.

Post the link to the report, we actually need to see the details on it.

Domains added. They can take up to 2 hours to work.

Plesk does not have the ability to talk to our DNS, so these will never set up on their own. Also, several IPs in that SPF (notably the .77 and .67 IPs) are obsolete or irrelevent (.66 and ::3 don't host any user accounts and would never send user emails). You only need the .106 and :2009 IPs for Johnny. I'll let Krydos add the DKIM value as I cannot figure out why that record causes the zone file to become invalid (named-checkzone comes back invalid with a syntax error on the line with the key if I add it, so I removed the DKIM line for now). SPF and DMARC are added.

Removed.

I just checked and they were set up already but SPF was configured for the wrong IP address. I've corrected that issue and email deliverability should improve in the next few hours. If you continue to have issues after a few hours, please use mail-tester.com and post the report here so we can see if there's anything else we can do to assist with email that isn't delivering.

Are you sending the emails and they’re not delivering? Or does it actually give you an error? If you’re sending emails, but they’re not delivering to the recipient, it’s usually because SPF and DKIM aren’t set up (you have to request this if using our name servers, or you do it yourself if using external DNS).

Krydos should be able to help you troubleshoot your VPS.