Even from the console? If it’s just blocked from SSH, that’s the default. You could edit
/etc/ssh/sshd_config
to permit root login, but it’s more convenient and secure to set up public key authentication.
I didn’t try from console, I can try that then. My concern is that the size of the volume for my system is only 50G out of the box. From running lsblk I can see the RAID 1 was created but I want to confirm I can change the size of the actual install for the server.
The FPBX v17 ISO design makes some decisions about disk partitioning, root access, network device names, and more.
What is the output of df -h ?
And the LVM associated commands (pv/vg/lvdisplay) should help you determine what can be resized.
Root login works on console, I allowed root login but now I can’t SSH into the server at all. I looked through the settings there and I confirmed PermitTTY is set to yes and Password Authentication is set to yes as well. I restarted asterisk but no dice.
@penguinpbx Here is what I got from running df -h
668G for call recordings and voicemails – is that enough ?
Yeah I didn’t quite notice that, I think that should be good.
As for SSH access, any ideas as to why I couldn’t get connected to the server via ssh now?
Per SSH, well, the adaptive FreePBX firewall can be pretty intense so if you failed to connect a few times, the door gets closed because that looks like an attack. Workarounds include specifically allowing your IP via fwconsole on the CLI, rebooting and connecting right away and then punching open the holes, or KVM if SSH’ing as the sangoma user isn’t working, etc.
I was able to check the fail2ban list for sshd and there is nothing listed. I also checked standard fail2ban and the same, this was done over CLI on the system. I didn’t have the firewall enabled initially. Oddly enough, my coworker can get to the system with a different pc and ip. I’m able to get to the GUI but not ssh on my machine. Any other ideas?
Sorry to bug, any thoughts on my most recent reply?
When you attempt to SSH in, does it hang for a long time and then respond with “Operation timed out”? If so, and you are connecting to the correct IP and port, it is being blocked by FreePBX firewall, fail2ban, or another software firewall running on the PBX. Do
iptables -vL
on the PBX to start troubleshooting. If you get a different error from SSH, post that.