Skip to main content

3CX Certificate File

I use to install 3CX on a bare Debian then switching to the Web wizzard.

The installation process on bare Debian is well described on installing-3cx-pbx-on-debian-10 and just for archive purpose (in case the source website is disabled), I paste the main steps here

wget -O - | apt-key add -
echo "deb buster main" | tee /etc/apt/sources.list.d/3cxpbx.list
dpkg-reconfigure locales

Then absolutely choose en_US.UTF-8

apt update && apt install 3cxpbx

Now we are going to the web Interface and after entering the licence and some other informations:


Not a problem: in fact, you must first generate your server certificate with "certbot". 

Note that "certbot" will need to bind to the port 80 for this to work: temporarily stop "nginx" for that, with:

systemctl stop nginx

You can do it another way, but it is the easiest to me

certbot certonly --standalone -d

Of course, must be an existing DNS record. Create it then run the command, and you have your certificate.

Start  "nginx" back with:

systemctl start nginx

You will have to upload 2 files:

  1. The "cert.pem" file first
  2. The "privkey.pem" file in the next screen

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs Pulumi LSP

Install Pulumi Emacs Mode The source code is on At the very bottom of the page are the instructions on how to install. You Need to have make installed. $ make install emacs-client mkdir -p ./bin go build -ldflags "-X" -o ./bin -p 10 ./cmd/... go: downloading v3.53.1 ... ... ... go install -ldflags "-X" ./cmd/... mkdir -p editors/emacs/bin cd editors/emacs && emacs -Q --batch --eval "(progn (setq package-user-dir \"$(pwd)/bin\" \ package-archives '((\"melpa\" . \"\") \