PlanetCloud

Since the reason for suspension comes in many shapes and sizes, I believe I shouldn't add a specific handler for each. Just onAccountSuspended is enough. For the reason, it is recommended that it is logged/saved to database along with the account. Sometimes the same reason for example "Disposable email" comes in the following format: DISPOSABLE_EMAIL and "disposable email protonmail.com". Would be hellish to code for each scenario.

Added new features: Before and after callback middlewares. Should help with logging.

Saying that "every" free web hosting provider should have the features said above is a bit too much... A "Good" Free Web Hosting Provider should have those but not every one of them should. Many MOFH users are just people who are new to web development who can't even make their own systems yet, and we're not trying to shunt them down by saying "Hey you don't have this and that! Every host should have it". We welcome those who wants to experiment with things here, as that's how I manage to learn a lot of things, just by playing around with the things here and I hope many new developers can be empowered by the features provided by iFastNet. Not everyone can afford Site.Pro integration (or implement it), not everyone can draw a mascot/pay someone to do so, etc. etc. My point is that: Every hosting here should have the following features that has been provided by iFastNet from the start: A website indicating that this is a free hosting, signup form for the hosting, cPanel Link/Login link An active email that is monitored to receive complaints and support customers Those are the most barebone minimum what every hosting here should have. For advanced ones, they should have the following features: A non-free company domain, so you won't get locked out of your hosting when Freenom decided they will take over your domain and charge a premium for it because it has gained a lot of interesting traffic, and to look more professional. Advertisements placed on cPanel or website to help recoup the cost of the domain so you don't need to shut down after only a year or so. and lastly, for Professional ones who truly wants to invest time and money into this, should have (some or all) of the features mentioned by @TinkerMan above as it is truly nice touch to the Free Hosting business. IMPORTANT NOTE: All of those "features" are utterly useless if the company went under, lack management or support. This business is not something you can just setup and leave. You need to invest time and money into it. Take a look at the most successful, long-standing MOFH powered hosting: InfinityFree. It's not the client area nor the Site.Pro builder that makes them successful. It's years of proven reliability and dedication by the owner, by that I mean it had existed for years without many major outages, there are ads and or systems in place to ensure revenue coming in to keep the business from going under. The company also uses Cloud Platforms to serve the main site and client area so that it is fast and responsive (and cost money too!). The company also provides great support with max 2 days response and community forum to help with other questions. It is reliability and great support that truly matters in the end as customers/clients wants a reliable hosting to their website and support if needed to. Edit: I consider reliability and great support as "features"

Received, thank you. I'll analyze it and make changes accordingly.

Sure you can

I would love to get that data and I believe it should be shared privately (because it contains usernames) or you can remove the usernames first and share it here. It would be very helpful indeed.

What does data.json contains?

Okay, what about the comments given? Does it include comments from previous suspension?

I noticed for the comments, if there are multiple suspension history, we'll receive it all like this: OTHER_CLOSE; REQUESTED OTHER_CLOSE; OTHER_CLOSE; NULLED_SCRIPT Is this always the case or only for manual intervention/suspension?

I've updated the code, take a look: https://github.com/PlanetTheCloud/mofh-callback-client

Oooo I see, I'll add this, thank you.

It is but why would you?

Hi, I've created a new library to handle Callbacks from MOFH Api. Here's the link: https://github.com/PlanetTheCloud/mofh-callback-client If there are callbacks that are missed, please let me know. Thank you.

Hi, can't help but wonder won't the second function overrides the first and is this automatically called?

Yes, but I dont think I should limit that or rely on another 3rd party. However Ill consider.

Yes I know this may be a good idea but this is outside the scope of this topic I believe as if we are just trying to secure the most "authoritative" subdomains so our clients won't get tricked/phished/scammed/anything bad. But I would keep that in mind and I think optionally we can block swear/slang words as well but that would be a very, very long list

I see, good idea. Maybe a script to register all these would also come in handy

Is it smart to just add these subdomains under the main reseller account?

Hmm, do we have to configure what to blacklist or is there a default list that are automatically blacklisted? If so, can you send the list here? Here's the current list: $reservedKeywords = ['support', 'help', 'api', 'app', 'system', 'admin', 'team', 'administration', 'mail', 'mailer', 'cpanel', 'control', 'auth', 'smtp', 'imap', 'webmail', 'signup', 'signin', 'vpanel', 'register', 'login', 'forum', 'panel', 'server', 'phpmyadmin', 'client', 'tutorials', 'tutorial', 'blog', 'staff', 'dash', 'status', 'dashboard', 'manage', 'server', 'root', 'client-area'];

Oh the minimum is 4? Ah.. looks like there are a lot of things I've forgotten about these. Thank you for reminding me and for your input. EDIT: Current list: $reservedKeywords = ['support', 'help', 'api', 'app', 'system', 'admin', 'team', 'administration', 'mail', 'mailer', 'cpanel', 'control', 'auth', 'smtp', 'imap', 'webmail', 'signup', 'signin', 'vpanel', 'register', 'login']; The 3 character ones are still included just in case..

Hi, when we allow users to signup with our subdomain, they can pick quite dangerous subdomains such as "support" or "admin". This may cause confusion and or be used as a weapon to attack other clients, making them think that they're actually the authority from the hosting provider. Such keywords should therefore be reserved. Question is... What other keywords should we reserve in order to protect business integrity and our clients? Here's what I got so far: support, help, api, app, system, admin, team, administration, mail, mailer, cpanel, control, auth *Note: I'm not trying to blacklist swear words

Understandable, no rush as well. Thank you for the great service

Oh is that so? Hmm this information may be useful...

So just to confirm, the only domain extension that will have a problem is the .tk extension?

PHP 7.4's Active Supports officially ends in 4 months. Would be nice to have PHP 8 support implemented. Thank you.