Date: October 17th, 2026 8:11 AM Author: electric yarmulke house
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`.
- `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.
Date: October 17th, 2026 9:02 AM Author: haunting halford
God ur dumb
Someone is scraping the website which is essentially ddosing the server none of us were able to use it yesterday there is also a separate issue where rach has decided to ban certain vpns and there is a third issue (probably usa only) where certain isps have decided to block xo)