OK so Discourse setup decides to give me this non-existent error
(<unknown>): did not find expected key while parsing a block mapping at line 40 column 3 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
Line 40 is not even LANG, line 40 is LC_ALL
Found the problem. new Discourse setup script encrypts the SMTP password by default but itâs broken because it carelessly puts double quotes on the password, breaking the YAML
Tripped over on this stupid SMTP thing again, gonna reinstall OS and start over
a cool confusion material for tonight: mofhâs nameservers ptr record doesnât actually match the intended IPs. ns1âs PTR is ns1, good. but, ns2âs PTR is ns3, ns3âs PTR is ns2, ns4âs PTR is ns3, and ns5âs PTR is ns4. also mofh feels like another cloud computing giant. all of their NS is centralized in one location (FranTech in New Mexico,) so if that entire DC goes down, say goodbye to free subdomains
The nameserver IPs are anycasted across Europe, US East and US West. The only thing thatâs in New Mexico is the registered office of the company providing that infrastructure.
And no, you cannot tell this from the IP WHOIS information. That only tells you who owns the IP address and where they are located, IP addresses do not inherently have a physical presence anywhere.
i use ipinfo to check the IPs, and couldâve sworn for CF IPs it has Anycast tag. I guess FranTech can tell ipinfo to update the info. Also admin, how often you watch TV in your country?
iâm addicted to this theme for hours . alright, letâs run an experiment
letâs reveal the said experiment. and that is i tried to use cloudnsâ subdomain here. as it was listed in PSL, it worked. but i thought client areaâs SSL issuer caught a rate limit error or something to the point i close the page, but turns out it worked ._.
donât know why iâm going with a meh response here, but alright. itâs a required change anyway
Whatâs this âipinfoâ thing? Iâve never heard of it. Is it a tool? A service?
IP addresses donât have a physical location. IP addresses are owned by a network operator, and the WHOIS information of an IP address shows who owns that IP address. That network operator can then freely use that IP address however they want in their own network, which could span locations across the planet.
GeoIP databases are not facts, they are educated guesses. Other organizations feed them data with address details and IP addresses corresponding to them. Whenever my home IP changes, websites usually think Iâm in a city in a completely different part of the country, because thatâs where my ISP had used the IP address before.
I donât, I cancelled the subscription many years ago. And I donât have much time to watch anything nowadays.
Itâs going to be mandatory by 2029 for all CAs. Letâs Encrypt is ahead of the curve here by enforcing it a year ahead of time, but this is still an early notice.
Iâm curious to see whatâs going to happen with all companies that currently charge for certificates and have manual verification processes by email. Selling 5 year certificates that you have to manually reissue every year is still feasible, but every 45 days?
Agreed! I hate how you often have to give the SSL tool unlimited access to your domainâs DNS zone for the certificates. And using something like acme-dns has its own problems.