Netgate 3100...openvpn server...cannot connect
-
The Netgate 3100 openvpn server was working fine as of yesterday as i was able to remotely get in (i am on work travel now)
But now suddenly, i cannot get in.
I asked my young son to reboot the 3100 and she did, but i still cannot get in.
He said, after the reboot is completed, he sees three LEDs flashing initially and then just one Blue LED flashing eventually.
That is how it should be so i guess the 3100 boots u fine.
All networks in the house is working good including wifi etc.The config file is backed up regularly by Netgate to their cloud (i suppose).
Any suggestions on how i can get back in?
-
You can only attempt to access it remotely?
Can you get anyone to login and make sure the OpenVPN server is running? Or if there are any alerts showing?
What error is shown at the client when you try to login?
Is it possible any of the certs expired?
Steve
-
@stephenw10
Unfortunately i am only remote this week.
I am not sure people around me, at home knows pfsense etc but this could be the only option.
here is no reason for openvpn to stop running. I used it last week remotely and it worked fine.
The client says"connection refused"
My certs are in auto renewal mode with cron taking care of it.My fear is the Veriozon FIOS IP address changed and pfsensedidn't update that to Cloudflare (my DNS) .
I don't know how often this DDNS updates cloudflare. I am no running a cron job for it. -
If it's configured in pfSense then it will update automatically if there is a change in the IP.
You can probably have someone behind pfSense google 'what is my IP' to get the current WAN IP and check it.
The client cert would not be updated automatically, that could have expired.
-
@caymann if there’s a PC there you could have someone help connect you remotely. There are a few free options. Windows has one built in, or there are third party sites like showmypc.com in a pinch. Google has their own Remote Desktop but it requires an install.
-
Yup good point. Chrome remote desktop works well enough in my experience.
-
I was able to solve this issue....looks like the IP address didn't get updated by the DDNS client...i found out by calling Verizon FIOS and cross checking the IP address with what Cloudflare (my Domain provider).
All is good now...back in the game.
Thank you for all of your support and ideas.
jim