What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

BE88U - showing "Not Secure" since firmware update

greig2000uk

Occasional Visitor
Hi,
my BE88U has started to show "Not Secure" and "https ://www.asusrouter.com:8443/Main_Login.asp" while connecting using HTTPS and "Not Secure" with an explanation mark in white inside a triangle when using HTTP.
This just started last night and I have no clue how to fix.
I updated to the Asus latest firmware 3.0.0.6.102_39112 from 3.0.0.6.102_38152 and got a screen warning about being not secure and the option to continue using https, I did and got into the router GUI, but with the not secure warning.
I followed the help advice from asus on this screen warning also but nothing is moving the "Not Secure" from the address.

From here I installed the latest Merlin firmware but getting the same as above

Can this be fixed, is it an issue? What can I do to fix...

thanks
 
Re-upload the certificate to the client. Not really an issue.
I cant seem to get the certificate, under Administration>System>Local access Config to export to a .cert file, it exports as "cert_key" zip file and when extracted there are 2 files "cert.pem and key.pem"
what do i need to do here, i have no idea what these files are and righ clicking has no option to instal...
My set up is in the sceen grabs below.

1.jpg

2.jpg

3.jpg
 
Last edited:
Have you tried different browsers?
 
I don't what the fix is but a have workaround I been using in that scenario .

Go to the wan/ddns page.
In the http/ssl certificate section - select auto and apply.
Then select free cert from Let's Encrypt and then apply.

Usually I'm good till the next reboot.
 
I don't what the fix is but a have workaround I been using in that scenario .

Go to the wan/ddns page.
In the http/ssl certificate section - select auto and apply.
Then select free cert from Let's Encrypt and then apply.

Usually I'm good till the next reboot.
Thanks, ill give that a try tomorrow and report back
 
Thanks, ill give that a try tomorrow and report back
So this seems to work, though im not sure how i managed it, seems to want the certificate, which is now exportable after setting to auto and exports a "cacert_key" zip file with "cakey.pem and cert.crt" files inside, I used this cert.crt file.

4.jpg
So HTTPS seems ok, HTTP still "Not Secure"

Also seen this thread which tells me this is not just me with this problem....


It would be good to have some clear instructions on how to solve this once and for all, also i need to use lets encrypt as I have an FTP server on the USB port

any other advice appreciated
 

Attachments

  • 4.jpg
    4.jpg
    79.9 KB · Views: 9
Agreed.
"HTTP still "Not Secure"" is a product of the browser when credentials are exchanged. Not a lot can be done about this.
A little lateral thinking. Since you use ddns you can access your router locally using the ddns address, when using Let's Encrypt. Works that way on mine.
 
"Not Secure" with an explanation mark in white inside a triangle when using HTTP."
Gotcha. Mine does exactly the same, and has done for ages. Just use https, and disable http altogether if that suits you.
Nothing wrong here.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top