JuergenAuer Posted Tuesday at 02:39 PM Share Posted Tuesday at 02:39 PM Now it starts to be crazy. Local FireFox 131.0.3: No problem. FireFox from the DbServer (Server, who is used with check-your-website), 132.0.1: Problem - "Gesicherte Verbindung fehlgeschlagen" (same as older) Local Download (old own tool): D:\temp>download http://spacedock.info/ -h Connection: keep-alive Content-Language: en Content-Length: 2445 Cache-Control: no-store Content-Type: text/html Date: Tue, 05 Nov 2024 14:00:13 GMT Location: https://spacedock.info/ Server: 52K-CDN Via: http/1.1 localhost (52K) Status: 301 MovedPermanently 195,99 milliseconds 0,20 seconds D:\temp>download https://spacedock.info/ -h Vary: Cookie,Accept-Encoding Permissions-Policy: interest-cohort=() Age: 0 Connection: keep-alive Content-Length: 26198 Content-Type: text/html; charset=utf-8 Date: Tue, 05 Nov 2024 14:00:15 GMT Set-Cookie: session=; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure; HttpOnly; Path=/; SameSite=Lax Server: 52K-CDN Via: 1.1 spacedock.info, http/1.1 localhost (52K) Status: 200 OK 302,67 milliseconds 0,30 seconds No problem connecting http + https. Same from the DbServer (with a small older Download) e:\sd-db>download http://spacedock.info/ -h Connection: keep-alive Content-Language: en Content-Length: 2445 Cache-Control: no-store Content-Type: text/html Date: Tue, 05 Nov 2024 14:25:53 GMT Location: https://spacedock.info/ Server: 52K-CDN Via: http/1.1 localhost (52K) Status: 301 MovedPermanently e:\sd-db>download https://spacedock.info/ -h Error (1): The request was aborted: Could not create SSL/TLS secure channel. SecureChannelFailure 3 The 3 indicates, that the server doesn't send a complete answer. Same server, with a newer download: No Problem! e:\sd-db\temp>download http://spacedock.info/ -h Date: Tue, 05 Nov 2024 14:27:23 GMT Connection: keep-alive Via: http/1.1 localhost (52K) Server: 52K-CDN Cache-Control: no-store Location: https://spacedock.info/ Content-Type: text/html Content-Language: en Content-Length: 2445 Status: 301 MovedPermanently 184.87 milliseconds 0.18 seconds e:\sd-db\temp>download https://spacedock.info/ -h Date: Tue, 05 Nov 2024 14:27:25 GMT Server: 52K-CDN Content-Type: text/html; charset=utf-8 Content-Length: 26198 Vary: Cookie,Accept-Encoding Set-Cookie: session=; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure; HttpOnly; Path=/; SameSite=Lax Via: 1.1 spacedock.info, http/1.1 localhost (52K) Permissions-Policy: interest-cohort=() Age: 0 Connection: keep-alive Status: 200 OK 285.21 milliseconds 0.29 seconds That's completely crazy, never seen such a difference between two own download - versions. Rechecked your ip address. There is an "Accelerator" on your ip address - https://95.217.59.158/ Is there the SSL connection termination? If yes, is it possible do deactivate that tool (temporary)? Manual rechecked with the command inside check-your-website: No problem, no error. Normally, if download fails, check-your-website fails too. That would indicate a SSL problem, because the command line tool and the code of check-your-website use the same Windows - SSL - libraries. Quote Link to comment Share on other sites More sharing options...
Iapetus7342 Posted Wednesday at 04:22 PM Share Posted Wednesday at 04:22 PM Still seems to be broken Quote Link to comment Share on other sites More sharing options...
Valentin Gosu Posted Friday at 06:12 PM Share Posted Friday at 06:12 PM Hi folks, Firefox developer here. We received Bug 1928600 - spacedock.info - "Secure connection failed" when accessing the page and diagnosed that it's triggered by SETTINGS_NO_RFC7540_PRIORITIES from RFC 9218 Extensible Prioritization Scheme for HTTP. What I'm seeing in wireshark is that Firefox is sending this in the HTTP/2 SETTINGS packet, and spacedock.info is sending a GOAWAY with PROTOCOL_ERROR(1). Is this error coming from the CDN or the target server? For Firefox users out there, you can avoid it by setting `network.http.http2.send_NO_RFC7540_PRI` to false in about:config. Quote Link to comment Share on other sites More sharing options...
Cheesecake Posted Friday at 07:28 PM Share Posted Friday at 07:28 PM 1 hour ago, Valentin Gosu said: For Firefox users out there, you can avoid it by setting `network.http.http2.send_NO_RFC7540_PRI` to false in about:config. Thanks, that works. Quote Link to comment Share on other sites More sharing options...
Errol Posted 20 hours ago Share Posted 20 hours ago That fixed it for me too; thanks. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.