Is it just my computer, or is anyone else having problems getting RWGPS to open properly on their desktop or laptop computer?

On my (Android) phone, the RWGPS app opens and works as expected, so it seems the issue is limited to (my?) desktop.

On my Windows 10 desktop machine I'm using Edge, and all I get is a blank screen when I try to open RWGPS.  I'm a Premium-level subscriber and my login info is cached, so it should just connect to my data as it always has in the past.  I started seeing this issue on Tuesday or maybe Wednesday; a reboot appeared to "cure" the problem once but not the second time.

When I've switched to Chrome, where I've never logged in so RWGPS doesn't know who I am, the default RWGPS home / not-logged-in page loads but clicking the Login link produces no result or even a visible reaction.  If I click the Sign Up box I'm taken to the screen where I could create a new account but that does me no good.

I've cleared the Edge browser cache (but retained password and login data) and also flushed my local DNS cache, but neither action has changed the observed behavior.

Do you use any ad blockers or popup blockers? These may also create unexpected behaviour as I have had here on CycleBlaze once.

Nothing beyond what's built into the browser.   I've made no (deliberate, conscious) changes to the system since my last successful use of RWGPS on Sunday or Monday.

I had an issue yesterday but a system restart seemed to fix it; not so, today.

I think it's a very localized gremlin.

I typically put my system into "Sleep" (power-saving) mode when it's not in active use, and periodically when it wakes back up it loses the internet connection.  Obviously I had internet access a few hours ago when I originally posted but after another sleep/wake cycle I did not.

The only way forward that I know of is a system restart; after this one I tried RWGPS again and got instant satisfaction.

[EDIT]

30 minutes later: nope it's not as simple as a system restart.  That worked for exactly one operation on RWGPS: I created one new route but, when I chose "View route" after saving it, it was back to the blank stare.

On the premise that I might somehow have a corrupted authentication cookie (I had not deleted those when I cleared the rest of the Edge cache) I wiped out ALL cache data (knowing that would also log me out of RWGPS), closed the browser, and powered the system down completely.

After pouring myself a relaxing cup of coffee I restarted the system.  No joy, and now I can't even get to the RWGPS login screen so I'm firmly stuck.

Switching browsers to Chrome didn't help: I cannot get the RWGPS login screen to load there, either.

Ain't technology grand?

[SECOND EDIT]

Changing browsers to DuckDuckGo didn't change any of the symptoms either, so now I'm really stuck.

[THIRD (and hopefully FINAL) EDIT]

On every browser I explicitly enabled javascript for the RWGPS website.  No joy, UNTIL I also shut off the VPN provided by my antivirus software (Norton).  Bingo!  I can now log in to RWGPS from any of my browsers.  I haven't tried doing anything but at least I am back in and have the potential to use the site.

I'm not really technically able to completely follow this conversation but I'm puzzled by the squirrelly VPN influence on RWGPS. That seems like something that RWGPS would want to know about, seeing as how so many clients are using it overseas where having a VPN is often a really, really good idea. 

It's a head-scratcher, to be sure.  I'm no VPN expert (about as far from it as possible, truthfully) so I don't really know if the fault lies on the RWGPS side or my VPN setup / provider.  And I don't know how to test that to see if I can find out.

I work in cybersecurity, many of those VPNs have ad blockers built in that often block pop-ups in general.  I'm not familiar with Norton, but you should be able to disable the ad blocker.

Or just turn off the VPN. There is a marginal security gain by using a VPN when you are at a public WiFi hotspot, but at home really minimal need for it.

Thanks John.

Or just turn off the VPN

That's exactly the route I've taken.  No issues since.