B4J Question [ABMaterial] "Dangerous Site" Warning

[mangyun]

Hello,

i create webapp using abm. it contains approx 50pages.
but a few of them give my client warning "dangerous site" like below screenshot.

if they click visit "this unsafe site" everything works as it should.

i tried google safe browsing checker, but found no problem (maybe because to access that page, need to logged in first, hence no problem found by google, because it scan the first(login) page)

please give me some guidance on how to resolve this problem, where to start....

thanks.

 

[MichalK73]

Very strange.

I also have pages written in ABM with login and extended, but I have never had such problems.

Do you have any antivirus? Check on another browser.

 

[alwaysbusy]

This means Chrome does not trust your https certificate as a valid one.

 

[mangyun]

Very strange.

I also have pages written in ABM with login and extended, but I have never had such problems.

Do you have any antivirus? Check on another browser.

on my windows, just the usual windows defender. on client's mac, i don't know.

 

[mangyun]

This means Chrome does not trust your https certificate as a valid one.

-> its fine on most page.

-> i use lets encrypt as per the example

-> it only gives the red warning for a few pages, not all of my pages.

i request for a review from google
>> search.google.com/search-console
and they remove the warning. its ok for now, but its a reccuring problem.
it happens one time before, around a year ago.

i'm hoping someone have been dealing something like this, and able to give me some advice on what to look for to correct the problem.

 

[alwaysbusy]

What doe you see in the chrome console (network and security tab)? I found these post about similar problems with Lets Encrypt that may be helpful:

Certificate valid but flagged by Chrome as "Not secure"

I agree with regard to the Security tab, that one is also pretty good for mixed content.

community.letsencrypt.org

Chrome "Active content with certificate errors"

We recently updated our ZNC server (don't think this matters) with a new certificate to include a Subject Alternative Name (SAN) DNS field. It works now in incognito but my existing session shows the

stackoverflow.com

 

[mangyun]

secure and valid

maybe i should've check it (chrome console) when it is displaying the dangerous message , maybe it displayed another message back than.

i think i'll just have to wait for it to display the red dangerous page again to further check whats going on.

thanks alain and michal..