wolstech

You can put the protocol in the name field after the name, separated with a period. For instance, the _sip record with protocol _tls would become _sip._tls and get entered in the Name/Host field From MS's website (here):

Since he's on Tommy, the server will get him a certificate from Comodo/Sectigo on its own within 24 hours. He needs to do nothing other than use our name servers and ensure he doesn't have a redirect blocking plain HTTP access to the .well-known folder.

Unarchived. It may take up to 2 hours to start working.

We can't troubleshoot or support any site using CloudFlare. Assuming the domain is added to your account, it should just work once you change the name servers back. CF is notorious for causing tons of issues with our service, so it's recommended that you avoid it if possible. The only times I've seen CF be required was when someone needed either the bandwidth support (lots of static content) or advanced DNS functions. 99% of users don't need it.

Unarchived. It may take up to 2 hours to work.

This domain should now be working. Please clear your cache if you still see an error or queued page.

Nope. We intentionally block users from changing this on their own so they don't hog the server resources. Tommy did not have any major outages. Something's broken on your end or with your ISP: http://heliohost.grd.net.pl/monitor/

Unblocked. It was for failed SFTP logins. Please keep in mind that SFTP takes your cPanel username and password only. It does not support email addresses as the username, and also does not support the additional FTP accounts created through cPanel.

It's 3 concurrent connections on Johnny and Ricky, per database user. There's no limit at all on Tommy (though that's subject to change if abused).

That account cannot be restored because the archive is missing. Invite sent.

Unblocked. It can take up to 10 minutes to be effective.

Great There were leftover DNS entries I had to remove before it would add for you. Let us know if you need anything anything else.

The domain zumbalenzburg.ch has been cleaned up. Try it now.

What settings are you using? Also, keep in mind that due to the performance of Ricky, plain FTP is going to be fastest. Try using host ricky.heliohost.org on port 21, with plain (no) encryption.

Johnny's very backed up due to load at the moment. You're 1 of 10 people currently waiting in line to be created. To be honest, nothing (including actual websites) is fast on Johnny...it's meant for experiments and is severely overloaded. Johnny only has an uptime of 80-90% on a good week (currently showing 87% for the past 7 days), so it might take some time. If you need fast and reliable service, you should sign up for Tommy instead. That server is intended for production websites and responds as most would expect. We aim for 99+% uptime on that server, and it currently is 100% for the past 7 days. Keep in mind that Tommy is very difficult to get onto for free (fills in <5 seconds every day), so you might want to verify your software runs using Johnny before trying to get a free account. Donating is another option (if you donate, we can just move the Johnny account for you).

Unarchived. It should work within the next 2 hours.

Working on it now.

This account failed to restore because of a database server issue. Krydos can usually restore these, but the username will change when he does.

That account cannot be restored because you already have an active account. Do you want me to suspend the active account and restore the old one? Also, the username is bnsoyun, not sarginex.

plantgreenpg.com was successfully unparked from ja190823.heliohost.org. Try it now.

What is the domain in question?

The way our servers work means these getting parked can cause major issues. The outside world won't see much wrong, but stuff running on the server won't function properly, and there's risk of data loss as well. We've actually had it happen at least once, so it's not speculation. It's experience.

Very true. Their service sucks in every way imaginable, especially when it comes to any sort of reliability. I've only seen that one case, so unless we get an influx of freenom users that suddenly can't use their domains, I guess it's best we assume freenom was just sucking that day.

Unblocked. It was for DOS, so not anything you did, but rather our firewall busy trying to keep the server online.

The weird part about this is that I've seen the issue impact Freenom as well. An example case is the guy that went the main domain route last time: https://www.helionet.org/index/topic/38978-solved-dns-problem/ He had a .ml domain. We all know that Freenom doesn't require a .br style registration.