When something is wrong
Start here:
blysis logs
blysis status
The log is the application's own, not the web server's, and a failure almost
always names itself in it. status says what is running and since when, which
answers "did it restart" faster than anything else.
The site is serving an old version
A rebuild failed. The previous build keeps being served on purpose, so this is the platform working rather than the platform broken. The log names the module that would not compile. Disable it from the admin panel and the next build leaves it out.
A module installed but its screens are not there
Almost always one of two things.
The module is installed but not enabled. Installed and enabled are separate states, and a module that is installed and disabled is invisible everywhere by design. Admin, then Modules.
The build has not finished. Installing rebuilds and restarts. Give it a minute, then check the log.
Everything is in English for a Turkish reader, or strings look like keys
A screen showing forum.topics.title instead of a sentence means the
translation table does not have that key yet. Translations are synced when a
module is installed and when a theme is activated. Reinstalling the module or
re-running the seed fixes it, and the admin's own edits survive both.
Sign-in works, then the session is gone
Check the site URL in Settings, then Site Config. A cookie is issued for the host in that setting; if it does not match the host in the address bar, the browser keeps the cookie and never sends it back.
Payments never confirm
A gateway confirms a payment by calling back, so the callback has to reach the site from the internet. Check that the site URL is the public one, that the gateway's dashboard has the callback address the module's settings page shows, and that the webhook log in the admin panel is receiving anything at all.
Rate limiting refuses everything, or nothing
In production the rate limiter needs Redis and fails closed without it: no
Redis means refusals rather than a silently open door. blysis status shows
whether Redis is up.
Nothing above
Bring the last fifty lines of blysis logs, the output of blysis status, and
what you did before it started. Those three answer most questions before anyone
has to ask them.