Jump to page: 1 2
Thread overview
!Alert! dlang.org SSL Error
Feb 06, 2018
Jakub Łabaj
Feb 06, 2018
Seb
Feb 06, 2018
Seb
Feb 06, 2018
Seb
Feb 06, 2018
Jakub Łabaj
Feb 06, 2018
Simen Kjærås
Feb 06, 2018
Jan Knepper
Feb 06, 2018
Seb
Feb 06, 2018
Jan Knepper
February 06, 2018
Chromium: ERR_SSL_PROTOCOL_ERROR

With Firefox and Chomium and with different Ubuntu Versions (17.10 and 16.04.)

Firefox - Google translated:

Error: Secure connection failed

An error occurred while connecting to dlang.org. SSL has received an entry that has exceeded the maximum allowed length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

     The website can not be displayed because the authenticity of the received data could not be verified.
     Please contact the owner of the website to inform him of this issue.
February 06, 2018
On Tuesday, 6 February 2018 at 10:05:52 UTC, Martin Tschierschke wrote:
> Chromium: ERR_SSL_PROTOCOL_ERROR
>
> With Firefox and Chomium and with different Ubuntu Versions (17.10 and 16.04.)
>
> Firefox - Google translated:
>
> Error: Secure connection failed
>
> An error occurred while connecting to dlang.org. SSL has received an entry that has exceeded the maximum allowed length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
>
>      The website can not be displayed because the authenticity of the received data could not be verified.
>      Please contact the owner of the website to inform him of this issue.

Same for me.
February 06, 2018
On Tuesday, 6 February 2018 at 13:18:26 UTC, Jakub Łabaj wrote:
> On Tuesday, 6 February 2018 at 10:05:52 UTC, Martin Tschierschke wrote:
>> Chromium: ERR_SSL_PROTOCOL_ERROR
>>
>> With Firefox and Chomium and with different Ubuntu Versions (17.10 and 16.04.)
>>
>> Firefox - Google translated:
>>
>> Error: Secure connection failed
>>
>> An error occurred while connecting to dlang.org. SSL has received an entry that has exceeded the maximum allowed length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
>>
>>      The website can not be displayed because the authenticity of the received data could not be verified.
>>      Please contact the owner of the website to inform him of this issue.
>
> Same for me.

I don't have any issues on my machine with Chrome and Firefox..
February 06, 2018
On Tuesday, 6 February 2018 at 13:31:23 UTC, Seb wrote:
> On Tuesday, 6 February 2018 at 13:18:26 UTC, Jakub Łabaj wrote:
>> On Tuesday, 6 February 2018 at 10:05:52 UTC, Martin Tschierschke wrote:
>>> Chromium: ERR_SSL_PROTOCOL_ERROR
>>>
[...]
Please contact the owner of the website to inform him of
>>> this issue.
>>
>> Same for me.
>
> I don't have any issues on my machine with Chrome and Firefox..
Hmm, my phone with chrome on android7 and chrome on ipad2 no problems,too.

February 06, 2018
On Tuesday, 6 February 2018 at 13:42:18 UTC, Martin Tschierschke wrote:
> Please contact the owner of the website to inform him of
>>>> this issue.
>>>
>>> Same for me.
>>
>> I don't have any issues on my machine with Chrome and Firefox..
> Hmm, my phone with chrome on android7 and chrome on ipad2 no problems,too.
@forum.dlang.org and @code.dlang.org everything ok.

February 06, 2018
On Tuesday, 6 February 2018 at 13:45:20 UTC, Martin Tschierschke wrote:
> On Tuesday, 6 February 2018 at 13:42:18 UTC, Martin Tschierschke wrote:
>> Please contact the owner of the website to inform him of
>>>>> this issue.
>>>>
>>>> Same for me.
>>>
>>> I don't have any issues on my machine with Chrome and Firefox..
>> Hmm, my phone with chrome on android7 and chrome on ipad2 no problems,too.
> @forum.dlang.org and @code.dlang.org everything ok.

Those are different servers ;-)
February 06, 2018
On Tuesday, 6 February 2018 at 13:42:18 UTC, Martin Tschierschke wrote:
> On Tuesday, 6 February 2018 at 13:31:23 UTC, Seb wrote:
>> On Tuesday, 6 February 2018 at 13:18:26 UTC, Jakub Łabaj wrote:
>>> On Tuesday, 6 February 2018 at 10:05:52 UTC, Martin Tschierschke wrote:
>>>> Chromium: ERR_SSL_PROTOCOL_ERROR
>>>>
> [...]
> Please contact the owner of the website to inform him of

Vladimir already did so an hour ago.
Though his web presence is blank for me at the moment:

https://www.janknepper.com
February 06, 2018
On Tuesday, 6 February 2018 at 14:05:46 UTC, Seb wrote:
>
> Vladimir already did so an hour ago.
> Though his web presence is blank for me at the moment:
>
> https://www.janknepper.com

Works for me again.

February 06, 2018
On Tuesday, 6 February 2018 at 14:32:41 UTC, Jakub Łabaj wrote:
> On Tuesday, 6 February 2018 at 14:05:46 UTC, Seb wrote:
>>
>> Vladimir already did so an hour ago.
>> Though his web presence is blank for me at the moment:
>>
>> https://www.janknepper.com
>
> Works for me again.

I also had this happen yesterday. dlang.org worked, dlang.org/phobos and other deeper urls failed. Only on Chrome, and it worked again after I restarted Chrome.

--
  Simen
February 06, 2018
On 02/06/2018 09:05 AM, Seb wrote:
> On Tuesday, 6 February 2018 at 13:42:18 UTC, Martin Tschierschke wrote:
>> On Tuesday, 6 February 2018 at 13:31:23 UTC, Seb wrote:
>>> On Tuesday, 6 February 2018 at 13:18:26 UTC, Jakub Łabaj wrote:
>>>> On Tuesday, 6 February 2018 at 10:05:52 UTC, Martin Tschierschke wrote:
>>>>> Chromium: ERR_SSL_PROTOCOL_ERROR
>>>>>
>> [...]
>> Please contact the owner of the website to inform him of
> 
> Vladimir already did so an hour ago.
> Though his web presence is blank for me at the moment:
> 
> https://www.janknepper.com

That is because that websites still uses HTML frames... :-)

Too busy doing many other things that the website is seriously lagging...

« First   ‹ Prev
1 2