felog

So it’s profile specific. Could even be browser specific. Something is not right with the communication path. For example, you create a hosts file entry and you point it to your dev server which does -not- have the name https://www.yourdomain.com << that would give you a cert error.

When you use nslookup, you’re querying against your nameserver. Do you get the same ip when you ping from a command line?

Of course, that’s all machine specific and it wouldn’t matter who was logged in.

Also, when you’re getting the cert error, view the cert. Does it match correctly?

Site and cert seem fine. It could be location specific — does this issue occur when you’re offsite with your laptop? If so, check another device at that same location. Do you get the same issue?

My guess is that it’s something to do with your current location. When I do a lookup on your URL, I get the following IP: 192.185.52.135

Open a command prompt or a terminal and type the following: nslookup https://www.ngpstoreusa.com

Do you show the same IP as what I have listed above?