Rank 1: Thread
And Chrome on my Ipad is similar to Safari in that it's showing no security issues. I'll try restarting Chrome on my Mac
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 1: Thread
And Chrome on my Ipad is similar to Safari in that it's showing no security issues. I'll try restarting Chrome on my Mac
Admin
There isn't really any special account
Admin
And the CN of the certificate is fine?
Is there anything else in the browser console logs?
The only other time I've experienced this is when there are some other http requests or something on the page.
Admin
Did you try in incognito?
Rank 1: Thread
I don't know much about security certificates, so I'm not sure what R3 means in terms of Common Name
Rank 1: Thread
I'll try Incognito mode and look at the browser console logs
Admin
Are you sure you're looking at the right certificate? The CN should be your domain 🧐
Rank 1: Thread
The page shows up fine in Incognito mode, but I got some weird errors in the browser console in the normal browser
Rank 1: Thread
The Common Name in the Issued To section is my domain. The R3 is the Common name from Issued By
Admin
Oh okay then
Admin
No certificate warning in incognito?
Rank 1: Thread
No
Admin
Maybe you have a browser cache problem then
Admin
Perhaps this is a websocket error? Does your Apache have web sockets enabled?
Rank 1: Thread
I'm not sure. I can't remember how to check that, but I can look it up
Rank 1: Thread
proxy-wstunnel was not enabled
Admin
So you enabled that and now the error is gone?
Rank 1: Thread
I enabled it and restarted Apache, but I'm still getting the errors
Admin
In the chrome network logs, you can filter on WS for web sockets. You can check that to see if it's connecting properly
Rank 1: Thread
Nothing with WS showed up in the network logs I recorded while refreshing the page
Rank 1: Thread
I'm going to restart Chrome and see if anything changes
Rank 1: Thread
Okay, so I'm still getting the same weird console errors, but the security warning is gone and everything looks secure
Rank 1: Thread
Based on minimal googling, apparently some of the console errors could be related to browser extensions
Rank 1: Thread
So I'm crossing my fingers that things will work out fine now
Rank 3: Container
You can use aapanel its more easy that nginx proxy manager