Direct answer
For the TP-Link Archer AXE75 router, provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated. First, test tunnel status and endpoint reachability on one client.
What this covers
- TP-Link Archer AXE75 router (Archer AXE75)
- TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary.
- The specific fault this record addresses: VPN client or server will not connect
What it does not cover
- ×The same symptom on a different TP-Link product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
A VPN client app cannot connect or breaks other traffic
What separates it A single device's VPN app fails to connect, or once connected some sites or local devices stop working.
How to confirm Test the VPN app on another network to separate the app from your router; local-device access breaking while connected is normal VPN routing, adjusted with split-tunnelling in the app.
- 2
A router-level VPN client is misconfigured
What separates it The router routes all traffic through a VPN provider and connections are slow, failing, or leaking.
How to confirm Verify the router VPN's credentials, server and kill-switch settings; a router VPN affects every device at once, so a bad config takes the whole network down.
- 3
An inbound VPN server (to reach home) is unreachable
What separates it You cannot connect back to your home VPN server from outside.
How to confirm Confirm the server's port is forwarded and that the line is not behind carrier-grade NAT — an inbound VPN needs a reachable public address, exactly like port forwarding.
- 4
An MTU or protocol mismatch is dropping the tunnel
What separates it The VPN connects but stalls on large transfers or specific sites.
How to confirm Lower the MTU or switch the VPN protocol per the provider's guidance; an MTU that is too high for the tunnel silently drops large packets.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Which VPN you mean: a client app, a router-level VPN client, or an inbound home VPN server.
- Whether it fails to connect at all, or connects then breaks specific traffic.
- For an inbound server: whether the port is forwarded and the line has a public IP.
Establish which of the three VPN roles is involved
ReversibleClient app, router-level client, or inbound server — the fixes barely overlap.
Test a client-app VPN on another network to isolate it
ReversibleSeparates the app from your router and line.
For a router VPN, verify credentials, server and kill-switch
ReversibleA router VPN misconfig takes down every device at once.
For an inbound server, confirm the forward and a public IP, and tune MTU
ReversibleAn inbound VPN needs a reachable address; MTU mismatches drop large transfers.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- Archer AXE75. TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary.
- Wi-Fi 6E tri-band router (single unit)
- A Wi-Fi 6E (AXE) router adding 6 GHz on top of 2.4/5 GHz. 6E/6 GHz needs Wi-Fi 6E/7 clients; older devices use 5/2.4 GHz normally.
- 6 GHz short-range + WPA3
- 6 GHz is short-range and needs WPA3; devices drop to 5 GHz at distance. It is 6E, not Wi-Fi 7 — a Wi-Fi 7 feature will not appear.
- Managed by Tether app or web
- TP-Link Tether app or web admin.
- Symptom boundary
- This record covers TP-Link Archer AXE75 router when it VPN client or server will not connect. A different symptom on the same hardware, or this symptom on a different TP-Link product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Do not disable a router VPN's kill-switch to 'fix' connectivity — that silently leaks your traffic unencrypted. Resolve the tunnel instead.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. TP-Link publishes this as "How to Set Up OpenVPN on a TP-Link Router to access your home network". TP-Link's VPN server and client setup on the router. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and Archer AXE75 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My TP-Link Archer AXE75 6 GHz band isn't visible on my phone.+
Only Wi-Fi 6E and Wi-Fi 7 phones and laptops can see 6 GHz — a device without a 6 GHz radio simply will not show that network, which is normal. Confirm the 6 GHz band is enabled and WPA3 security is on (6 GHz requires it), and join it close to the router since 6 GHz has short range. Older devices staying on 5/2.4 GHz is expected behaviour, not a fault.
My VPN connects but then some things stop working.+
That is usually the VPN's routing rather than a fault. When a VPN is active it sends your traffic through the tunnel, which can cut off local devices (a printer, a NAS) or trip up sites that dislike the VPN's exit. Use split-tunnelling in the app to keep local and trusted traffic off the tunnel. If large transfers specifically stall, it is often an MTU that is too high for the tunnel — lower it per your provider's guidance.
Does this answer apply to every TP-Link model?+
No. It is scoped to Archer AXE75. TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary.
What should I record before troubleshooting VPN or tunnel?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing VPN, tunnel. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Protect keys and preserve emergency/admin access.
Answer for the exact device and software version shown above.