💾 Archived View for bbs.geminispace.org › u › istvan › 18822 captured on 2024-08-19 at 01:01:15. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Suddenly getting an expired proxy certificate error in..."
Awesome. Thank you! I searched the documentation but never saw those flags. Maybe I missed it. I’ll just tie it to the domain’s cert and it should be good going forward. Thank you so much for the response and hope it helps anyone else using levior.
Jul 24 · 4 weeks ago
😺 gemalaya [mod] · Jul 24 at 13:13:
@istvan It wasn't documented, only by running "levior --help" you could see these flags.
I just pushed a new cert (expires in 2188) to the git repo, but there's an issue with the gitlab release creation, so there's no new appimage yet, i should be able to fix it.
😺 gemalaya [mod] · Jul 24 at 13:31:
@istvan Fixed, there's a new appimage, this should fix the problem for a while (164 years).
💎 istvan [OP] · Jul 25 at 10:02:
Thanks for pointing me to those parameters. Being able to specify the right certificate for my domain finally knocked out the warning message about domain/cert mismatch I’d been getting the last few months.
😺 gemalaya [mod] · Jul 25 at 10:42:
@istvan I will definitely add a section in the docs to explain how to use a custom certificate.
😺 gemalaya [mod] · Jul 25 at 11:20:
@istvan Looked at the code and actually in the cfg file it expects 'gemini_cert' and 'gemini_key' as opposed to --cert and --key on the cmd line. I've changed that to 'cert' and 'key' so that it matches.
Suddenly getting an expired proxy certificate error in Levior when using it as an HTTPS proxy for Lagrange. Says the server's TLS certificate expired, but don't see any setting to change the certificate. Is it possibly something that was baked into the AppImage? Pinged cipres on misfin but got an away message. Figured I'd post here in case anyone else is having some trouble.