18.1.1 & acme client

Started by elektroinside, February 02, 2018, 01:16:14 PM

Previous topic - Next topic
So it's a permissions issue.

I would like to see someone (hint! hint!) write up a nice tutorial on using the acme client plugin to create certs.

Does anybody know when the update for acme 2.6.7 (ETA on LE package) is coming ??


I will ping the FreeBSD maintainer.


Nice :) Thanks, Franco!
OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member

Thanks Franco, how can we update the acme package ??

# opnsense-code tools ports
# cd /usr/ports/sysutils/acme.sh
# make
# make deinstall
# make install

Will also be in 18.1.3, but that takes two more weeks.


Cheers,
Franco

Thank you, it works! In your description is a mistake

The correct directory is:

# cd /usr/ports/security/acme.sh

I am very exicited about the quick answers here. Thank you at all people !!

Can't get a cert issued. Log shows 'Create domain key error'
I can see the key file was created.

What am I doing wrong?

Quote from: dcol on February 24, 2018, 08:31:00 PM
Can't get a cert issued. Log shows 'Create domain key error'
I can see the key file was created.

What am I doing wrong?
Well, um, bro, update your acme.sh script or wait for 8.1.3 in a week or so  8) How to?  :o This has been answered few times some posts above  :-\

acme.sh was updated. This is not the reason.

Quoteacme.sh was updated. This is not the reason.
Still Create domain key error ?

I did what franco posted:

# opnsense-code tools ports
# cd /usr/ports/sysutils/acme.sh
# make
# make deinstall
# make install

After that i deleted the certificated that are in a failed status und created them successfully again.

Quote from: dcol on February 25, 2018, 06:21:19 PM
acme.sh was updated. This is not the reason.
Well, there is very only thing left: Your validation method fails. Personally, I always used a non-standard port for GUI so a HTTP-01 method never worked for me. I use DNS-01 with Hurricane Electric. I've configured DigitalOcean 2 droplets in a week and both works with DNS-01 challenge and doesn't validate with HTTP-01.