OK. If you’re running the bot on a VPS, I presume it’s running as a service? If so,
cd into the directory it sits in then use
./launch.sh to get the bot running with the console.
Give it time to start, then check the panel again. Type
offlinetest to cheat the bot into thinking you’re offline. Just to make sure, use
offlinetest again to give it a good kicking, before shutting down the bot and restarting as a service.
Hopefully this will reset it enough to pick up your real status properly. Note that the
onlinetest will trigger Discord and Twitter alerts if you have them set up.