Hi,
I’ve been having issues installing a freepbx 17 instance from script.
I’m attempting the install on a VPS with a public IP4. I first install debian 12.12 net install through VNC, followed by running the script. All goes well and the script finishes.
When i access the web interface, I am prompted to create an admin and activate.
The issue seems to be the firewall - I go through the tutorial, whitelist my home IP, enable responsive firewall, but at the last step when I’m asked to enable firewall, i lose connection and am unable to connect again, either through http or ssh.
When i reboot and login through my provider web VNC i noticed that the terminal info states the mac address but no ip address.
I’ve tried reinstalling a couple of times, always with the same problem. In the end, I didn’t enable the firewall at the end of the initial setup, so I was able to finally access the server.
Now, when I go to Network Settings under System Admin, it lists the netmask as 24. As this is a public-facing VPS, I would like to change it to 32, but when i save interface, it reverts back to 24?
How can i restrict the network to my individual IP?
Thanks in advance for your help
I am unsure about the whole firewall thing, I’d try fwconsole firewall trust yourhomeip.
As for the network settings, your subnet mask can’t be /32, because it has to have a default gateway to be able to get out to the internet.
thank you for the reply.
I’ve allowed my ip through the firewall.
After rebooting I’m again unable to connect to the server through http or ssh.
I’ve disabled the firewall with fwconsole firewall disable and still can’t access the server. When i log in through VNC, the server has no IPs listed, only mac address.
The ens3 interface appeared to be down so i raised it with ip link set ens3 up and restarted networking but still has no IP attached.
The file at /etc/network/interfaces seems to be correctly formated.
How can I reconfigure network?
Ok, so the file /etc/network/interfaces was not correctly formatted after all.
It seems the process of enabling the firewall replaces the originally well configured file with an incorrect formatted version:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
address 123.456.789.112
netmask 255.255.255.0
gateway 123.456.789.1
So I had to amend it to the correct format:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto ens3
iface ens3 inet static
ddress 123.456.789.112
netmask 255.255.255.0
gateway 123.456.789.1
I’ve regained access to the server now!
Thank you for your help @Eris
Glad to hear you got it working! Personally I haven’t used the sysadmin network config section since the move to Debian. I’m not sure if the FreePBX team have that working with Debian. Maybe someone else has had a different experience and can comment.
Which VPS ?
Does your VPS provider offer a Debian 12 image ?
Assuming that is a typo missing the “a” in the front of “ddress” ?
Yes, FreePBX managed networking via sysadmin very much works on Debian; however, there are many other things that can compete with the configuration file generation e.g. systemd, cloud-init, entries in the /etc/network/interfaces.d/ directory, VPS provider customizations, etc.
Hi @penguinpbx, thank you for your reply.
Just a VPS I rent from a provider. I had an instance of Freepbx previously there that was working fine, but a recent apt update knocked the all system offline and I decided to reinstall.
It does, but it also offers the possibility to upload an .iso image, so I just downloaded the latest official Debian net install and ran the Debian setup through VNC as per the tutorial on the website. I just had to setup the network manually.
Yes, copy & paste typo, sorry for that!
I’ve tried installing a couple of times, and I always had the same error of losing connection after going through the firewall tutorial and answering “yes” to the last question about configuring the network. In the end, I noticed that the system had automatically changed the /etc/network/interfaces from the original file with a wrongly configured version that wasn’t allowing the ens3 interface to start. I know the file was changed because after the install, I had to amend it to start networking (the file had listed an eth0 interface when it should have been ens3)
Got it working in the end after amending the /etc/network/interfaces file.
That isn’t right! There is an a in address.
Yes, sorry, it was a typo due to copy paste. I am unable to edit that post to correct it.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.