Just to recap, the goal was to serve a little personal website using my
freedombox instead of the desktop system where it has lived until recently, and
to have it place nicely with freedombox. I copied over my vhost configuration
and LetsEncrypt files, taking care not to clobber. I enabled the
On 04/03/19 12:44 pm, David Mintz wrote:
[...]
> Thought experiment: Suppose you just disable the RedirectMatch "^/$
> ..." and use one and the same domain for serving both your personal
> site and plinth/freedombox apps? (sounds like the implication below
> is that you can do that). I am trying
@Sunil thank you for this clear and thorough explanation. I think I've now got
a better handle on the issues and will be able to fix.
And thank you for Freedombox.
Thought experiment: Suppose you just disable the RedirectMatch "^/$ ..." and
use one and the same domain for serving both your
On 03/03/19 8:21 am, Daddy wrote:
> Hello!
>
> What's the exact certificate error? Is the setup using separate
> certificates for each of the sites, or the same cert?
> If it's the latter, the certificate would have to be "wildcard"
> certificate, supporting multiple subdomains. Let's encrypt is
This issue is somewhere at the intersection of Freedombox and LetsEncrypt and
Apache. Hope no one minds if I bring it here.
I am having trouble getting LetsEncrypt and Apache working together properly to
serve both the freedombox and a little personal website. I've long been using
dyndns.org
