SSL not Secure
-
Report number: JRLKRCTQ
Report date: 05/04/2023 14:31:10I use Litespeed CDN and everything work fine, CDN is connected, but the browser show NOT SECURE connection for 2 days. Please help me with it.
The page I need help with: [log in to see the link]
-
I can’t find any SSL problems with any browser. However, you should clean up your fonts. 168 fonts are definitely 150 fonts too many. This is also the reason why your site is so slow despite the cache.
If there’s no problem with the SSL why it appears to be Non Secure?
Where exactly do you see this?
On the desktop browser, in front of the URL box.
As already said I can’t see any hint that something would be not secure. I habe checked it in different browsers. Maybe you use any browser plugin that checks it?

As you can see here. Normally, it will show only the lock icon to tell us that the website we are browsing is secured.
Before I use this plugin, my website is secured. After I use your CDN and SSL, I got this Not Secure.
Could post a screenshot?
Screenshot already posted above.
https://www.dropbox.com/s/ei02hjkg55z54tu/Screenshot%202023-05-05%20at%204.06.27%20PM.png?dl=0
Which browser do you use?
Google Chrome
Sorry, I can’t confirm. If I use Chrome there are no errors.
may I know which node you have connected to ? please check the http response header, you should see one shows
x-qc-popHTTP/2200 content-type: text/html; charset=UTF-8 vary: Accept-Encoding x-dns-prefetch-control: on x-litespeed-tag: dce_HTTP.200 link: <https://www.79artstudio.com/wp-json/>; rel="https://api.w.org/", <https://www.79artstudio.com/wp-json/wp/v2/pages/7804>; rel="alternate"; type="application/json", <https://www.79artstudio.com/>; rel=shortlink x-litespeed-cache-control: no-cache cache-control: max-age=0 expires: Sat, 06 May 2023 01:48:17 GMT vary: User-Agent date: Sat, 06 May 2023 01:48:18 GMT server: LiteSpeed x-qc-pop: EU-DE-FKB-67 alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"root@v220221044927204975:~# curl -I -XGET --resolve www.79artstudio.com:443:45.132.244.92 https://www.79artstudio.com HTTP/2 200 content-type: text/html; charset=UTF-8 x-dns-prefetch-control: on link: <https://www.79artstudio.com/wp-json/>; rel="https://api.w.org/", <https://www.79artstudio.com/wp-json/wp/v2/pages/7804>; rel="alternate"; type="application/json", <https://www.79artstudio.com/>; rel=shortlink x-litespeed-cache-control: public,max-age=604800 x-litespeed-tag: dce_HTTP.200,dce_front,dce_URL.6666cd76f96956469e7be39d750cc7d9,dce_F,dce_Po.7804,dce_PGS,dce_guest,dce_,dce_MIN.c64605f919cde3636fcbdb473ae15dfc.js cache-control: max-age=0 expires: Sat, 06 May 2023 01:54:48 GMT vary: Accept-Encoding,User-Agent etag: "142524502-1683338090;;;" x-qc-cache: miss date: Sat, 06 May 2023 01:54:50 GMT server: LiteSpeed x-qc-pop: EU-DE-FKB-67 alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"the node is working as it should on my test
are you using some kind of VPN or proxy service ?
No, I don’t use any proxy or VPN.
The topic ‘SSL not Secure’ is closed to new replies.