From: Alexander Burke via pve-user <pve-user@lists.proxmox.com>
To: Randy Bush <randy@psg.com>
Cc: Alexander Burke <alex@alexburke.ca>, pve-user@lists.proxmox.com
Subject: Re: [PVE-User] use existing LE account
Date: Sun, 19 May 2024 22:06:00 +0000 [thread overview]
Message-ID: <mailman.189.1716156375.319.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <m2msoliior.wl-randy@psg.com>
[-- Attachment #1: Type: message/rfc822, Size: 3895 bytes --]
From: Alexander Burke <alex@alexburke.ca>
To: Randy Bush <randy@psg.com>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] use existing LE account
Date: Sun, 19 May 2024 22:06:00 +0000
Message-ID: <da262ce5-4310-4f75-9881-85e3f08e6488@alexburke.ca>
Hi Randy,
Create a new account in the UI. Let it write its files into that dir.
Edit them as you see fit.
Cheers,
Alex
On 2024-05-19 23:40, Randy Bush wrote:
> bennet
>
>> have a look at the files in "/etc/pve/priv/acme". They contain all the
>> information needed.
>
> prox.rg.net:/home/randy# ls -la /etc/pve/priv/acme/
> total 0
> drwx------ 2 root www-data 0 May 19 16:46 ./
> drwx------ 2 root www-data 0 May 19 16:46 ../
>
> i already had that information :)
>
> if there had been the classic directory `secret`, i would have known
> where to put my account key. but ...
>
> randy
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-05-19 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 17:20 Randy Bush
2024-05-19 19:16 ` Bennet Gallein
2024-05-19 21:40 ` Randy Bush
2024-05-19 22:06 ` Alexander Burke via pve-user [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.189.1716156375.319.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alex@alexburke.ca \
--cc=randy@psg.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal