Connection showing not secure

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: localhost and connekted.pagekite.me

I ran this command: certbot certonly --webroot -w D:\Development\Certbot\acme -d connekted.pagekite.me

It produced this output: You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry. etc

My web server is (include version): nginx 1.25

The operating system my web server runs on is (include version): windows 11

My hosting provider, if applicable, is: pagekite

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 2.6.0

Hello Everyone, I have recently been able to solve the problems with http/https and now the site is https everywhere including the html files but somehow it is still saying not secure. Most probably it being self signed?

and the warning in url

image

Additionally, for these reasons it is not loading in WebView of android.

You will never get a publicly trusted certificate for this name:
image

You can't use both of those names securely.

5 Likes

but, even when i look against connekted.pagekite.me/room1.html
image

It is still showing same issue. then how to solve the other one?

I get:

3 Likes

I can open your page without any issues.

The issue lies with the antivirus software you're using, you may want to complain about it to them.

I'd remove this piece of software altogether

2 Likes

No issues?
The link to the "upgrade" is:
Pagekite - TLS Certificate Bug

5 Likes

Well, at least without issues that the OP seems to be experiencing.

3 Likes

try with connekted.pagekite.me/house

No but same site,

  1. wont even load in webview and
  2. show similar not secure warning in android chrome

So you're getting the same error that's on Rudyʼs screenshot or the Kasperskyʼs one?

2 Likes

No im not getting that error , kaspersky one on pc. and no explicitly mentioned error on android, page wont load in web view

actually you are correct this would load sometimes and sometimes it wont. specially with mobile hotspots(cg-nat) so i think the problem is with pagekite.

But, if we ignore this for a while and focus on the localhost/house or [ip]/house shouldnt we not get this not secure message there?

No, that's expected, since the certificate doesn't certify localhost domain name as well as IPs. Perhaps this will be helpful:

4 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.