> Am 01.06.2023 um 17:44 schrieb Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx>: > > On Thu, 2023-06-01 at 11:15 +0930, Tim via users wrote: >> Trying to find decent and affordable hosting in my country is an >> exercise in frustration. Trying to find one that's actually in my >> country is difficult > > Realising, after the fact, I hadn't mentioned I'm in Australia, during > this thread... > > There's a couple of aspects to wanting local hosting service, apart > from the obvious of wanting to deal with locals and no overseas call > centres. Google will consider my site is Australian if I have an > Australian IP address, or an Australian top-level domain name. And can > return my site as an answer for queries that want local answers, > instead of discarding it as overseas. > > I don't have a .au TLD. You can get personal id.au domain names > without too many hurdles to jump through, but I don't want one of them > (a website in my own name). All the other .au (com.au, net.au, org.au) > domain names required an Australian Business Number, or other similar > business registration, I don't have one of them, nor want to get one. > So having an Australian IP address is the only way to make Google thing > my .com address is Australian. > > Most people around here don't understand the purpose of these various > top-level subdomains and think that most sites are either simply > .com.au or .com, so bucking that trend works against you. > > While it's a good thing that our name registration system knuckled down > and insisted that .com.au was only used for commercial sites, likewise > with .net.au for business, there's asn.au & .org.au for non-profit > associations and charitable organisations, etc. Using them for their > intended purposes. It's a shame that they didn't have the foresight to > have a general-purpose top domain, having .net.au simply for something > that's on the net would have been a good idea. > > Only recently (end of last year) they seem to be opening up .au by > itself for uncategorised purposes, but registrars are price gouging it. Two ideas: (a) The message says .. domain failed DCV (Domain Control Validation) … Even if the domain worked previously, it may be worthwhile to check the DNS entry. (b) If you suspect a problem with the certificate handling by certbot or your hosters administrative tools, did you try Apache md module (https://httpd.apache.org/docs/trunk/mod/mod_md.html)? Then Apache would handle the certificate directly. You would to have to add to your host configuration something like # Letsencrypt certificate management via Apache mod_md # By default, automatically all alternative names get included. MDContactEmail joe@xxxxxxxxxxx MDCertificateAgreement accepted MDomain example.com <VirtualHost *:443> (Your configure here) And comment out the #SSLCertificateFile /etc/letsencrypt/live/example.com/cert.pem #SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem #SSLCertificateChainFile /etc/letsencrypt/live/example.com/chain.pem -- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@xxxxxxxxxxxxxxxxx Timezone: CET (UTC+1) / CEST /UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
