wolstech

It looks like the Johnny account didn't clean up properly for some reason so I've fixed it for you. The domain <removed> has been cleaned up, and has been assigned to your new tommy account. It should start working shortly.

The Domains don't always clean themselves up correctly. What is the domain you're trying to attach to the new account?

There's actually no way to rename a hosting account oddly enough. Your forum account can definitely be renamed though. In fact, your old forum account should still be valid if you want me to merge the two. Do you want me to merge and rename the forum accounts?

That's what I was trying to do with this guy but he decided on the main domain route. I'll let you know when I get one.

It likely fixed itself because you put it as your main domain (which forces the zone to create). Glad to see it's working now.

Very true. I've just been seeing a trend in chat bots and load suspensions lately. One guy got his stuck in an infinite loop, which is an easy way to spike the CPU. Also, creative coding makes it completely possible to have the bot watch the overall server load and react (e.g. stop doing certain intensive things, or just flat out quit) when server load is up...

Ironically I had a user get suspended for load while following that guide last week...

I know. I can see them set here: https://bybyron.net/php/tools/dns_records.php?domain=kanboard.ml&rec=NS My experience has been that a registrar will not propagate NS records for a name server that sends REFUSED as a response. The REFUSED code is meant for when a server wants to refuse to provide an answer at all, as opposed to answering the query but saying "I don't know about that domain" (NXDOMAIN). Our NS should be returning either a valid zone, or NXDOMAIN if not known/parked. If I manually park the domain (or manually create a zone file for it), the REFUSED goes away and the server will return a valid zone. Once I do this, the DNS propagates across the internet, usually within the hour. What I don't know is what's causing the server to send that REFUSED back for some domains but not others (which correctly return NXDOMAIN). I can't think of any good reason our servers should ever return REFUSED as it currently stands. The main problem is that domains usually don't propagate well (if at all) while being answered as REFUSED, yet the domain needs to propagate so it can be added and stop being refused. As a result, the only fix I've found is for an admin to manually park it (which bypasses the DNS check) unless you use as the main domain.

@Krydos: This is an ongoing issue. cPanel won't let you add the domain claiming the name servers aren't set...even though they are. It never propagates (I had one guy wait almost a week). Only once I manually park the domain for the user does the DNS propagate (and it does so within the hour). Eu.org is the worst affected, but I've had a few other freenom domains like this do the same thing. The issue is that our name servers return REFUSED instead of NXDOMAIN like they should. The REFUSED code keeps the registrar from propagating the records for some reason. If you take a look through the past week or so, you'll see me manually parking a bunch of these for this issue.

We’ve had people try for weeks without success, and others get it on their first try. We don’t provide specifics on how many per day is given away, but it’s always less than 3 for tommy. That’s in contrast to Johnny which usually gives out 20+. The number given by a server is never 0 unless announced. On average, tommy fills in 0-5 seconds. There’s no need to check the box, just click the sign up button. If it kicks you out, you didn’t get it. Also, don’t do the validation too early or your session can time out before midnight.

Unarchived.

Ricky supports 2.7 and 3.6. If you need 3.7, that's available on either of the other two servers. Module list for 3.6: http://krydos1.heliohost.org/cgi-bin/modules36.py Module list for 2.7: http://krydos1.heliohost.org/cgi-bin/modules27.py

We generally don't provide exact numbers to the public because it varies from time to time and we don't want to disappoint our users who find old and outdated numbers. I will say that it's less than 3 per day though on Tommy. This is as compared to Johnny, which usually gives away more than 20. The fact we give away so few Tommy accounts is one of the primary reasons that server is fast. All servers give away at least 1 account per day unless otherwise announced. Tommy gives the least, Johnny gives the most. Ricky is in the middle, but is much closer to Tommy than Johnny. Also, note that even when full for the day, donors will still receive and can use their account invites (the invites ignore the daily limits).

Tommy currently fills in 1-2 seconds, so it's basically a lottery as to who gets it. You basically have to get to the server selection screen and mash F5 at midnight UTC hoping you're the one who sees it open. An account can be moved directly to tommy (as opposed to deletion and trying to sign up for free) but that service requires you be a donor.

It's for failed IMAP logins...you have a mail client misconfigured somewhere. Unblocked.

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

The username is actually r910dev. Unarchiving...

Real time? Not really, though it can usually be had to within a few minutes. The load images in Luigi's signature are the closest you'll get to real time. Historical information is available here: http://heliohost.grd.net.pl/monitor/ Data is usually current to within the hour, but sometimes falls a little behind. We don't run this monitor service, it's provided for free by one of our users Piotr GRD. As for speed, yeah, johnny sucks when load is up. Minutes for an empty page is normal during periods of load, and if you actually installed software a 500 error should be expected due to php's process timing out. Johnny exists for those who want to play around with a piece of software, test their code, etc. and is not meant for production websites. Tommy is a much better choice if you need an account with good up time.

Yep high load. This is exactly why we don't recommend converting videos here, it gets users suspended pretty much every time. Unsuspended.

I believe it's 3 on Johnny and Ricky at the moment. Tommy has no limit (though this is subject to change if abused).

Unblocked. Our logs don't specify why the SMTP logins failed, just that they did, so we have no way of knowing which mailbox or device is causing it.

Krydos is the one to install these...

We can ask Krydos, but in my opinion that's well into VPS territory. What are you doing that needs that much anyway (if it's running XF or WP, they're known memory hogs and the answer is to find different software)? To give you an idea, the server has 16GB of RAM and ~1300 accounts. You're asking for 1/32 of the entire server's worth of RAM, when it needs to be shared by 1300 people. While the memory is often free now, it can't be raised for a single person. If everyone starts using it, the server will promptly run out of memory.

Glad to see you got it working. Post removed at user request. It's one person, not one IP. You can have as many IP addresses as you want, you're still only allowed one account. If we see two accounts for a single person and you claim there's more than one person, we ask for government ID to prove there's two people. The reason for this policy is because people used to create two accounts to evade the disk space limit. A single person is only allowed 1GB for free, and can buy 1GB extra for $5 (one time fee). No account can have more than 2GB. 1. Yes. You can be the busiest site in the world, and you'll still need to log in. If you're a donor, we can waive this requirement at a rate of $1 per month waived. We prefer it over time as a recurring donation, but can also accept the entire donation up front as a lump sum. We require the logins or donations as a way to keep abandoned accounts from piling up and wasting resources. A site's traffic is not a good indication of an account being used since abandoned websites still often see tons of bot traffic. 2. Excessive CPU and RAM usage. I answered this question here: https://www.helionet.org/index/topic/38856-how-does-the-suspend-account-script-work/ In cPanel, there's an option for "Account Load" that shows you where you stand. Keep those bars as low as possible and you're good If you're up around 100, you're likely to be suspended if the server load spikes.

You should be good now.