I am running a current version of FreePBX and I have no web access to it at all. The web address times out and nothing is available for display. I can SSH into it just fine. I have a couple phones that are not connecting and I can’t log in to see why. I tried to reboot it and it goes down and comes back up properly. I can watch it do it’s thing on screen and can move around in the console but I am not strong in Linux stuff so have no idea what to dig through to see what might be in a log. User interface is gone as well. I do not have a recent backup that I can fall back to if I have to wipe this and start over.
Any way to back this machine up from SSH as it sits so I can mess around and not lose what little functionality I have if I have to completely reinstall?. I do not have another identical machine to do a hot swap with either. Also, is there any way to reinstall Apache or whatever is borking the WebUI? Having to rebuild this machine from scratch is going to put down a number of phone lines we need here since we have no cell service on the property.
Well folks, technology has once again laughed in my face. I have spent three weeks Googling, reading forums and trying to resolve this issue of no web interface and the day after posting, the stoopid things comes back to life. I have literally done nothing to the system itself, the network or either the PBX firewall or the network firewall to cause the problem nor have I done anything but surfing around in the terminal/console window to rectify it. It quit working one day for no reason and it must have known I reached out to get help because it is behaving again. I was able to get in and make a backup which I now have safely stored and I cloned the system just in case. This has been the most frustrating thing I have encountered in awhile and it’s probably more for my own lack of knowledge in it’s resolution. Thank you for your interest in assisting me… it was probably just your good intentions that scared it into submission
My guess (lacking any evidence otherwise) is that you had fail2ban set with default settings/timeouts, had your caplocks on or some other issue when you tried to login and exceeded the number of failed attempts allowed by fail2ban. That locked your IP out for the configured time period. Leave it alone for a few days and the lockout expired.
Actually, fail2ban is disabled. I have my PBX running on a server behind a PfSense firewall that only allows an outside connection directly from Voip.ms as my trunk provider so I turned off the firewall and fail2ban. Some would say that was stupid but I watched traffic for a number of months to see if anything was trying to get through and I had no issues with rogue traffic so I shut down the firewall and fail2ban. I thought that the issue might have been exactly that even though I thought I had killed those two setups so I did the reboot twice and tried again without the firewall up. No joy. I have upwards of 25 VM’s running within my network and I tried pulling the page up on about a dozen of them over a two week period and the page never loaded. Like timed out with no messages. Then all of a sudden it came back and I can load it on any of the VM’s I used to be able to. I know there was a reason, I am just at a total loss as to what it could have been. I could SSH in, I could move around in the file system, it said apache was up. I don’t know. I am however the king of weird shtuff when it comes to technology so… who knows. I will close this topic since it is kind of useless for anyone since nothing was really addressed. Thank you all for your responses.
