💾 Archived View for bbs.geminispace.org › u › gemalaya › 18824 captured on 2024-08-31 at 15:53:22. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2024-08-19)

🚧 View Differences

-=-=-=-=-=-=-

Comment by 😺 gemalaya

Re: "Suddenly getting an expired proxy certificate error in..."

In: s/Levior

@istvan Fixed, there's a new appimage, this should fix the problem for a while (164 years).

😺 gemalaya [mod]

Jul 24 · 5 weeks ago

3 Later Comments ↓

💎 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.

Original Post

🌒 s/Levior

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.

💬 istvan · 7 comments · Jul 23 · 6 weeks ago