port forwarding, NAT, and odd client behavior

[crashdox]

Hi everyone, I'm new to opnsense.  I have replaced an old box, and am using one of these new appliances.  So far so good.

The scenario:
Single WAN to verizon fios, single LAN connectivity to my "big" LAN. (not a home lan, but not enterprise either).
I have port forwarding set up to several different services on my LAN; a camera system, phone system, etc.  Nothing unusual.  Different ports to get to everything via forwarding.  Used to work fine with my old firewall.

My main PC is hard wired into my ASUS router (Merlin).  My phone and a laptop are wireless to that same router.
I am logged into the OPNsense GUI at home, no problem.  SSH as well.

Here's the kicker that i worked on all day, and only at the end of the day did something strange show itself:
My main PC *cannot* access these sites via the port forwarding.  However: The laptop & phone are able to access them without ANY problem.  HUH?   These are all through the same ASUS router!  Is it Windows screwing me over ?  I rebooted the router & the main PC a couple times.  No change.   tcpdump at the OPNsense side shows the traffic; in the PC instance, like 5 lines & stops.

This occurs both in Edge & Chrome.

The Opnsense side seems to be perfectly fine!  What am I missing ? 

thanks

[crashdox]

Update:  I had been playing with acme client to install certificates.  I had imported at least one of them to my main system.  I have since - as far as I can tell - deleted any obvious certificates, rebooted, etc.   Browsers on that system still cannot get to systems via the port forward, but are able to access the firewall dashboard itself without any issues.

I can't think of anything else I did that could have caused this...

[crashdox]

[SOLVED]  Had to delete bad security info from chrome at least; have to check on edge yet

https://howchoo.com/chrome/stop-chrome-from-automatically-redirecting-https
https://answers.microsoft.com/en-us/microsoftedge/forum/all/how-to-stop-ms-edge-to-auto-redirect-to-https/21b0c999-2042-4487-874b-2fc01a7ca167

Same method works for Edge too.