Changed IP, Unable to Connect FreePBX 17 Debian 12

General Help
1

I’ve install a new FreePBX instance on a Virtual Debian machine. Was able to restore an old backup and things work fine until I change the IP address of the server. Then get “Unable to Connect” when trying to access the webpage at the new address. Even using the console on the server and trying LocalHost it doesn’t connect. Changed the IP from the Debian Desktop from the original dynamic IP to a Static IP. Even when I changed the IP back to it’s original IP the website doesn’t connect.

The address I am changing to is the same subnet and gateway. Origional DHCP is 10.10.2.109 Changed to 10.10.2.181
I know the address is changing since I can SSH into the server at the new address.

I even reinstalled everything and then used the FreePBX Interface to change the IP. Still NOJoy.

What am I missing?

2

After changed PBX ip have you tride to use different Internet Browser ? maybe your browser keeps cash.

3

Even trying LocalHost from the console?? I tried refreshing the page and entering everything from scratch No Luck

4

what you mean Localhost ?
check 1st ping to new ip.
If is ping works the try at new browser http://192.168.xx.xx to login via IP address…

5

Ping works, SSH works Website No Workie

6

Maybe FW blocking you. Login via SSH to your PBX Box. In a Console write this command and then try again from Web GUI access.
fwconsole firewall disable

7

Assuming that the VM is using bridged networking, a reinstall gets the web interface running again, and there isn’t a conflict with the DHCP-assigned IP address, I recommend logging into your router/firewall and making the address static. Then, you don’t have to change anything in FreePBX or its OS.

However, it’s unusual for FreePBX to run in an OS with graphics (rather than a server version), so there may be some conflict there. Why did you choose an OS with a desktop?

8

Showing Firewall is not enabled.

9

Because I’m lazy. I’ll reinstall it on another VM without the Desktop and see how it works.

10 
systemctl set-default multi-user.target;reboot

will be quicker

systemctl set-default graphical;reboot

To get your GUI back, but modern hardware has no problems running a GUI on your VOIP server.

11

Looks like apache2 did not start.
Got a msg on startup like… ordering cycle found, skipping apache2
Once I restart apache2 the website comes back up. (localhost still doesn’t work but it does from the IP)

12

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.