Ipsec VPN site-to-site it doesn't work anymore, it doesn't connect anymore from today

I have 2 controllers with 2 sites each, I have Ipsec vpn connections between locations, since this morning they no longer connect either manually or automatically. I didn't make any changes in any of the controllers, they just disconnected and don't reconnect, I redid the settings, I tried on automatic, nothing just doesn't connect, and the worst thing is that absolutely nothing appears in the logs!. I don't know what else to do, I restarted the controller, I restarted routers, but nothing. I mention that I have 3 Er605 routers and a router ER706W. A controller is OC200 and a controller is software on an on-premise server, I mention that there are 4 locations in total, 3 locations have ER605 routers, and one location has ER706W.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
support@tp-link.com
It's the weekend so you probably won't get any answers until Monday.
Use this thread as a reference so you don't have to rewrite everything :-)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @Sadiqus
First, please let us know the following to understand your VPN config:
1. did you create IPsec tunnel for all the 4 sites, and all of them can communicate with each other?
2. Is the Internet of the 4 sites still working?
3. Go to Insighs > VPN Status, are the VPN tunnels still showing on this page?
4. Did there any change on the outbound IP addresses of the four sites?
- Copy Link
- Report Inappropriate Content
1. So, on the OC200 controller (2 locations) I have a connection (tunnel) with the second location and a second connection with location 3 (which is on another controller, it is a software controller that has 2 managed locations), on the second controller (software) I have a connection with location 4 which is on the same controller.
2. Yes, the internet works perfectly in all 4 locations.
3. On Insights>VPN Status doesn't show any connection just like in your screenshot.
4. There were no changes to IPs, I have 4 fixed IPs from my ISP.
I hope this outline will make you understand better.
- Copy Link
- Report Inappropriate Content
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID250216447, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
@Vincent-TP @MR.S
Over the weekend it only came back from one direction, the connection appears at Insights>VPN Status, but sometimes it only works from one direction, sometimes not at all. also started to appear in the logs: Gateway IPsec Module Information
WAN2: Lifetime of the SA created in phase 1 of IKE negotiation expired. (Peers=94.53.244.211<->94.53.106.244)
Feb 10, 2025 10:31:21
Gateway IPsec Module Information
WAN2: Lifetime of the SA created in phase 2 of IKE negotiation expired. (Peers=94.53.244.211<->94.53.106.244, SPI=3244311518)
Feb 10, 2025 10:31:14
or like:
Gateway IPsec Module Information
WAN2: Phase 1 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14)
Feb 09, 2025 09:48:06
Gateway IPsec Module Information
WAN2: Phase 1 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14)
Feb 09, 2025 09:48:04
Gateway IPsec Module Information
WAN2: IPsec connection was disconnected passively. (Peers=94.53.244.211<->94.53.231.180)
Feb 09, 2025 09:59:50
Gateway IPsec Module Information
WAN2: Enable DPD successfully. (DPD-Interval=30, Peers=94.53.244.211<->94.53.231.180)
Feb 09, 2025 09:49:41
- Copy Link
- Report Inappropriate Content
to me it seems like it's wrong Pre-Shared Key or proposal settings. try setting up the tunnel like this on both sides. let both be initiator
Make sure you have configured local network on remote network correctly on both sites.
double check that the Pre-Shared Key is the same on both sites
- Copy Link
- Report Inappropriate Content
@MR.S
it's not connecting, both are initiator
Gateway IPsec Module Information | WAN2: Phase 2 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14) |
Feb 10, 2025 15:08:08 | ||
Gateway IPsec Module Information | WAN2: Phase 2 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14) |
Feb 10, 2025 15:08:06 | ||
Gateway IPsec Module Information | WAN2: Phase 2 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14) |
Feb 10, 2025 15:06:20 | ||
Gateway IPsec Module Information | WAN2: Phase 2 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14) |
Feb 10, 2025 15:05:44 | ||
Gateway IPsec Module Information | WAN2: Phase 2 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14) |
Feb 10, 2025 15:04:49 | ||
Gateway IPsec Module Information | WAN2: Phase 2 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14) |
Feb 10, 2025 15:04:12 | ||
Gateway IPsec Module Information | WAN2: Phase 2 of IKE negotiation failed. (Peers=94.53.244.211<->94.53.231.180, Error=14) |
Feb 10, 2025 15:03:19 |
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@MR.S
I have seen the error but i corect it! still nothing no connection!
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 555
Replies: 28
Voters 0
No one has voted for it yet.