FreePBX appliance 300 locked out!

Remote client got a FreePBX appliance 300 (at my recommendation) about 2 weeks ago. Password was set when unit first turned on but since I was unfamiliar with the new firewall I left it disabled. I then noticed I couldn’t get into the command line via putty, thinking it might be a special character I changed the password. So far so good with the web interface and the password change but I still couldn’t access the command line.

After a little research I decided I wanted to check out the firewall so I enabled it. This machine is now dead in the water. The only thing I see is in the web interface now is the buttons FreePBX Support, Dashboard, ISymphonyV3 Panel, and UCP. There is also an error now under Firewall Configuration about Trusted Interface Detected. I then decided to go ahead and get the Serial to USB cable up to bypass the firewall.

At this point I can connect but cannot authenticate to the command line, both TCP and Serial continually prompts me for password even though I am using the same password to log into the Web interface. I have also tried the original password (w/ possible bad characters) but that is not working also.

This unit did come with a USB key. I have not physically seen or installed these units before but I am thinking it’s time to start over. Are there any instructions on how to do remote reload with this unit?

Any suggestions about how to fix the issues?

Your GUI username and password have nothing to do with the root login of Linux CLI.

That login is root as the username and the password we set is sangoma.

If you changes this and not sure what you set it to google Linux Single User mode on how to boot linux into single user mode to reset the password

Thank you, Tony. I thought the root password was set at the same time when the initial password is set. I have connected to the linux CLI and then Asterisk via Serial connection.

I still have only the 4 buttons on the web interface though, even after completely dropping the firewall(s). I am wondering if there is any documentation on this hardware, but more specifically I am wondering about the ports. Is eth0 a WAN or LAN port?

Their is no such thing as wan or lan. Its whatever you setup the connection to be. This is not a router where you would have a lan and a wan.

As far as 4 buttons you need to login. Click on the admin button and login.

Thank you for the information Tony.

What is the purpose of the Green eth0 port? Why is it treated differently?

I do understand that it’s up to the user to setup this device but lacking proper documentation one must ‘guess’ at the intended function. Is there no actual documentation for this appliance?? Are there plans to produce? TBH, without documentation I feel one would be better off purchasing off the shelf server components (w/ proper documentation) and building FreePBX the ‘old fashion’ way. Not trying to be a nay-sayer here, just trying to give feedback as an end admin.

What documentation are you looking for? Its just a piece of hardware that you plug in like a dell server. I dont get documentation on how to plug in cords into my Dell Server when I buy them.

Plug in the power and hookup up to eht0 and connect the console port. Their is a wiki on this

Also with the system should of been a quick start guide telling you how to access the server and directing you to the wiki from their.

Not exactly the answer I would expect but thanks for the information. Just a rhetorical question but do you really think that each and every Dell server doesn’t have a small library of documentation?

Having said that, I do also appreciate the fact that Dell doesn’t have one of the top devs trying to help people out on the forum. One of the (many) reasons I think FreePBX is awesome!

I am 1500 miles away from this unit. It’s an unknown item to me but I have so much faith in the Sangoma and FreePBX team that I had my client just order one; shipped to site. Normally I would just built something up here and sent it out, but now I am really hoping I didn’t make a mistake here.

Currently I there is an ethernet cord from single green port to switch. ifconfig says this port is eth4 not eth0. No other ports will light up when ethernet cable is plugged into them.

I still cannot access anything on the admin panel but the 4 buttons I mentioned in an earlier post (and yes, I am logged in to the admin panel not just welcome page). I see the module upgrade message on Dashboard so I click Resolve button to bring up Module page and I get Module Not Found in big bold letters, “We are unable to find any information on the module you are looking for.” is below that and nothing else. Even if I try to access a known URL (ie. /admin/config.php?display=extensions) I get Module Not Found.

Do you think if I renamed eth4 to eth0 the GUI issue would be resolved or do you think it might be deeper than that? This is still a brand new setup so perhaps a wipe/reload would be the best approach, just start fresh. However I don’t know of any documentation to do that…

If you are getting tona GUI their is nothing wrong with the Ethernet port. Something bigger is happening.

Can you open a ticket with us with your login information for SSH and we will see what’s going on. Https:// under the RMA section

1 Like

It appears like the machine was in the middle of an upgrade and it was rebooted/turned off. This means that a bunch of modules are in the middle of getting upgraded.

If you go to display=modules you’ll be able to manually re-enable and re-install all the modules.

This took FOREVER to get back to a fresh install. To save someone in the future having to pull their hair out here are the instructions for wiping and reloading a FreePBX appliance via included USB drive and Console Cable.

  1. Connect console cable and verify access to appliance
  2. Insert USB into Appliance
  3. Issue reboot command via SSH
  4. Get into BIOS by pressing delete during HW boot
  5. On boot tab select USB device under Override boot

Support was couldn’t resolve the issues I was having. I was asked to create a new case moving it to a Configuration from Hardware request. Basically, there was going a big chance I was going to have to pay to have this fixed.

After reloading this unit I went through the initial install steps again but this time there was about 6 pages of firewall setup. I only remember seeing 1 or 2 previously so perhaps something did go horribly wrong that was out of my control. Oh well, lessons learned and moving on.