@phenomlab absolutely, their step brother residing in a different Countries.
https://surfshark.com/blog/surfshark-vs-nordvpn
@jac I see it - you’ll need to create the new subdomain in your Virtualmin instance
@phenomlab logged in to Virtualmin now.
Just looking how to do this.
@jac looks tricky if you don’t know what you’re doing
@jac Create virtual server > sub server?
@jac I don’t want to post sensitive information but is this correct?
@jac Yep, that’s it.
@phenomlab thanks, now to proceed
@jac said in setting up Matomo:
@phenomlab thanks, now to proceed
rookie error
“Failed to create virtual server : A sub-server cannot have MySQL enabled unless the parent server does”
@jac Yes, that means that MySQL isn’t enabled at the root domain. You’ll need to go to the root domain, and enable that feature for it to work on subdomains.
The reason for it being missing is that you do not require MySQL for NodeBB as it uses MongoDB instead.
@phenomlab Thanks Mark,
I’ll go and locate this now.
@jac done
@jac Yes, this probably helps
@jac Now re-add the subdomain
@jac “Requesting a certificate for stats.stockportcounty.fans, www.stats.stockportcounty.fans from Let’s Encrypt …”
that will be interesting…
@jac Should be fine. It may bomb on the www request - let me know if that’s the case.
@phenomlab said in setting up Matomo:
@jac Should be fine. It may bomb on the www request - let me know if that’s the case.
Requesting a certificate for stats.stockportcounty.fans, www.stats.stockportcounty.fans from Let's Encrypt ..
.. request failed : Web-based validation failed :
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for stats.stockportcounty.fans
http-01 challenge for www.stats.stockportcounty.fans
Using the webroot path /home/stockportcounty/domains/stats.stockportcounty.fans/public_html for all unmatched domains.
Waiting for verification...
Challenge failed for domain www.stats.stockportcounty.fans
http-01 challenge for www.stats.stockportcounty.fans
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: www.stats.stockportcounty.fans
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for
www.stats.stockportcounty.fans - check that a DNS record exists for
this domain
DNS-based validation failed :
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Obtaining a new certificate
Performing the following challenges:
dns-01 challenge for www.stats.stockportcounty.fans
Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
Waiting for verification...
Challenge failed for domain www.stats.stockportcounty.fans
dns-01 challenge for www.stats.stockportcounty.fans
Cleaning up challenges
Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: www.stats.stockportcounty.fans
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.www.stats.stockportcounty.fans - check that a DNS
record exists for this domain
@jac Unsurprising. There are two ways to do this
VirtualMin -> Server Configuration -> SSL Certificate
Let’s Encrypt
Set as per the example, so you only request the domain you want. Ensure that “Automatically renew certificate” is selected, then “Request Certificate”
@phenomlab said in setting up Matomo:
@jac Unsurprising. There are two ways to do this
- Create a CNAME record called WWW and have it point to the subdomain in DNS
- Create a custom request for LE so that it ignores the www value, and only processes the actual domain you want
VirtualMin -> Server Configuration -> SSL Certificate
Let’s Encrypt
Set as per the example, so you only request the domain you want. Ensure that “Automatically renew certificate” is selected, then “Request Certificate”
Thanks,
which is the best solution?
@jac Well, depending on configuration, they are as simple as each other. If you choose the first, then you need to add DNS records, and ensure your server is capable of handling them on arrival (it should be by default).
If you choose the second, it’s the easiest (and probably laziest ), but it will work. We just then need to set a redirect so that all traffic lands up at https://site.domain.com even if we try with or without the www prefix.