#@gerhard one thing I've noticed is that
1 messages · Page 1 of 1 (latest)
Can you share an httpstat https://daggerverse.dev ?
This is what it should look like:
I'm not there right now, but can do from my home location.
curl -Lvo /dev/null https://daggerverse.dev would also help
~ ➤ httpstat https://daggerverse.dev
Connected to 18.211.147.51:443 from 192.168.0.65:58992
HTTP/2 200
date: Mon, 17 Jun 2024 16:39:45 GMT
content-type: text/html; charset=utf-8
link: <https://daggerverse.dev/>; rel="canonical"
vary: Accept-Encoding
Body stored in: /var/folders/s4/xyj9q5ps2ys3rc9nsps1v20m0000gn/T/tmp9resq42l
DNS Lookup TCP Connection TLS Handshake Server Processing Content Transfer
[ 36ms | 74ms | 169ms | 265ms | 299ms ]
| | | | |
namelookup:36ms | | | |
connect:110ms | | |
pretransfer:279ms | |
starttransfer:544ms |
total:843ms
LGTM!
~ ➤ curl -Lvo /dev/null https://daggerverse.dev 👇
Yes, that looks correct.
This is the reference for certs: https://www.ssllabs.com/ssltest/analyze.html?d=daggerverse.dev&s=18.211.147.51&latest
Here's HubSpot getting hit by the over-agressive security I see at my grandmother's place: https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Comcast-xFi-Advanced-Security-blocklist/m-p/842658
As a comcast user on the east coast I ran into this issue in the past. Last time it was a firewall update on their routers. I would reach out to hubspot support to let them know. Nothing we can do from the community side.
Looks like they filed a bug with Comcast/Xfinity. Wonder if it worked...we should try in case other users are affected.
Unclear if it's something about our certs, name, response that has us flagged. Could affect other ISPs who use similar firewall gear.
Yes, that might be worth doing. That last xfinity thread is 4 years old, wondering if it still applies today. From what I hear, Comcast is hard to love as an ISP.