Harald<p><span class="h-card" translate="no"><a href="https://fedi.arkadi.one/@tootbrute" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tootbrute</span></a></span> <span class="h-card" translate="no"><a href="https://c.im/@sbb" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sbb</span></a></span> </p><p>In case you are interested how I solved having a publicly signed SSL certificate for a home server not connected to the Internet, here is what I did:</p><p><a href="https://codeberg.org/harald/Codeschnipselnotizen/src/branch/main/notes/Public_Cert_In_Home_Network.md" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/harald/Codeschnip</span><span class="invisible">selnotizen/src/branch/main/notes/Public_Cert_In_Home_Network.md</span></a></p><p>The downside: there seems to be no way without having a registered domain. It took me unnecessary time to accept this. The upside: taking the step to get yourself a domain is simpler and cheaper than I was aware of and with the right tool, the rest was easy enough.</p><p><a href="https://nrw.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a> <a href="https://nrw.social/tags/homeserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homeserver</span></a> <a href="https://nrw.social/tags/acmesh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>acmesh</span></a> <a href="https://nrw.social/tags/letsencrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>letsencrypt</span></a></p>