-
Posts
24,552 -
Joined
-
Last visited
-
Days Won
869
Everything posted by Krydos
-
You can use external DNS and host the domain directly with us by setting your A record to 65.19.141.77 and your AAAA record to 2001:470:1:1ee::2002. You don't have to use our NS to host a domain with us.
-
The records have been changed, but it was pointless because you're not using our nameservers so it's not going to change anything. [root@control ~]# dig +short MX @ns1.heliohost.org optbeacon.com 0 tkolp.com. [root@control ~]# dig +short MX @ns2.heliohost.org optbeacon.com 0 tkolp.com. You can see the NS records you're currently using with this link https://dnschecker.org/#NS/optbeacon.com If you want to actually change where the mail is routing to you need to change the MX records on dns1.registrar-servers.com and dns2.registrar-servers.com.
-
-
[Solved] Inquiry on my request to add subdomain
Krydos replied to seintitus's topic in Escalated Requests
Done. -
[Solved] Setting up my play...er, work area :)
Krydos replied to gektek's topic in Escalated Requests
Added. Thanks! Correct. Login to your registrar and delete any existing NS records, and then put ns1.heliohost.org and ns2.heliohost.org as your only NS records. We just finished a fundraiser to buy a new server, and have plenty of VPS space that just opened up. We will also be releasing our new Morty server before much longer. Yeah, definitely. HelioHost is great for people who are just learning still. Very few people want to pay for hosting when they have no idea what they're doing so we get a lot of people who are new to web hosting. Now that the domains have been added to your account you can create the email addresses yourself. Then once you set the NS records the mail will automatically flow to your HelioHost account instead of your DreamHost account. I would keep an eye on the old mailbox for a few days though in case some mail servers have the old MX record cached. No problem. Let us know if you have any questions. -
[Solved] Undelivered emails (Reverse DNS Issue)
Krydos replied to seintitus's topic in Escalated Requests
It should be working now. -
Is there any particular reason you want the wrong DKIM value set? Plesk determines the DKIM value for you, and if you set it to the wrong value you listed above your emails sent through Plesk will be marked as spam since DKIM will fail. If you're sending emails through something other than Plesk you need to let me know the DKIM identifier. Plesk uses "default" so it will have to be something other than that if you want to be able to send emails through Plesk and some other service.
-
[Solved] Undelivered emails (Reverse DNS Issue)
Krydos replied to seintitus's topic in Escalated Requests
Oh my bad, I didn't notice that you had let your account get archived. When an account gets archived the SPF, DKIM, and DMARC get deleted, so when you renew your account you have to request them be set up again. Try sending another test email. -
SPF, DKIM, and DMARC have been set up on your optbeacon.com domain. I recommend sending an email to https://www.mail-tester.com/ to make sure everything is configured correctly. If the score is less than 10/10 please post a link to the full report so we can fix any other issues that there may be.
-
Remote access enabled.
-
[Solved] Undelivered emails (Reverse DNS Issue)
Krydos replied to seintitus's topic in Escalated Requests
It should be fixed now. Try sending an email to https://www.mail-tester.com/ to make sure everything is good. Please note that each time server your account is on is targeted by a DDoS we may need to move your account to an alternate IP to mitigate the downtime for everyone's websites. This may temporarily break the email. After 1 week without a DDoS attack we will move everything back to the original IPs. -
Going to mark this as solved since you don't need admin assistance to add non-wildcard SSL. If you still need help let us know.
-
Since this looks like a SSL verification, are you aware that Plesk can provide free SSL certificates and then automatically update them when they get close to expiring? I don't mind adding the DNS record for you if you really need it though.
-
Generally what happens is the old Hestia process locks up and won't exit. You can force it to exit by using the kill command. Then you can do apt update and apt upgrade to update the software for the whole server.
-
Remote access enabled.
-
Fixed.
-
Here is the payment link for another 6 months https://heliohost.org/vps/pay/?code=nsy13vgkn8jpMQIF We don't have a 12 month plan or a pay as you go option currently. We may add them in the future. There are a few Indians who are unable to set up subscriptions because of their country's crazy laws, and a few other people have expressed interest in just paying month to month manually rather than using an automatic subscription. We'll make a news post when that functionality is added.
-
Your VPS has been canceled and you won't get charged again. Thank you for using our VPS service.
-
We are installing the new server in our cabinet. There may be downtime on some servers and some VPS over the next few hours as we rearrange the other servers to make room for the new one.
-
- 1
-
-
Bandwidth is unlimited, but we do monitor memory and CPU usage. Generally the more bandwidth you use the more memory and CPU you use as well. Well designed websites can have 100 GB of bandwidth and not get suspended, but poorly designed websites, such as Wordpress, can get suspended for 100 MB of bandwidth since Wordpress is so bloated and resource hungry.
-
Unsuspended. Please stop trying to cram 20 GB of database into a 5 GB account. I'm actually a little disappointed in Plesk for not stopping you before you even started importing the data.
-
-
You posted it in your screenshot. 5000 MB.
-
Yeah, we can help you transfer your database to a VPS if you want. They start at $4 per month, and would handle a 20 GB database just fine. Like Wolstech already said our largest Tommy or Johnny account can hold 6 GB so you're never going to fit a 20 GB database into that. You crashed PostgreSQL and caused several hours of downtime for thousands of other users so I fixed it, and then emailed you to let you know about it. You ignored my email, and proceeded to crash MySQL and Plesk for several more hours for thousands of users instead of talking to us. If someone accidentally causes downtime I tend to give them a second chance and let them know what they did wrong, but since you ignored us and made things 10 times worse you definitely deserve a suspension.