Hi,
I'm using the newest version of OPNsense, 24.1, running on a Proxmox VM, and overall, the experience has been smooth sailing. However, I've hit a roadblock while attempting to set up an LTE Stick from Huawei. I've been following the official documentation https://docs.opnsense.org/manual/how-tos/cellular.html (https://docs.opnsense.org/manual/how-tos/cellular.html), but I'm encountering difficulties right from step 1 due to console access issues.
Initially, I attempted to utilize the Proxmox console, but I kept receiving the error message "This account is currently not available." Even after enabling SSH connections, I encountered the same error. I've been trying to connect using the root account, assuming the settings were correctly configured.
Does anyone have insights into why I might be unable to access OPNsense via console? Alternatively, I'm open to suggestions for circumventing this issue or approaching step 1 of the LTE setup documentation differently.
Any assistance would be greatly appreciated!
That screenshot from the login is odd, how did you install OPNsense? Using the ISO attached to a new, empty VM you created in Proxmox and following the install instructions?
And connecting to the console using Proxmox, right-click on the VM >_ Console, then following should appear after OPNsense booted up:
*** OPNsense.somesome: OPNsense 24.1.2_1 ***
LAN (vtnet1) -> v4: 192.168.1.2/24
WAN (vtnet0) -> v4: 10.111.222.2/24
HTTPS: SHA256 <lots of digits>
<more digits>
SSH: SHA256 <snip> (ECDSA)
SSH: SHA256 <snip> (ED25519)
SSH: SHA256 <snip> (RSA)
FreeBSD/amd64 (OPNsense.somesome) (ttyu0)
login:
Did you make any changes to the root account ?
If you have a current copy of the configuration you could simply reinstall and restore the config
root user account is probably disabled (which is good practice). System > Access > users
Or, it might have a /nologin shell.
OP once there, you should create a new user, make it member or admins group and that will allow you to sudo when needed.
thx for all the answers :D
Quote from: cookiemonster on February 26, 2024, 12:49:10 AM
Or, it might have a /nologin shell.
Seems to be the problem. What should I choose instead?
for the root account is best to set to freebsd default /bin/csh on vanilla freebsd but for OPN, best to /usr/local/sbin/opnsense-shell . The OPN devs know best.
thank you, now everything works :D
very good. Remember if you can/want, to use your own separate user account instead of root and disable root. Make your user account member of wheel/admins and that account will have the same privileges but has a better chance of spotting a mistake before causing a problem i.e. needs to sudo which should prompt you to pause before running the command. Can always sudo -s for elevating for more than a few commands.