How can I tell if the issue is with the antidetect browser or the proxy?

The proxy shows green in my antidetect browser and seems to be working, but websites still won’t load. Any idea if it’s the browser or the proxy?

Try using the same proxy in a regular browser. If the sites still won’t load, it could be the proxy IP, DNS, or connection settings. If everything works fine there, check your antidetect browser’s profile and proxy configuration, or contact the antidetect browser support team directly.

90% it should be proxy but it could be both as well.. anyway your question is not much clear.. You didn't mention what kind of error it appear instead just saying won't load. anyway most of the time even finger print leaks if the proxy is clean enough sites are working.. try out with hotmail as i know hotmail is one of best site to check to see whether site is clean or not.. IMO

Your proxy setup is fine, but the proxy itself isn't 'clean'. Use a clean proxy, and then log in to all your accounts—you won't face any issues.

The green light in most antidetect browsers only means it could open a connection to the proxy, it doesn't prove traffic actually goes through. So I'd test outside the browser first. Run curl with the -x flag (userass@hostort) against any IP echo page from your terminal, and if that works but the browser doesn't, it's the profile.

Common culprits in the profile are a protocol mismatch (SOCKS5 entered as HTTP or the other way around), a wrong port, or DNS/WebRTC settings that don't match the proxy. Also look at the actual error instead of "won't load". Timeout means blocked or dead route, 407 means auth is wrong, 403 or a captcha page means the IP is flagged, and ERR_TUNNEL_CONNECTION_FAILED usually means the proxy refused the CONNECT.

If curl fails too then it's the proxy, and I'd ask the provider before touching browser settings.

Yeah, that green check in an antidetect browser doesn't always mean the proxy is working fine. Does this happen on every site or just some? If it's all of them, could be a proxy issue.

I would try a fresh profile in the same browser with the same proxy. If that works, I'd compare the profile settings before paying for new IPs.