Categories

• Blogs

  Posts from individual members

  0
  Topics
  0
  Posts
  No new posts.
• Guides & Walkthroughs

  Guides and walkthoughs created by our team members

  3
  Topics
  3
  Posts

  

  If your IT department is doing things right, then the user account that you log in to a computer with will not have administrative access.

  In the Linux ecosystem this is called sudo access.

  Normally an accout is made with sudo rights that is only used as needed.

  If the password for this account is lost, then there is no longer a way to administer the computer.

  In the Windows world, you shutdown the system and then boot to a specially crafted USB boot disk that you can read the Windows information and then reset the admin password.

  For Linux, it is easier. You simply need to reboot and interrupt the normal grub boot sequence to get into single user mode.

  Reboot the system. As soon as it powers back on begin tapping the ESC key.
  Technically, we are only wanting to stop grub from automatically booting. but with modern SSD or NVMe drives, this can go by so fast you never knew it was available to interrupt. The first grub entry should be highlighted by default and is normally the one you want. Press e to edit that entry. Find the line beginning with linux Go to the end of the line and add init=/bin/bash Press F10 to boot to this modified file without permanently saving it. The system will boot to a command prompt similar to root@(none):/# Enter mount -o remount,rw / and press Enter. Now you can reset the admin account password with the passwd command: passwd YOURADMINNAME. Enter the new password, then again to confirm it. Type exit and then use the power button to reboot the computer.
• FreePBX Guides, Hints, and Tricks

  Guides specific to FreePBX

  14
  Topics
  14
  Posts

  

  Always do this upgrade via the command line over SSH. This prevents HTTP/PHP timeouts from affecting you. You can use the console if you want, but SSH is normal.

  Login with your non-root user. Because you never allow root to log in over ssh right? Update the system sudo yum upgrade -y Upgrade the current modules. sudo fwconsole ma upgradeall Fix permissions, as module upgrades can leave some files owned by root. sudo fwconsole chown Reload the system to rewrite the config files. sudo fwconsole reload Reboot, to make sure everything in in a pristine state, or at least should be. sudo reboot Log back in and then switch to root. If you run the versionupgrade with sudo instead of as root, it fails to properly do everything, even though it says the upgrade succeeds. sudo su - Download the versionupgrade module fwconsole ma downloadinstall versionupgrade Fix permissions again as it messes up file permissions in /var/www/html after you install it. fwconsole chown Reload fwconsole reload Run the version upgrade check fwconsole versionupgrade --check If you have an error about a deprecated module remove them and them reload.
  756b5fb2-09a8-4cf8-aa4e-e67862552e6e-image.png fwconsole ma delete campon fwconsle reload Then run the version check again. It should be clean, so upgrade. fwconsole versionupgrade --upgrade Log back into the web interface Make sure everything looks normal Make a couple test calls, in, out, internal, etc. Once everything looks good, hop back to your SSH session and reboot. Sure everything is runing now, but how do you know it will reboot correctly if you don't try it now? reboot Assuming everything come sup normally, you are done. The most common thing I find here is that I sometimes need to run fwconsole restart before the GUI shows a connection to Asterisk, even though everything is running.