<!– BODY START –>
Few error messages are as simultaneously specific and unhelpful as "connection refused". Unlike a timeout, which suggests the browser could not find anything at all, a refusal means the browser reached a device and was actively turned away. Something, somewhere, said no. That precision is actually good news: it narrows the problem considerably. When a PC browser reports "connection refused" while trying to open X-plore's Wi-Fi sharing, the cause is almost always one of a short list — the sharing session stopped, the address or port is wrong, a firewall intervened, or the network itself is blocking the connection. This guide works through that list in the order most likely to fix your problem, so you can stop guessing and start transferring.
Refused is not the same as timed out
It helps to understand what the browser is telling you, because the two most common errors point in different directions. A timeout, or "site can't be reached" after a long wait, usually means the browser's request never arrived anywhere — the phone may be asleep, the devices may be on different networks, or AP isolation may be discarding the traffic. A refusal, by contrast, arrives quickly. The browser connected to something and received an explicit rejection. That usually means the network path works but the service on the other end is not accepting connections on that port right now.
In practice, the most common cause of a refusal is beautifully mundane: the sharing session on the phone is no longer running. X-plore's Wi-Fi sharing may have stopped because the phone's screen locked and the system reclaimed resources, because you navigated away and the app was closed, or because the phone restarted its Wi-Fi connection and the old session ended. The PC browser, still holding yesterday's address or this morning's port, knocks on a door that is no longer open, and the network stack answers with a refusal. Restarting sharing and reading the fresh address fixes this more often than any other single step.
Step one: restart sharing and verify the live address
Begin on the phone. Open X-plore and check whether Wi-Fi sharing is still running. If it is, stop it and start it again — a clean restart removes any stale state from a half-ended session. When sharing restarts, read the address it displays right now, including the port number, and compare it character by character with what is in the PC browser's address bar. Pay particular attention to the port, the number after the colon. If X-plore restarted with a different port than the one in the browser, the browser is knocking on the wrong door, and a refusal is exactly what you would expect.
Type the fresh address into the browser manually rather than relying on autocomplete, history, or a bookmark. Browsers helpfully suggest old addresses, and an old address with an old port is a reliable way to reproduce the same error. If the fresh address works, you are done, and the lesson for next time is to always read the address from X-plore at the start of a session rather than reusing one from before.
Step two: check the phone itself
If a fresh address still refuses, look at the phone's state. Is the phone awake, with X-plore visible? Some phones aggressively suspend background network services when the screen locks, and a sharing server is exactly the kind of service that gets suspended. Keep the phone awake and X-plore in the foreground while testing. Is the phone on the same Wi-Fi network as the PC? Check the network name on both devices, since a phone that drifted onto a guest network or a neighbour's network will present a different address on a different segment, and connections to its old address may be refused by whatever now holds that address.
Also consider battery optimisation. If your phone has a setting that restricts an app's background activity, it may stop the sharing server even while the app appears open. Exempting X-plore from battery optimisation for the duration of the transfer is a reasonable temporary measure. Similarly, if a VPN is active on the phone, it can interfere with local connections by routing traffic away from the local network; turning the VPN off for the transfer and retrying is a quick test that either clears the VPN as a suspect or identifies it as the cause.
Step three: check the PC's firewall and network profile
When the phone side checks out, the PC side is the next suspect. Desktop firewalls, including the built-in Windows firewall and third-party security suites, sometimes block incoming or outgoing local connections they have not seen before. The tricky part is that they often do this silently: the browser reports a refusal, and no firewall popup explains why. As a diagnostic step, temporarily disable the PC's firewall — briefly, and only on a trusted home network — and retry the address. If it works with the firewall off, you have found the cause, and the proper fix is to add an exception for the browser or for local network traffic rather than leaving the firewall disabled.
Closely related is the PC's network profile. On Windows, a network classified as "public" is treated with much stricter rules than one classified as "private", and local device-to-device traffic is one of the things that can be blocked on a public profile. If your home network is set to public — which sometimes happens after a router change or a Windows update — changing it to private often resolves refusals immediately. On a genuinely public network, such as a café, you should not change this setting to bypass protections; use a phone hotspot instead, where the network is yours and the profile question does not arise.
Step four: rule out port and address conflicts
A refusal can also occur when the address points at the wrong device entirely. Local IP addresses are reused: if your phone held a particular address yesterday and a different device holds it today, the browser's request reaches that other device, which is not running any file sharing service and therefore refuses the connection. This is why reusing old addresses is so unreliable. Restarting sharing on the phone and using the freshly displayed address eliminates this possibility, but if the problem persists, check the phone's current IP address in its Wi-Fi settings and confirm it matches the address X-plore is showing. If they disagree, the phone's network connection has changed underneath the sharing session, and restarting both Wi-Fi and sharing will bring them back into agreement.
Another, rarer cause is a port conflict: another service on the phone or network already using the same port. Restarting sharing usually selects a working arrangement, but if refusals persist across restarts, rebooting the phone clears any stuck service holding the port. A reboot is a blunt instrument, but it is fast, and it resolves a surprising number of "nothing changed but it stopped working" network problems.
Step five: consider the network itself
If every device-side check passes and the refusal persists, the network is the remaining suspect. AP isolation, discussed in detail in our guide to shared Wi-Fi, usually produces timeouts rather than refusals, but some routers and access points actively refuse local connections rather than silently dropping them, so isolation remains a possibility on managed networks. The test is the same as before: try the transfer on a network you control, or via a phone hotspot. If it works there, the shared network's policy is the cause, and no device setting will override it.
Similarly, some corporate and school networks run client firewalls or intrusion prevention systems that refuse unexpected local connections. On such networks, the correct response is not to fight the policy but to use an approved method — a hotspot, a cable, or an authorised file-sharing service. Attempting to bypass a workplace network's controls can violate its acceptable-use policy, and the hotspot route achieves the transfer without touching those controls at all.
A systematic order that saves time
When you meet a refusal, resist the urge to change five things at once. Change one thing, test, and note the result. The order that resolves most cases fastest is: restart sharing and use the fresh address; confirm the phone is awake and on the same network; disable any phone VPN temporarily; check the PC firewall and network profile; reboot the phone if the problem survives restarts; and finally test on a hotspot to isolate the network itself. Most refusals are fixed in the first two steps. The later steps exist for the stubborn minority, and following them in order means you will find the cause rather than stumbling around it.
Once the connection works, finish the transfer promptly and stop sharing when you are done. A working session is not a permanent one: phones sleep, addresses change, and networks shift. Treat each transfer as a fresh session — start sharing, read the address, transfer, stop sharing — and "connection refused" will become a rare visitor rather than a regular one.
<!– BODY END –>
Frequently asked questions
What does "connection refused" actually mean?
It means the browser reached a device on the network and that device actively rejected the connection, usually because no service is listening on that address and port — for example, because sharing has stopped or the port changed.
Why does restarting Wi-Fi sharing fix it so often?
Restarting sharing gives you a fresh, currently valid address and port, and clears any stale session state. Old addresses and ports are the most common cause of refusals.
Can my PC firewall cause a connection refused error?
Yes. Firewalls can silently block local connections. Temporarily disabling the firewall as a test identifies it; the proper fix is adding an exception, not leaving the firewall off.
Does a VPN on my phone cause connection refused?
It can. A VPN may route local traffic away from your home network, breaking local sharing. Turning the VPN off for the transfer is a quick and reliable test.
What if it works on a hotspot but not on the office Wi-Fi?
That points to the office network's policy, such as client isolation or a local firewall rule. Use the hotspot or another approved method rather than trying to bypass the network's controls.


