Nevermind, it doesn't look like it's related to SSL. It seems like a proxy is disrupted, so hard refreshing a couple of times seems to put you on a working proxy.
To clarify, there seems to be a network disruption related to SSL. If you convert the URL to an HTTP (remove HTTPS) URL, the log is accessible.
ChaoyiOn Sat, Jun 20, 2015, 1:24 AM Truong Anh Tuan <email@example.com> wrote:FYI.
(meetbot is inaccessible here so I can not copy the full minutes)
----- Forwarded Message -----
Sent: Saturday, June 20, 2015 12:11:44 PM
Subject: tuanta's meeting ended in #fedora-meeting
tuanta's meeting ended in #fedora-meeting
You received this message due to your preference settings at
meetingminutes mailing list
ambassadors mailing list