i just installed freepbx 12 on ubuntu 14.04.
i tried to install freepbx 13 on ubuntu 16.04 and centos 7, but idk why, the installation will always fail in the end with “cannot connect with asterisk” or something like that.
now that i have it running i got to a new issue, when i try to apply the config to add the extensions, i get this error:
Reload failed because retrieve_conf encountered an error: 126
Is there a reason you decide to start with the “expert” install instead of using the SNG7 based Distribution? It handles all of these problems and gets you a working system at the outset.
To answer your question, try running “fwconsole chown” at the system console and see if that helps.
OK - makes sense. Which VPS are you using? Lots of people have had lots of success installing the FreePBX distro on various platforms.
If you can give us more information, I’m sure someone would be willing to help you get this working. BTW - did you check the FreePBX Wiki pages? There is lots of information out there, including several sections that talk to ‘bare metal’ installs
The minimum comfortable system requirements for the system are 4G RAM and 120G of disk space. While you seem very committed to this installation, I would still highly recommend getting onto a platform that is better suited to running a PBX. SIPStation (a division of Sangoma) comes to mind. If you look back through the forums, you’ll see lots of people with lots of PBX experience running into problems.
Let’s be clear on something. FreePBX 12 has been EOL for over three years now. It is completely unsupported not the mention this is a manual install. So we have no idea what has actually been done by you and how it was done.
In fact at this point Distro 6 (what FreePBX 13) was built on is also EOL. FreePBX 13 has support left too it but even then FreePBX 14 is the current release with 15 down the pipe in the next 3-6 months.
If you’re going to install a new PBX try using the current software release and not software that even the vendor is going to say “Its unsupported, we can’t help”
i have an update,
i left vpscheap and i moved to digital ocean, i have successfully installed FreePBX 14.0.3.13, now i have a new problem, port 5060 is not open, i can see that its there with netstat -na |grep 5060
udp 0 0 0.0.0.0:5060 0.0.0.0:*
but when i use nmap localhost it shows me this:
Starting Nmap 6.47 ( http://nmap.org ) at 2018-10-20 23:04 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000060s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open rpcbind
3306/tcp open mysql
Nmap done: 1 IP address (1 host up) scanned in 1.68 seconds
Because nmap is TCP by default, you have to tell it to scan UDP. At this point since you’re jumping around host companies and you clearly are out of your depth with doing a manual install. Go to some place like vultr.com where the FreePBX Distro actually can be installed and is part of their ISO library.