On Nov 8, 2016, at 7:25 AM, Dirk Engling wrote:
>
> WELLKNOWN="/usr/local/www/dehydrated/.well-known/acme-challenge"
Thank you, that solved it.
Processing covisp.net with alternative names: mail.covisp.net www.covisp.net
+ Signing domains...
+ Generating private key...
+ Ge
>
> On 08 Nov 2016, at 07:11, Dirk Engling wrote:
>
> On 08/11/2016 14:59, @lbutlr wrote:
>
>> # su -m _dehydrated -c 'bash /usr/local/bin/dehydrated --cron'
>> # INFO: Using main config file /usr/local/etc/dehydrated/config
>> Processing co
LLKNOWN="/usr/local/www/dehydrated/.well-known/acme-challenge"
created both directories and had apache use /usr/local/www/dehydrated
for non-tls connections. Your mileage may vary, so you might need to
have WELLKNOWN point to /usr/local/www/.well-known/acme-challenge and
make this directory b
On 08/11/2016 14:59, @lbutlr wrote:
> # su -m _dehydrated -c 'bash /usr/local/bin/dehydrated --cron'
> # INFO: Using main config file /usr/local/etc/dehydrated/config
> Processing covisp.net with alternative names: covisp.net www.covisp.net
> + Signing domains...
>
>> /usr/local/www/.well-known/acme-challenge/bXxlfu…
>>
>> Certs are being created in /usr/local/etc/dehydrated/certs each time I try
>> to run the script.
>
> What does your /usr/local/etc/dehydrated/config say about the WELLKNOWN
> variable? Shouldn't that poin
ted in /usr/local/etc/dehydrated/certs each time I try to
> run the script.
What does your /usr/local/etc/dehydrated/config say about the WELLKNOWN
variable? Shouldn't that point to /usr/local/www/dehydrated? Your
webroot seems to point to /usr/lo
I’m having issues getting dehydrated to work after installing it, and there
seems to be no documentation installed with it that I can find.
The package is installed, but I am unable to get the web side of things working
and have found conflicting information.
I tried creating a directory in my
I’m having issues getting dehydrated to work after installing it, and there
seems to be no documentation installed with it that I can find.
The package is installed, but I am unable to get the web side of things working
and have found conflicting information.
I tried creating a directory in my
In een bericht van 19-9-2016 13:58:
Btw, can someone tell me what the logic is between the new name
dehydrated and its functionality (domain certification)? Don't see it
yet :-)
Thanks for explaining.
./Jos
___
freebsd-ports@freebsd.org ma
On 19/09/2016 15:10, Mark Martinec wrote:
> It seems to allude to instant drinks (dehydrated): just add water and
> it does all the rest by magic - you obtain a ready drink / a valid
> certificate.
It's a pun on the ACME protocol it implements. ACME dehydrated rocks,
just add wate
On 2016-09-19 13:58, JosC wrote:
Btw, can someone tell me what the logic is between the new name
dehydrated and its functionality (domain certification)? Don't see it
yet :-)
It seems to allude to instant drinks (dehydrated): just add water and it
does
all the rest by magic - you obt
In een bericht van 17-9-2016 1:38:
After switching from letsencrypt to dehydrated, the upgrade to the
latest port version keeps appearing when running
Is solved - for some reason letsencrypts was still installed although it
didn't show in my pkg list. After deinstalling it an re-insta
After switching from letsencrypt to dehydrated, the upgrade to the
latest port version keeps appearing when running
portmaster -y --clean-distfiles
portmaster -y --clean-packages
portmaster -y --check-depends
portmaster -a
although there is no port update of it available.
Apperantly there
13 matches
Mail list logo
