The certificate error means the common name on the certificate does not match the domain name you are surfing to but what causes it is unclear. It could be anything from a false site to a problem with the rv130 or your isp, maybe you have a corrupt security software.
Have you checked for any firmware updates to the RV130 or tried to reinstall one your computers and see what happens. Also if you have the possibility try the RV130 on another internet service.
I could try to use the RV130 on my home network possibly and see what happens, but truthfully I'm not considering keeping this device that long if this problem keeps occurring.
Regarding the firmware, the latest version of the firmware is on the router. And I have, coincidentally, reinstalled several laptops in the past week that all had the problem before reinstalling and still have it after reinstalling.
We do have a piece of internet security software, which is kaspersky internet security, but disabling it doesn't help and secondly, we've had that long before we started using this router and the problem never occured then.
Is there at all a possibility that the router is causing this? If the answer is yes then I think I don't have any more time left to invest in looking for a cause and will just return the product and search for a new router. Preferably still a Cisco, but definitely another one than the RV130.
Hello, I have same problem about certificat and same router, a brand new Cisco RV130W. But I dont use yet VPN feature. My customer use too Kaspersky internet security.
Dont know if it's about the 'mariage' of rv130 and kaspersky but anyway kaspersky is very popular and if it's about that we should be a lot with this trouble.
I find a littlebit od to see on a cisco forum no answer about that ! And very disappointed, if I change a piece of shit router with a small business cisco to get more troubles and stress...
Well hope one cisco admin can answer us quick because it's professional customers not private user...
One thing you could try to at least rule out dns problems is to configure other dns servers, for example google public dns servers in the router dhcp scope as static dns :
Google dns1: 126.96.36.199
Google dns2: 188.8.131.52
I just googled "kaspersky ssl authentication error" and a lot came up so Kaspersky has had this problem before especially in Chrome. Try to uninstall Kaspersky and see what happens, on windows you can rely on Defender/MSE at least for the time it takes to see if Kaspersky is the problem.
If it is Kaspersky that causes it see if Kaspersky forums has anymore info on it.
Thanks for the suggestion. I did however, almost a week ago, changed the DNS's of our router to the Google DNS just to see if it would make a difference. Sadly it did not however.
In the meantime I will also look at the Kaspersky forums today and see if I can find anything helpful there.
Thanks for the info! I had the same problem with a RV220, and a couple of RV180's. I solved it by replacing them with routers from another company (that work properly)!
I had the problem on a RV130 a few firmware versions back, and switching to a RV180w eliminated the problem (operating for more than a year now).
A recent RV130W had SSL certificate browsing issues on implementation with the latest 184.108.40.206 firmware, but seemed to be ok after a full reset via the hardware reset button and has been working without reported issues at a new site. I also used the wizard during the second round of programming, vs my usual cancelling the wizard and doing all of the programming manually.
Regardless of whether the reset & wizard use eliminates the SSL issues, a new bug I've found on the RV130W causes all web browsing to go dead if the wifi is used heavily. This symptom can be easily recreated by doing large data transfers through a wifi-connected client using a utility like Totusoft's LAN Speed Test to a NAS. The data transfers do not go down, but web browsing stops working and no errors are reported in the router logs.
I've tried reconfiguring the wifi to various restricted modes vs the defaults (cutting support for B clients, disabling frame bursting, fixed vs auto channels etc) but nothing resolves the wifi load crashing web browsing via the gateway.
My test environment involved no use of the RV130W's DNS or DHCP (as both services were being provided by an external server) and access to the SMB share on the NAS is never lost, so the crash is happening in the gateway routing from the WAN vs the LAN. I normally use an RV320 (and have tested many other models and brands of routers) in this environment with zero stability issues in the WAN routing through the gateway.
In between going from the RV130 to an RV180W in the previous post, I tried a TP-Link TL-R600VPN v2 for kicks which booted extremely fast but would eventually crash and go completely offline with their final firmware release from Aug 2014. TP-Link support was pretty useless and to date never produced any newer firmware for it; for perspective, the site had about 20 desktop clients and misc mobile devices.
A previous Netgear router in the same office was reliable but slow and couldn't meet its rated 60Mb WAN routing spec, bottlenecking the connection with its limited WAN routing performance levels more and more as their firmware development continued.
The Netgear also had extremely buggy VPN support; Netgear support was terrible and eventually fixed the issue (when I got aggressive with them) in a never-released beta and then broke the VPN feature completely in their next generation of 4.x firmware for the device.
I have since used mostly RV180, RV130 and RV320 product lines, with the substantial issues being the RV130s (SSL browsing errors, port fwd'ing single ports as a range workaround, and now these wifi / WAN bugs) and a stability issue with early 1.3.1 firmware on the RV320s (which was latter pulled). For small office use, these product lines have been stellar in comparison.
I normally use separate wifi APs, so the token gesture wifi in these Cisco RV1x0W SMB products isn't usually worth anything to me unless the client's wifi needs are little to no priority, but it should at least function and not crash the basic routing functions...
I think the moral to this story is pretty clear. Cisco small buso esa range as the other brands like tplink and netgear are shite. Spend the extra cash and go for a real business solution from Cisco.