Forum: >>> Magnum BBS <<<

Hint..

From kk4qbn@1:103/705 to All on Sat Aug 10 14:16:50 2024

Wow.. I feel so stupid..

If you want letsyncrypt to continue working without issue, do not put *.amazonaws.com in your hostname filter..

I did this quite some time ago because I presume some crawler of somesort kept hammering my webserver, I didnt realize acme used amazonaws to do its verifications, etc.. until just a few minutes ago.. been having issues with this for quite sometime, everytime letsyncrpt run it would error out stating it expecting 200 and recieved another errorlevel..

then noticed that I have never actually seen acmes hostname in the webserver logfile, then when trying to run letsyncrypt manually *.compute.amazonaws.com would hit my webserver from a few different subdomains on that hostname..

So yeah... that was a stupid mistake that can easily hide an issue for a while if not paying attention..
---
Tim (kk4qbn)
+o kk4qbn.synchro.net
� Synchronet � KK4QBN BBS - kk4qbn.synchro.net - Chatsworth, GA USA
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	797
Nodes:	16 (3 / 13)
Uptime:	201:53:37
Calls:	13,215
Calls today:	14
Files:	15,493
Messages:	6,579,840
Posted today:	1