wolstech

Stripe I think Krydos has to cancel it and then just have you create a new new subscription. That platform is relatively new for us, so integration for stripe on our end is decidedly lacking... Escalating to see if Krydos can handle this for you.

Domains added. They can take up to 2 hours to function. Also, I noticed you're using Cloudflare. If you haven't already done so, be sure to update your A and AAAA records, as the IP addresses changed when the account moved to Morty.

That account isn't suspended on my end. I'm not sure why it's suddenly showing an inactivity page, it was renewed back on September 17. Let's have Krydos take a look.

We haven’t even started developing that server yet, so this isn’t a consideration for the foreseeable future. We’re going to be more concerned about how well (if) basic Java is even going to work.

India is a known issue. It's due to their weird banking regulations. You can make one time purchases through paypal if your card has international support, but subscriptions aren't allowed so VPSes cannot be purchased through our website. Krydos can set up a stripe link for a VPS, but it may end up being the 6 months one time purchase option. Not sure if the subscription is an option with Stripe in India or not...

Credit of $87.16 has been added to your account. Thank you again for the very generous top up Please let us know if you need anything else.

We have to add the subdomain for you. What domain do you want added?

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

Your account has been reset. You'll receive an email when it completes with a link to finish the reset process and create a new account.

You did it correctly. I see the payments in there and we'll credit you shortly for these. Thank you very much for these! I'm just waiting for an answer in one of our staff channels since I'm not sure if/what the multiplier should be on them (the $19 would be $24 of credit up front for example, but since there is no $50 option I had to ask).

Yeah you can only have one account, so you can only keep sentinelx. You can have up to 10 domains on a single account though. Do you want me to put both domains in the same account for you?

The settings shown are correct, however I recommend the proxy option be set to DNS only while you're getting things set up. The domain is working for me, if you're still seeing that error you should clear cache.

Domain changed. It can take 2 hours to be effective. The suggested way to set up Cloudflare is to configure the domain using our name servers, then tell Cloudflare to copy the DNS directly from our system. To set them up manually, at minimum, you'll need: A record (blank name) pointed to the IPv4 shown in Plesk AAAA record (blank name) pointed to the IPv6 shown in Plesk. CNAME record ("www") pointed to frozennodes.com If you want email to work, you also need: TXT record (blank name) with value "v=spf1 include:tommy.heliohost.org ~all" TXT records for DKIM (see Plesk for the correct names and values). If you want webmail, a CNAME record ("webmail") pointed to frozennodes.com (you'll also need to enable webmail in Plesk and wait 2 hours). Note that if setting up mail clients, you need to use tommy.heliohost.org as the server host name instead of your domain in the server settings of the mail client.

No problem Please let us know if you need anything else.

That error can be either Apache restarting, or your app taking too long to respond (i.e. it's too heavy for the server and can't respond before it times out). If the issue doesn't go away, the usual solution is to fix your software or find different software. See https://wiki.helionet.org/504_Gateway_Timeout and https://wiki.helionet.org/502_Bad_Gateway

It's probably because you're using the IP address for the server name, causing the common names to not match. You need to use tommy.heliohost.org instead.

By configure DNS, we just mean that you need to set the name servers for the domain to work. You should use ns1.heliohost.org and ns2.heliohost.org.

Domain added. Please be sure to configure DNS. The domain can take up to 2 hours to start working.

Escalating...

We haven't heard from the other user that matched, so I've cancelled the pending suspension on your account. Shared networks are indeed a common cause of false detections for this...

You need to install an SSL certificate. Assuming your domain's DNS is configured correctly and you're not using something that can break domain validation (like Cloudflare with strict SSL mode enabled), Plesk should actually fix this on its own. You can go into the SSL options and issue a certificate from let's encrypt to fix it more quickly. Once you install a valid certificate, it should start working properly within two hours.

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

We’ve updated our records to indicate that you want to keep the sat4all account. The other account has been banned and will delete on its own in 60 days.

We've updated our records to indicate that you want to keep the other account sat4all. The rafal1509 account will be automatically banned in about 2 hours when the 24 hour warning period runs out. Thank you for complying with the terms of service.

This support request is being escalated to our VPS admins.