I dit run fwconsole on terminal,
reload [–json] [–dry-run] [–skip-registry-checks] [–dont-reload-asterisk]
But error stays.
The square brackets are meta characters, used in describing the syntax, and have been for more than 50 years (e.g. they are used for COBOL) language descriptions). If entered correctly --dry-run would prevent the command from having any real effect.
Did you install Debian 12+ and then use the FreePBX install script to install FreePBX 17?:
Or did you use the Beta ISO? (I imagine you used the install script from what I’m seeing, but just making sure). I have a script that tweaks a bunch of settings in Debian before I run the install the FreePBX install script, that seems to make the install go alot smoother. Let me know if you want me to share it. Not sure if it will help, but it may. I’ve had good success with it. I also find I have the best luck with RAW pure Debian 12+, command line only install.
Yes i did the complete img from Freepbx. it was an easy setup, burn .iso and put it in the nuc
But for the script from Github i must first install a (good version) of Debian linux?
Yes. You need to install Debian-12 first if you run the script above.
Are you typing fwconsole reload --verbose from the linux prompt? If you do, it should give an explanation why the reload does not work.
If the reload command does not work on your installation, go to module admin and see if there is a module in there that is either disabled or a module that isn’t compatible with FreePBX-17. Sometimes, you have to remove a bad module to get the reload to process.
If you did a downloadinstallall, (fwconsole ma downloadinstallall) you likely got some modules that you should not download and install. Like Synology, for example.
Yes if you use the FreePBX17 install script, you have to install a clean version of Debian 12+ first. I just find there’s a lot more control when I do that. I also find for the long run, there’s less that goes wrong with updates. That could just be my perception but I’ve had way better luck since I’ve moved to Freepbx 17, and I do the separate Debian install, and then I run the free PBX 17 install script. It just seems to work like it should, and updates work really well. As per my other post today, I run the free PBX and Debian updates together with a script.
Hmm, there are a lot of Debians, i need a complete .iso as i have to install on a NUC, i hope this is the good one (its very big 7,7 GB) most of the files are not iso or AMD, i have a DN2820 (thats an Intel processor) debian-edu-12.10.0-i386-bd-1.iso.
I tried also Vanilla as your script is for Vanilla, too bad, after selecting language, select keyboard.. empty, tried 2 keyboards but there is emtpy result, i can not further.
Which installable .iso to use? have you got a link?
Have you tried this
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.10.0-amd64-netinst.iso
NUC’s are tricky since they were not initially designed for Linux. Many Linux distributions don’t have the required drivers for that hardware. In the past, I’ve had difficulties with a couple of NUC’s and ended up loading Windows and running the PBX inside VirtualBox VM’s.
Yes, your right, i had in the past tried windows on nuc, but always troubles with (not standard) drivers. And i can install (correct i have installed) Freepbx on my Qnap (with virtual… ) Too bad the virtual box used aboud 15 watt extra. For US no problem but in the Netherlands we payed about 0,80 dollar for 1 kwh.
I would use this one, it’s the FULL 64 bit one. No need to pull anything online:
https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-12.10.0-amd64-DVD-1.iso
3.7GB, and usually the one I use.
I think I could not live someplace with such high electric rates. I pay $0.09/kwh. It would cost $100 to charge an electric vehicle in your country. Ouch! I understand why you want to conserve power usage.
All files with amd in it gives error when trying to burn with Balena etcher.
Ah, pc… i renamed it and now it is burning on de usb stick
I have installed the debian 12, i have made same password for linux user and root but too bad on terminal (macs putty) i got acces for user but root: permission denied publickey password
i dit remove row for the linux nuc on known_host
Connection to 192.168.178.220 closed.
Mac-mini-van-Bob:~ bobwalberg$ ssh [email protected]
[email protected]’s password:
Permission denied, please try again.
[email protected]’s password:
Permission denied, please try again.
[email protected]’s password:
[email protected]: Permission denied (publickey,password).
Mac-mini-van-Bob:~ bobwalberg$ ssh [email protected]
[email protected]’s password:
Permission denied, please try again.
[email protected]’s password:
Permission denied, please try again.
[email protected]’s password:
[email protected]: Permission denied (publickey,password).
Mac-mini-van-Bob:~ bobwalberg$
Mac-mini-van-Bob:~ bobwalberg$
Debian by default does not permit root login by password, edit /etc/ssh/sshd_config to go the insecure way,
PermitRootLogin yes
better to use public keys which are easy to set up with ssh-copy-id [email protected]
Log in as the regular user. Then do:
sudo passwd root
After changing the root password, do:
su root
Then do:
sed -i 's|#PermitRootLogin prohibit-password|PermitRootLogin yes|' /etc/ssh/sshd_config
systemctl restart ssh
At that point, you will be able to log in as the root user.