Can't Access GUI after Reboot

I’m a new user. Installing FreePBX 17 on bare metal with Debian 12. After initial install, I ran the setup wizard and started setting things up. But decided to reboot as a verification – I usually do that on new installs. But after the reboot, I couldn’t access the GUI. The machine is fine, including SSH. Disappointed, I rebuilt the whole machine down to the OS. Same thing happened again. Now I’ve learned that if I run the install script again, I regain access and everything looks fine, but only until I reboot again. Did I miss a step somewhere? Thanks in advance for any assistance here!

Does the web UI page itself is not opening or you are getting any whoops error? if page itself not loading then check your network/firewall settings.

Thanks, It can’t be a network or firewall issue since I was able to access the GUI after install but not after a reboot. Then again after a re-install access returns. This has something to do with FreePBX itself.

I’ve had this issue on FreePBX 17 as well. What I’ve found happens is that the apache2 service doesn’t start after a reboot. In the CLI, run service apache2 start and you should get your web UI back.

There seems to be some issues with services not starting on a reboot, specifically Apache and Asterisk. There have been some GitHub commits recently about it I think.

there is a ouroboros in the systemd service files that Sangoma provide but need to fix, they have known about it for a while without fixing it yet, I guess you will have to wait . . . ( or roll your sleeves up and edit the .service files yourself :slight_smile: )

This was the problem. I never considered Apache being the problem restarting – it’s been used in servers for as long as I can remember! But, it’s happening! Thanks.

No problem! I’m sorry you had to go through the trouble of reinstalling the entirety of FreePBX instead of just running the command :frowning:

Please mark my reply as the solution to help other community members find the fix

Consider that a work-around rather than a fix, one fix is edit the .service files to not have apache2 rely on freepbx or vice-versa

1 Like