Date: October 17th, 2026 8:11 AM
Author: AZNgirl w/Penis discussing Interest Rates w/TT6
Excellent — this gives us a much clearer picture. AutoAdmit is responding successfully over HTTPS from your apartment Wi-Fi right now. Your `curl` output confirms that the TCP connection, TLS negotiation, and HTTP request all completed, and the server returned `HTTP/1.1 200 OK`.
## What we've established
| Component | Result |
| -------------------- | ------------------------ |
| DNS resolution | Working |
| TCP port 443 | Working now |
| TLS handshake | Successful |
| AutoAdmit web server | Returned HTTP 200 OK |
| TCP port 80 | Failed in previous tests |
The TLS renegotiation messages aren't necessarily errors; the request completed successfully despite them.
## So why does it work, then stop minutes later?
The original cause remains unresolved. The most useful possibilities now are:
1. Intermittent routing or packet loss between your apartment ISP and AutoAdmit's host.
2. Server-side filtering or rate limiting that temporarily affects your public IP.
3. Browser-specific behavior, such as a stale connection, cookies, or an extension—especially if `curl` continues to work while Chrome fails.
4. Different behavior on HTTP and HTTPS. Port 80 failing may be incidental if you use HTTPS, but it doesn't explain the earlier HTTPS timeouts.
## The next time Chrome fails
Don't change any settings yet. Run this single command immediately:
```
curl.exe -I --connect-timeout 8 https://www.autoadmit.com/
```
Interpret the result as follows:
- `HTTP/1.1 200 OK`: The site is reachable outside Chrome. Investigate Chrome, its proxy settings, extensions, or browser connection state.
- Connection timeout: The issue is below the browser layer, such as routing, filtering, or server availability.
- A response such as 403 or 429: Investigate server-side access restrictions or rate limiting.
One question that matters: when Chrome fails to load AutoAdmit, does it show `ERR_CONNECTION_TIMED_OUT`, or does the page just keep spinning? That will help distinguish a network timeout from a browser-side problem.
(http://www.autoadmit.com/thread.php?thread_id=5913301&forum_id=2...id#50193322)