A security group or network ACL that allows your office IP but not the public internet makes an S3-backed site or its origin time out for everyone else.
A security group or network ACL that allows your office IP but not the public internet makes an S3-backed site or its origin time out for everyone else.
Review the security group's inbound rules for ports 80/443 and the bucket policy's public-read settings. Test from a network outside your allowlist before declaring it fixed.
AWS S3 has its own failure mode, but ERR_CONNECTION_TIMED_OUT has a wider set of causes. The most common one overall is: The origin server is down or the web server process has stopped.
Check the service is running and listening on the expected port, then restart it and confirm from outside the network.
An uptime probe from outside your network tells you whether the server is unreachable for everyone or only from where you are sitting — which is the first fork in every timeout diagnosis.
A security group or network ACL that allows your office IP but not the public internet makes an S3-backed site or its origin time out for everyone else.
Review the security group's inbound rules for ports 80/443 and the bucket policy's public-read settings. Test from a network outside your allowlist before declaring it fixed.
DNS resolved and the browser tried to open a TCP connection, but nothing answered before the timeout. The server is unreachable, overloaded, or a firewall is dropping the packets silently.