It's back up.

On 4/26/17 7:52 AM, Gerald Combs wrote:
> There's a hardware issue at AWS. I'm hoping to have it back up and running in 
> the next 30 minutes or so. 
> 
> On 4/26/17 6:50 AM, Roland Knall wrote:
>> There is a known issue with the server atm, and we ware trying to fix
>> it, please check back a little bit later
>>
>> cheers,
>> Roland
>>
>> On Wed, Apr 26, 2017 at 3:44 PM, Maynard, Chris
>> <christopher.mayn...@igt.com <mailto:christopher.mayn...@igt.com>> wrote:
>>
>>     It seems that Bugzilla is unreachable for me.  Am I only the one
>>     seeing this?
>>
>>     Error 525 Ray ID: 3559f7453baa06a9 * 2017-04-26 13:42:32 UTC
>>     SSL handshake failed
>>     What happened?
>>
>>     Cloudflare is unable to establish an SSL connection to the origin
>>     server.
>>
>>     What can I do?
>>     If you're a visitor of this website:
>>
>>     Please try again in a few minutes.
>>
>>     If you're the owner of this website:
>>
>>     It appears that the SSL configuration used is not compatible with
>>     Cloudflare. This could happen for a several reasons, including no
>>     shared cipher suites. Additional troubleshooting information
>>     here.<https://support.cloudflare.com/hc/en-us/articles/200278659
>>     <https://support.cloudflare.com/hc/en-us/articles/200278659>>
>>
>>     Thanks.
>>     - Chris
>>
>>     --
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>     CONFIDENTIALITY NOTICE: This message is the property of
>>     International Game Technology PLC and/or its subsidiaries and may
>>     contain proprietary, confidential or trade secret information.  This
>>     message is intended solely for the use of the addressee.  If you are
>>     not the intended recipient and have received this message in error,
>>     please delete this message from your system. Any unauthorized
>>     reading, distribution, copying, or other use of this message or its
>>     attachments is strictly prohibited.
>>
>>     
>> ___________________________________________________________________________
>>     Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org
>>     <mailto:wireshark-dev@wireshark.org>>
>>     Archives:    https://www.wireshark.org/lists/wireshark-dev
>>     <https://www.wireshark.org/lists/wireshark-dev>
>>     Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>     <https://www.wireshark.org/mailman/options/wireshark-dev>
>>                  mailto:wireshark-dev-requ...@wireshark.org
>>     <mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe
>>
>>
>>
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
>> Archives:    https://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>              mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>>
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to