Hi everyone!
I have a FreeNAS server in an office 2 hours away. I'm trying to not go up there unless there's other servers in the office besides the FreeNAS that need attention, so that I'm not driving 4 hours just to do a bit of maintenance.
I can access it no problem. I have a VPN to the network, and can access pretty much anything there, including the FreeNAS machine via SSH from inside the VPN.
My issue is this: when I make configuration changes while remoted in via SSH, they don't stick. This is the message, which I'm sure you all know very well:
"Warning: settings changed through the CLI are not written to the configuration database and will be reset on reboot."
Even as root, I have to either use the web access GUI or be there physically? Seems silly. Surely there's a way around this?
I have a FreeNAS server in an office 2 hours away. I'm trying to not go up there unless there's other servers in the office besides the FreeNAS that need attention, so that I'm not driving 4 hours just to do a bit of maintenance.
I can access it no problem. I have a VPN to the network, and can access pretty much anything there, including the FreeNAS machine via SSH from inside the VPN.
My issue is this: when I make configuration changes while remoted in via SSH, they don't stick. This is the message, which I'm sure you all know very well:
"Warning: settings changed through the CLI are not written to the configuration database and will be reset on reboot."
Even as root, I have to either use the web access GUI or be there physically? Seems silly. Surely there's a way around this?