a FreePBX running well since 2020
after a hardware failure:
pc replaced with absolutely the same model
old disk inserted in the new pc
freepbx restarts but is extremely slow
phones are connected but the trunk is down
I can connect to the GUI
it asks me to reactivate the software but it cannot complete the activation
I cannot access the CLI with the same credentials, neither via ssh nor interactively with keyboard and monitor
hi franckdanard,
but do you know why I can no longer login via ssh or locally with keyboard/monitor using the usual credentials?
I would like to check that the network/DNS are configured correctly but without access to the system and without activating the GUI, I think I can’t do it…
ok, I reset the root password.
but excuse me if I insist: why have I always had CLI access and at a certain point no more, has some update changed something?
now I’m looking for something in the wiki about reactivation in case of hardware replacement…
if I really can’t, I’ll follow the advice of franckdanard
ok, problem solved.
with the network configured correctly I was able to update the modules.
then I tried an activation from scratch from the GUI, I used the same credentials as then, the procedure detected the machine already activated previously and re-activated it without problems