I got a freepbx 17 vm running on hyperv and was able to get into it fine. After restoring from freepbx 16 backup, I can now longer access it. I originally got a 403 forbidden on port 80. I can ssh into it until the firewall enables after 5 minutes, then lose my ssh connection. I ran a port scan on it and there are no web ports open. What does it take to get this running?
Is the IP that you are SSH’ing from loaded into your Trust zone ?
For example:
$ fwconsole firewall add trusted 192.0.2.14
Then to review it:
$ fwconsole firewall list trusted
1 Like
I got my ip address added after a restart and I can ssh into it now, but I get a 403 Forbidden on the gui on http port. And after 5 minutes I lose my ssh connection 
I disabled fail2ban and Found out the restore had a redirect in the apache file at /etc/apache2/sites-enabled/sangoma.conf and the ip address was redirecting to the fqdn which had not been cut over to the new pbx since it wasn’t ready for production yet. Removed the #### Force / Redirect acp to HTTPS ####
RewriteRule ^/(.)
lines and saved the file was able to access the pbx and finish setup.
1 Like
Nice. Temporarily stopping fail2ban can help in testing and development, but, of course, for production it is not advisable.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.