#dev | Logs for 2017-11-12

« return
[01:46:40] <Bytram> TheMightyBuzzard: thanks!
[01:55:25] <Bytram> may be a silly question, but how can I verify we have the right version of apache running on bery?
[02:39:41] <TheMightyBuzzard> Bytram, it's prolly in the headers from any response
[02:43:42] <Bytram> I thought that, but unless I'm poking at the wrong place, all I see is nginx headers (I assume from our front end?)
[02:46:17] <TheMightyBuzzard> shouldn't be a front end for bery
[02:48:39] <TheMightyBuzzard> use webmail.soylentnews.org then. it shows apache 2.4
[02:53:07] <Bytram> hmmm, Imust be doing it wrong... maybe I should try: https://72.14.184.41:443
[02:54:04] <TheMightyBuzzard> no. that will not work.
[02:54:12] <Bytram> yup, just found that out.
[02:54:20] <TheMightyBuzzard> named vhosts
[02:54:36] <Bytram> Huh? Oh. doh!
[02:55:28] <TheMightyBuzzard> curl -i https://webmail.soylentnews.org
[02:55:56] <TheMightyBuzzard> sylnt.us shows apache as well
[02:57:11] <Bytram> hmm curl did not work... also tried curl -k
[02:57:12] <Bytram> but
[02:57:19] <Bytram> I'm also running on windows so
[02:57:26] <Bytram> it is likely something in my implementation
[02:57:42] <Bytram> I *am* able to look at full headers sent back using my browser
[02:57:46] <Bytram> that showed:
[02:57:56] <Bytram> Server: Apache/2.4.23 (Unix) OpenSSL/1.0.1e-fips PHP/7.0.9
[02:58:45] <Bytram> much obliged for the pointers!
[03:00:00] * Bytram is sorely tempted to write up some kind of daemon script that runs in the background and checks things like cert expiration, server status, etc. and realized there's prolly packages out there for stuff like that already... ISTR we had icinga running for a while.
[03:00:40] <Bytram> thanks again
[03:01:17] <Bytram> had a *really* busy day at work today and am quite well knackered atm... gonna call it an early night as tomorrow is a work day for me, too.
[23:49:35] -!- systemd [systemd!~init@0::1] has joined #dev