Can't reach router/gateway at 192.168.2.1

the router/gateway is a pfSense appliance. pfSense is up-to-date on it

- - - Updated - - -
@Steve -- will do, LOL

THANK you both for all the comments/suggestions !!! ...gone step aside for a little as well...

- - - Updated - - -

...SOLVED !!

...it was an issue with the browsers not accepting the self-issued certificate of my pfSense firewall. Fixed in Firefox (not Edge yet) by opening Firefox Settings > Privacy & Security > Certificates > View Certificates > Add Exception. Had to give the IP address of the gateway, and Firefox queried it to obtain the Certificate I had generated several years ago, and they I added the exception. All working fine now.

Interestingly, only figured this out by using my 20 year old laptop wit Win XP, and very old Firefox, and when trying to access my gateway from there, Firefox provided a warning page stating the certificate of the gateway was not valid, and offering to make an exception. Firefox in my new Win 10 install, never did flag the issue with the certificate, it just refused to connect. The same is happening with Safari in my iPad -- no warning, it just does not connect; AND is the same with Edge in my Win 10. I think this is BS, they should warn and give the option to create exception.

Thank you again for the exchanges earlier today !!

- - - Updated - - -

...probably should add that I believe years ago, in my Win7 machine, I did add the exception for the self-signed certificate to Firefox, when alerted by that much older version of Firefox; and thus it all worked fine until now that I had to switch.

I just see this solved thread. I had a similar problem some months ago. I solved it by approaching the router not with Firefox but with the Brave browser. Later I could reach the router again with Firefox, presumably after an update of FF or after a router update.