That annoying certificate error with HTTPS

[tnbtaylor]

I tried to find a useful solution, but could not.  Sorry if the solution is out there...I can't find it.

 

I'd like to use HTTPS with the NAS web access feature, but there is a certificate error every time you go into the site.  Its annoying and unprofessional.

 

Other than disabling the HTTPS/SSL function on web access (clearly that would resolve the problem), is there a way to not get the certificate error?  Family will freak out when they get the certificate error...

 

Please advise, Buffalo!!

Thanks.

[AngelsAbys]

The certificate is typically related to security settings of the Windows and/or OSX based system noticing that you are connecting to a secure site

[tnbtaylor]

AngelsAbyss wrote:

The certificate is typically related to security settings of the Windows and/or OSX based system noticing that you are connecting to a secure site

Thanks, but that's an odd reply. 

 

The certificate error indicates the web page certificate expired or was not valid.  Even if you add the site to the trusted site list in IE, you still get the certificate error.  I guess what I'm saying is why doesn't Buffalo update the web access firmware to allow HTTPS without certificate errors?  Otherwise, HTTPS is useless if no one trusts the site they are going to. 

 

Message to Buffalo:  Firmware updates are needed for the LS-W2.0TGL/R1.  3.10 is archaic!  Please help your valued customers!!!  The web interface is old and useless and HTTPS is ridden with certificate errors.

[AngelsAbys]

Valid question, I will forward this on to get a reply on this matter.  Previous answer was based on experimenting with a unit from 2 different neworks within the same building.

[davo]

FYI: (Yes it's me again) If you use firefox you have the option to save the cerificate.

 

This means you will only be prompted for it the first time you logon to Buffalo nas using HTTPS and from then after it shouldn't bother you. It's the same with alot of HTTPS sites i find. (Such as logging onto a mobile providers account etc)

[tnbtaylor]

Thanks Davo and AngelAbyss. 

 

I just thought it would be better if  HTTPS could be used without the ongoing certificate error using the most popular internet browser (IE).

 

Davo -- I got the DNS working!  Turns out, DynDns needed my public IP address (did not know that).  Its now pointing to Port 9000, since I cannot (with my router) forward port 8081 to port 9000.  In fact, even when I forward port 8081 to the NAS, it is not open (not sure if my cable modem or ISP is blocking port 8081??).  So, you still get the dreary/useless Buffalo WebAccess page when you log onto my DNS (wish I could change that).  I'm wondering how your (Davo) NAS server page looked so much nicer than my server page.  Apparently you have a better NAS or firmware than me? 

 

PS:  Davo, You were probably correct about me bricking my router given the directions and nightmare strories I read with people trying to flash DD-WRT onto this particular router.  Seems like it is not easy to accomplish and is 50/50 success at best...I humbly apologize...