The the page for forum.vodafone.ro is stuck?

[Caspy7]

I tried doing a scan of https://forum.vodafone.ro/t5/Acoperire/Frecventa-telefon/m-p/136101 and it was taking a very long time. Eventually I tried reloading the page and this page only ever says "Loading Results".
So I'm wondering if there is a bug or something is "stuck".

[onpaws]

Right now for me one site works normally, but the site I'm more interested unfortunately just hangs here...

[floatingatoll]

Is the site you’re having trouble scanning “forum.vodafone.ro”? That server closes the connection when the root URL is fetched, which may be preventing the scanner from scanning that site. % curl -v https://forum.vodafone.ro/ * Trying 81.12.132.53:443... * Connected to forum.vodafone.ro (81.12.132.53) port 443 (#0) * ALPN, offering http/1.1 * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 * ALPN, server did not agree to a protocol * Server certificate: forum.vodafone.ro * Server certificate: DigiCert SHA2 Secure Server CA * Server certificate: DigiCert Global Root CA

GET / HTTP/1.1 Host: forum.vodafone.ro User-Agent: curl/7.71.1 Accept: */*

* SSLRead() return error -9806 * Closing connection 0 curl: (56) SSLRead() return error -9806

[onpaws]

I was using a different one.
Same behavior now - certain sites work normally, the one I'm trying to use, just hangs

[floatingatoll]

Note that the scanner will only attempt to scan the root of the site, never a specific URL — you should be entering a hostname into the scanner, without http: or https: or // or any of that. Such as: forum.vodafone.ro If that's the case, and the site you're trying to scan has not been intentionally configured to be IPv6-only nor TLS1.3-only, then it's hard to say what's wrong without knowing which site is breaking for you.

…

On Thu, Jul 23, 2020 at 5:05 PM Pat ***@***.***> wrote: I was using a different one. Same behavior now - certain sites work normally, the one I'm trying to use, just hangs — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#226 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWUDHYIUJU6LM3MAU56JDR5DF5TANCNFSM4OJ72BTA> .

[onpaws]

Thanks for the quick response. Hm, I asked around a bit and learned the domain I'm trying is being managed by CloudFlare. I'm not sure they force TLS 1.3 only (would that break Observatory?) but I could imagine they're doing other 'best practice' type things....

[floatingatoll]

They do neither of those things unless you seek them out and enable them, so you probably haven't. (If you're not the site administrator, you'd have to ask them, or check with other tools.)

…

On Thu, Jul 23, 2020 at 5:12 PM Pat ***@***.***> wrote: Thanks for the quick response. Hm, I asked around a bit and learned the domain I'm trying is being managed by CloudFlare. I'm not sure they impose TLS 1.3 only (would that break Observatory?) but I could imagine they're doing other 'best practice' type things.... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#226 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWUDFTXBGZALU2R5A7VOTR5DGXZANCNFSM4OJ72BTA> .

[onpaws]

Not 100% sure why, but this seems to have resolved itself. Thanks for your help @floatingatoll !