I've resolved the issue and now I'm able to serve https.
As you already know, the problem is always the same and it's between the chair
and the table ;-)
As noted by @ori (thank you), the issue was that I was trying to load the key
from my own namespace instead of none. Also I was missing to re
Quoth Iban Nieto :
> @skip I've performed the entire procedure in the same namespace and in
> another ns by using line per line commands in the console and using scripts,
> all with the same luck. Also /srv/factotum is in place in my namespace as I
> have auth/factotum in my $home/lib/profile.
Hello!
@igor I've followed some of your instructions (as you can see, the same
procedure for acmed), but my setup is a bit different than yours. Could you
please tell me what's wrong with my setup? (this is my very first time using
tls in 9front).
@skip I've performed the entire procedure in t
Do you have the right factotum in the namespace you're working on?
Listing /srv should give a clue.
On Wed, Sep 13, 2023 at 2:03 PM Iban Nieto wrote:
>
> Hello!
>
> I'm trying to serve https (443) and gemini (1965) under 9front.
>
> I've already a working rc-httpd (80) setup and now I would like
A working setup with tlssrv(8) and acmed(8) is documented here:
•
https://9lab.org/plan9/web-server-with-go-based-static-site-generator-hugo/#https-port-443
A comparison of those steps with your steps below might reveal
the issue.
Quoth Iban Nieto :
> Hello!
>
> I'm trying to serve https (443)
Hello!
I'm trying to serve https (443) and gemini (1965) under 9front.
I've already a working rc-httpd (80) setup and now I would like to start using
letsencrypt certificates.
Also rc-gemd (gemini server) needs a certificate in order to work.
I manage to get the certificate with acmed using the
