Proxy connected but no internet: check setup, authentication and DNS
Updated:
When you set up a proxy and lose internet access, the most common cause is configuration: a wrong port, username and password swapped, the wrong proxy type selected, or a system proxy still switched on after you stopped using it. Less often the problem is authentication, DNS failing through the proxy, a firewall or antivirus blocking the proxy port, or a proxy that has expired. The quickest route is to check in order from easy to hard, with each step ruling out a group of causes. This guide gives you that checklist plus the common error messages and what they mean.
First: turn the proxy off and check your base connection
Switch the proxy off and open any website. If it still fails, your own network is the problem and the proxy is just caught in the middle. If sites load fine without the proxy, the issue lies with the proxy or its setup. A common trap is a Windows system proxy left on after you finished with it, which cuts off every browser; the guide to turning off a proxy shows where to check.
Configuration checklist
VinaProxy proxies are delivered as ip:port:user:pass. Most no-internet cases come from splitting those four parts incorrectly when typing them into software.
- IP and port: the port is the number after the first colon. Do not paste the whole line into the IP field.
- Proxy type: choose HTTP or HTTPS. Selecting SOCKS4 or SOCKS5 will fail because the proxy does not speak that protocol.
- Username and password: the third part is the username, the fourth is the password. Make sure no stray spaces came along when copying.
- Special characters: in URL form
http://user:pass@ip:port, any@,:or#in the password must be URL-encoded. - Bypass list: make sure the Windows bypass field or your extension has no odd rule catching all traffic.
- Expiry: check the dashboard to confirm the proxy is still active. An expired proxy stops working until it is renewed.
Test with curl to separate software issues
One curl command gives a clear answer that does not depend on any browser or extension:
curl -v -x http://user:pass@ip:port https://api.ipify.org
If it returns the proxy IP, the proxy works and the fault is in the software you are configuring. If it fails, the -v output shows each step so you can match it against the table below. You can also run a quick web-based check with the proxy checker.
Read the error message to locate the fault
| Message | Meaning | Fix |
|---|---|---|
| 407 Proxy Authentication Required | The proxy accepted the connection but rejected the credentials | Re-enter username and password; see the 407 error guide |
| Connection refused | Nothing is listening on that port, or the port is wrong | Recheck the port and that the proxy is active |
| Timed out | Packets never reach the proxy | Check firewalls or office networks; try another network |
| ERR_PROXY_CONNECTION_FAILED | The browser cannot reach the proxy | See ERR_PROXY_CONNECTION_FAILED |
| ERR_TUNNEL_CONNECTION_FAILED | The proxy is reachable but the HTTPS tunnel failed | Check authentication and proxy type |
| Could not resolve host | The domain name could not be resolved | Check DNS, see below |
DNS: why sites cannot be found even with a proxy
With an HTTP/HTTPS proxy, the browser sends the hostname to the proxy and the proxy resolves it, so your local DNS usually does not affect pages loaded through the proxy. DNS can still cause trouble when your software resolves the name itself before contacting the proxy, when a removed VPN left broken DNS settings behind, or when your hosts file blocks a domain.
Test resolution without the proxy using nslookup example.com. If it fails, reset system DNS to automatic or a public resolver and clear the cache with ipconfig /flushdns on Windows. Background on DNS is in DNS leaks explained.
Firewalls, antivirus and office networks
Many office, school, café and public Wi-Fi networks block outbound connections on uncommon ports. The browser hangs, then times out. Try the same proxy over a phone hotspot: if it works there, your usual network is blocking the port. Antivirus and local firewalls can also block a browser from connecting to an unfamiliar port; pause them briefly to test, then add an exception rather than leaving protection off. More detail is in checking the proxy and firewall.
Still stuck: what to send support
If curl fails from several networks and the proxy is active, open a ticket with the proxy IP, the full curl -v error, the network you used and the time of the test. Support runs 24/7, and technical faults on the provider side are handled under the refund policy.
Frequently asked questions
Every browser lost internet after I enabled a proxy. How do I undo it?
Open the system proxy settings and switch off the proxy server option, or disable the proxy extension, then reopen the browser.
The proxy says connected but pages will not load. Why?
Usually authentication or the wrong proxy type. Recheck the username and password and make sure you chose HTTP or HTTPS rather than SOCKS.
The proxy works at home but not at the office. Why?
Office networks often block outbound traffic to the proxy port. Test over mobile data to confirm, then ask your network admin if you need it there.
Do I need to change DNS when using an HTTP proxy?
Usually not, because the proxy resolves hostnames. Only look at DNS when the error says the host cannot be resolved or your software resolves names itself.
Do I lose the IP when my proxy expires?
An expired proxy stops working. Renew it in the dashboard before it expires to keep the same IP.
Dedicated proxies with 24/7 ticket support
Dedicated IPs delivered in a clear ip:port:user:pass format, usually activated automatically within minutes of payment.
See pricing