On 7/25/18 7:15 AM, Maynard, Chris wrote:
>> From: Wireshark-users [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of David Aldrich
>> Sent: Monday, July 23, 2018 11:16 AM
>> To: wireshark-users@xxxxxxxxxxxxx
>> Subject: [Wireshark-users] ask.wireshark service unavailable
>>
>> On https://ask.wireshark.org when I try to login or recover my account I see:
>> Service Unavailable
>> The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
>> It's been like this for a week or more. Is there a site problem?
>
> In case this happens again to someone else, I thought I'd explain what happened here. In this case, the user had an account on the old Q&A site (now at https://osqa-ask.wireshark.org/), so when he tried to log into the new site at https://ask.wireshark.org/questions/, he didn't actually have an account there. His old account wasn't migrated because his reputation points on the old site were below the 25 point threshold that Gerald applied in order to avoid migrating over all the spam accounts, explained more fully at https://osqa-ask.wireshark.org/questions/60424/osqa-is-unmaintained-whats-next.
>
> "Service Unavailable" is certainly a strange way to report, "No account exists with that username", but that seems to have been what was reported. Incidentally, I tried logging in with an invalid account, but it just caused the login page to be refreshed for me.
With some help from David I was able to determine that the "Service Unavailable" error was due to what appears to be an antispam false positive.
