What goes wrong most often, what it actually means, and what to do about it. Most of these are configuration or another resource getting in the way, not faults — and /weatherinfo prints exactly what a client believes. Run it before opening a ticket.
Installation and Access#
"Could not use the qs_weather_… table" in the console
sql/database.sql was not imported, or was imported into a different database from the one oxmysql connects to. Import it into the right one and restart. Until then nothing is saved: zones, settings, the weather and the clock all reset on every restart.
"You do not have permission" on /weather, /weathercreator or /weatherconfig
Read the server console: it prints the exact add_ace line that would let that player in. Nine times out of ten the line is in but the server was not restarted, or the player is not in . On QBCore and Qbox use the ACE lines; only ESX groups are recognised on their own. Each panel has its own node, so having one does not open the other two.