📎 AI Summary:
The thread discusses issues with an SSTP VPN after relocating a server to a new location with a different external IP, with the original poster questioning whether a certificate issue might be causing the problem. A responder suggests that common problems after a server move include overlooked subnet configurations and recommends enabling server monitoring to diagnose issues, also mentioning that the VPN service itself could be at fault. Overall, the conversation centers on troubleshooting VPN connectivity problems following a server migration.
D

DarrenKentTec

New Member
Member details
Joined
Dec 3, 2021
Messages
1
Thread Author #1
Hi

We relocated our server to another town/city and now our sstp VPN doesnt work, all that has changed is a new external IP address, we have put a NAT rule in for 443 in the new firewall at the new office. Is this a certificate issue? Do you have to tell the certificate which exteral IP address it is to use?
 

Warfaree

Warfaree

Honorable Member
Member details
Joined
Apr 23, 2020
Messages
23
#2
During the process of moving to a new server, unexpected problems can always arise. Most likely, you forgot about some subnets. In general, you'd better enable server monitoring to collect statistics and track current problems. It is also possible that the problem is on the side of the VPN service itself.
 

You must log in or register to reply here.