Free Flarum hosting on an expert platform by FreeFlarum.com
New forum registration is bugged - the reason for that is that Nginx is using the 7.2 FPM file version globally - I will need to bulk rename all socks to a more general format (such as php.x.sock instead of php-7.4.x.sock), so expect another downtimes.
We have faith in you 
Forum creation now works again too 
Update done
Thank you for your patience and sorry for downtime
lakshya Discord: Kevo#7590 or by E-mail: kevo@kevo.link
arteteco
I've tested on several forums and none of them work. So it is not just for your forum.
Confirmed. We have 502 on our end as well.
PHP-FPM crashed, had to restart it, not sure why. I'll have to investigate it. The forums should be back up
lakshya If the problem already happened, enter https://community.myandro.in/all
SKevo Thanks for awesome work. Forums were up and then again 502 gateway error is seen.
Same Bad Gateway prob with the Free Form @https://playitloud.flarum.cloud/
Help would be awesome Ty
Freeflarum crash during registration =/
Forums are back up. Same issue. Because those crashes happened while I was sleeping, I couldn't assist (sorry). This morning I will try to fix it.
- Edited
I've added 2 new features to the main page:
- Checker whether our base (skeleton) forum is reachable. Puts a banner indicating that something went wrong if it's not (eg: 502 error, etc...)
- Live checker for forum name availability - handles also name length and whether or not it's on the forbidden name list.
Everything is done client-side by using JavaScript. I have implemented this in the darkness of the recent crashes with the intention to help people who are registering their forum, and why it might be down afterwards or why the registration might fail, where should they look for support or check for news (this thread) etc...
I've also tweaked the PHP-FPM failure, and I tested forum creation and forum renaming (both work fine), and also the reload (which caused issue). If it happens again, I'll try to fix it for good. But so far, no issues (except for some small 20 second forum downtimes, which were intentional because I was testing if the new features work 
)
Edit: The 502 error seems to be temporary when renaming a forum now. I might consider to just remove the function and accept "rename requests" through this thread or E-mail, as it just causes issues now.
Edit 2: As can be seen at https://freeflarum.com/status, PHP-FPM uses over 80% of open files. We have too many forums using it. I am going to clean up all inactive ones now (the ones that have no posts, visitors or activity in 3 months) until we figure out what to do with it. There wasn't bigger cleanup in a long time anyways.
If your forum got removed, message us and we'll restore it.
In this page https://www.freeflarum.com/status it says everything is fine.
But my forum https://mazowieckie.flarum.cloud/ is not working. Maybe I should be patient, but maybe I should contact you. I didn't get it. In case I am contacting you Thanks!
legionmaster aware of it, working on a fix.
- Edited
After 30 minutes of fast-scripting and creating code that you couldn't look at, I have fixed it and found the cause: it seems that the new PHP-FPM is very aggressive on configs and what sites exist and what don't. So, if there happens to be a config for a site folder that doesn't exist, it tears down entire FreeFlarum. Before, it wasn't a big deal, but now it is critical. We will have to update our scripts to delete every config and sock that doesn't need to exist anymore.
In this specific case, our inactive forum remover didn't remove the configs for sites, so I had to quickly bash Python script to iterate over all dead configs and remove them completely. Oof.
One positive thing: open files usage dropped to 66% after the cleanup...
I have (hopefully) put a temporary fix to one of our scripts that handle forum removals.
Because of this, forum reactivation is temporary paused too, unless it's urgent.
- Edited
I have finished the forum cleanup anyways in the end. Open files usage dropped to 62 %, so I increased the error report limit to > 80 %. https://freeflarum.com/status should no longer report any errors.
The crash is now gone, hasn't happened anymore which is great! Sorry for the recent downtimes, but it is difficult to update over 3 000 forums with no issues - even more difficult is fixing them.
As for forum reactivation (in case yours got taken down in the cleanup), it is still not allowed until further notice. I will try to fix the code for that today so it works again.
lakshya I want my forum to exist on both.
Flarum doesn't really support this. But moreover, why would you want to do this? You'd just be diluting your SEO. www is outdated, and shouldn't be used.