Upon my recent "renewal" (replaced with new) TLS(/"SSL") certs for
[*.]balug.org, for the cert covering the web stuff, I also added:
*.staging.balug.org (*.balug.org itself also covers the bare
staging.balug.org).
Haven't added any [*.]staging.balug.org stuff to DNS, etc - at least yet,
other than that temporarily added for obtaining the cert itself.
And no rush to do so (time, priorities, ...).
Rationale(?):
I think [*.]staging.balug.org may be more logical/appropriate for
most of what [*.]new.balug.org gets used for these days (well, years now).
Might want to, at some point, phase out [*.]new.balug.org.
Once-upon-a-time www.new.balug.org was intended to and used as
the "go forward" of what www.balug.org itself would generally
become - and they were on separate hosts. Well, for many years now,
www.new.balug.org is on same host as [www.]balug.org,
and www.new.balug.org is typically and mostly (if not entirely)
used as essentially staging/preview of what www.balug.org will become,
typically updating content on www.new.balug.org (and checking/revising it)
before making those same content changes to www.balug.org
May be mostly moot by the time this makes it through to the BALUG
list server and out. In any case ...
----- Forwarded message from Michael.Paoli(a)cal.berkeley.edu -----
Date: Tue, 20 Nov 2018 18:59:24 -0800
From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu>
Subject: outage: [www.]{sf-lug,balug}.org
To: SF-LUG <sf-lug(a)linuxmafia.com>
And ... outage again :-\
Guestimating if it's the "usual", will likely be on-line again
by sometime Wednesday evening (I may or may not get to it before then).
Per earlier:
impacts all [*.]sf-lug.{org,com} & [*.]balug.org
SF-LUG lists remain up and on-line (at least as far as I'm aware).
Also, DNS mostly not impacted (in general, slaves remain functional),
though there may be some additional latencies on DNS due to failovers
to other nameservers.
> From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu>
> Subject: "all better now:" Re: outage: [www.]{sf-lug,balug}.org
> Date: Wed, 10 Jan 2018 20:15:04 -0800
> And ... again, same deal, went off-line at:
> <~= 2018-01-11T01:23:21+00:00 2018-01-10T17:23:21-08:00
> and back on-line by:
>> ~= 2018-01-11T04:04:06+00:00 2018-01-10T20:04:06-08:00
> ... again, swift kick to the power switch on DSL modem to reset it,
> and "all better" - again ... at least for now.
>
>> From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu>
>> Subject: "all better now:" Re: outage: [www.]{sf-lug,balug}.org
>> (ETR: eveningish)
>> Date: Wed, 06 Dec 2017 18:08:09 -0800
>
>> And ... swift kick to the power switch on DSL modem to reset it,
>> and "all better now".
>> Looks like the outage started around:
>> BALUG PING: ping6 2001:470:1f04:19e::2 FAILED 2017-12-06T20:53:56+00:00
>> GW PING: ping 198.144.194.233 FAILED 2017-12-06T20:54:09+00:00
>> and service restored a few minutes ago
>>
>>
>>> From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu>
>>> Subject: outage: [www.]{sf-lug,balug}.org (ETR: eveningish)
>>> Date: Wed, 06 Dec 2017 14:46:38 -0800
>>
>>> So,
>>>
>>> They were up and on-line this morning, at least as late as about
>>> mid-morning or later, but off-line now.
>>> POTS line appears to be working, but not IP,
>>> likely the DSL modem needs to be reset (powercycled) again ...
>>> but don't have means to do that remotely.
>>>
>>> Presumably I'll have this resolved sometime this evening once I'm
>>> on-site again.
>>>
>>> impacts all [*.]sf-lug.{org,com} & [*.]balug.org
>>> SF-LUG lists remain up and on-line (at least as far as I'm aware).
----- End forwarded message -----
Tossing this one onto (suitable) list, because ... well, why not! :-)
> From: "Rick Moen" <rick(a)linuxmafia.com>
> Subject: Re: Login to BALUG Wiki
> Date: Thu, 15 Nov 2018 17:57:40 -0800
> Quoting Michael Paoli (Michael.Paoli(a)cal.berkeley.edu):
>
>> Seems more logical would to have that information on the
>> "self-"registration wiki page ... otherwise folks may not see it
>> anyway.
>
> After successful login, I put a notice on
> https://www.wiki.balug.org/wiki/doku.php , near the top.
Thanks ... I also tweaked the language (very) slightly just for slightly
better approximation of (mostly historical) reality.
> I ack your point that autoregistrations were few and far between, but
> lack of any information about how to get a login meant that anyone
> wanting to help would have no idea how to proceed.
>
> Sorry, but what 'self-' registraiton page? Not sure what this reference
> is to.
Heck, been so long I forget where the self-registration wiki page even
is/was.
>> I figured manual was "quite good enough" to stop the immediate issue
>> (the high volume of bot registrations was causing the wiki to bog down
>> and fail in annoying ways).
>
> I sympathise.
>
> Restoring login _with_ CAPTCHA plugin would be a 'have your cake and eat
> it too' solution, IMO -- if/when you get around to it.
Yep *somewhere* on the "todo" list.
Background/history - have a look at:
curl -s --range 134225-268633 https://www.archive.balug.org/log.txt
And *also* very handy for me too ... looks like I'd *disabled* the
registration page - so likely it doesn't show at all, or just won't
let one self-register.