- Edited
Hello, 7 days ago my website simply became inaccessible, without changing or installing any plugin. Can you help me understand (can you request any file and where can I find it?)??
forum.poptime.space
Hello, 7 days ago my website simply became inaccessible, without changing or installing any plugin. Can you help me understand (can you request any file and where can I find it?)??
forum.poptime.space
Nobody can help you with none message.
I have the installation and the error has never occurred. I am a beginner in this. So I don't know what to provide you. But whatever is necessary, ask for it and I will give it!
see: forum.poptime.space
danewolfs you can follow the https://docs.flarum.org/troubleshoot guide to identify the underlying problem.
luceos I already followed this and everything was white like in the link I sent
danewolfs the third step talks about collecting logs, see https://docs.flarum.org/troubleshoot/#step-3-collect-information
You can check your hosting environment for logs, either from storage/logs
in the Flarum directory or from the webserver error logs. You can also opt to enable debug as per first option: https://docs.flarum.org/troubleshoot/#step-0-activate-debug-mode
Seeing you're using cloudflare, maybe enable developer mode temporarily to disable their proxy, as well.
danewolfs so there is nothing in <flarum>/storage/logs
?
What kind of hosting is this? Is it a managed hosting or VPS? Does your hosting provider offer a way to contact support?
From the logs you provided, there seems to be some errors in the webserver configuration.
One error you could start with is /home/poptime/public_html/forum.poptime.space/.htaccess: RewriteRule: bad flag delimiters
. Have you modified this file? You can see what the original file is supposed to look like here flarum/flarumblob/v1.8.1/public/.htaccess
The errors like MaxRequestWorkers of 2048 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 2025
are probably irrelevant, there seems to be invalid configuration values but they get automatically adjusted. What these messages indicate however is that the webserver seems to be restarting.
The reason for the restart are probably the messages Cannot serve directory /home/supermagicaibras/public_html/: No matching
and AH01071: Got error 'Primary script unknown'
. I'm not familiar with the syntax of those logs, is that Apache, with a PHP CGI handler? You would have to check your host/VirtualHost configuration for the respective website.
If you are hosting other websites on the same server, it's also possible the configuration of those other websites is breaking the configuration for the forum site. The error messages seem to reference your forum hostname so the problem is probably there, or for the website that's just before or after it in your list of website as a missing delimiter in the previous site config could affect the one after.
clarkwinkelmann on the storage/logs thats the last log recorded (19/12) https://docs.google.com/document/d/15WHrUNropNu153vkaB6Q8bf_919Lx7KcBJ9R4MIbYIE/edit?usp=sharing
i use vps on contabo and i dont change nothing, anithyng has working until now...
i've suspend my other site and the error still
luceos so should i disable it to fix the problem on forum.poptime.space website?
luceos I just disabled it and it continues to do the same thing. I don't know what to do anymore since I've already worked on everything I had in the logs that I have that mention the domain with an error. The last log I have in the logs folder is from December, I don't know why it doesn't create new ones and the site doesn't open. It just leaves a blank page. Other sites on the VPS are 100% normal.
If there is a problem with the webserver configuration, then it's expected that there is no Flarum log file, as Flarum is never reached at all.
Have you been able to check the .htaccess
?
We don't have enough information to help further. If you want to continue troubleshooting with us on the forum, we'll need to see more. Your Apache configuration, your .htaccess
, etc.
It would also be useful if you could take a snapshot of the Apache error log, try accessing the site, and take note of which new lines appeared, and share just those new lines. That way we can isolate any error that might be irrelevant.
Also consider restarting Apache over the command line, you might see Apache start errors.
Server was hacked. Index file was doing something else entirely.