TR Forum and Training calendar both failed
Mac OS Sequoia 15.6.1
Vivaldi Browser
Functionality stopped Tuesday evening PST
Interesting. martenk, your private window idea worked for me. Any idea how I can reset my browser to stop TR denying the requests in regular windows though? Iāve cleared cache etc and it wonāt seem to let go. Iāve no idea what got my browser to do this in the first place 
Maybe try disabling installed plugins one by one until it works again. Or open the browser console to see if thereās an error visible. Most browsers also have a network tab in their console or their developer tools which should show all the requests made. Maybe thereās a hint to the issue in there.
Iāve been getting these too.
429 error for me as well trying to load the forum. The first time I cleared the TR cache (it was massive, hundreds of mb) and it fixed it. The second time it went away on its own after about a day.
There has got to be something going on on TRās end for us all to suddenly be getting 429 errors like this??? Iāve tried everything and I canāt seem to unlock things with my primary browser/computer. Iām just using TR now in a parallel private window but canāt get my normal browser window functioning again.
Is this just the forum for you or other TR pages?
Training Calendar too. Any trainerroad.com URL.
Both Forum and occasionally the calendar.
Edit: The fix for this issue is after the below paragraph. @eddie
I was experiencing the same issue. I decided to go down the rabbit hole this morning during a meeting. 
Mozilla was working, but no more. Same 429 error. Edge/Chrome 429 error (network rejection). If I open edge/chrome in guest mode, the forum loads normally. Guest mode from what I remember doesnāt load registered service workers. My guess is a service worker is hammering the azure remote ip 23.100.233.188 instance of discourse and thus the IPs are now soft blocked. Could be rules in the application gateway or waf if theyāre using that. Or maybe itās discourse and messagebus settings.
On my phone, in my chrome profile, on cellular, I can log into the forum fine since that IP hasnāt been soft blocked.
To resolve - for now. I unregistered these two service workers in chrome. I believe the 429 error was caused by a corrupt service worker state following any sort of recent update and spamming the hell out of the IP. After unregistering these two workers, the site loaded normally most likely due to the flood of requests stopped by that zombie service worker. Specifically, I think azure waf was the issue (this is where the 429 error came from) but not on purpose as it was most likely doing the job it was designed to do - block flood of traffic from a device/IP.
To fix this at scale - TR could update the waf rate limit or usersession. Or send http header out through their app gateway. This is about the extent of my expertise in azure apps. Background: sysadmin/security in public safety, azure tenant admin. Hope this helps for everyone having the issue!
I reset my settings in Edge using the following steps and I have access again, thanks @martenk
- Open Edge
- Go to: edge://settings/reset
- Click Restore settings to their default values
- Confirm
This was done on my pc..Iāll mess with my iphone edge and see if I can fix it there too.
Both ways will work. I wanted to find the root and the why of the issue without nuking my settings.
Gotta love this forum. Full of engineers, IT professionals, etc to the point that they can reverse engineer or debug pretty much anything 
All the while, I noticed TrainerRoad pushed out version 4529. Woohoo. Great collective of people on this board. Insane really.
Edge is still in the death loop. The 4529 version works, but doesnāt auto-recover browsers that are caught in the 429 loop (version 4472). TR should push a clearsitedata header to nuke the zombie service workers.
Seriouslly!!! I understood almost none of DMCās post but enjoyed the hell out of every confusing word. Thank goodness for smart people! 
So did we the users create the Zombies?
Update: Issue has been fixed!
However, let us know if youāre still experiencing it.
4 Likes
I think you were right about some WAF rules being the issue! 
Thanks for digging in!!
FIXED!! Thank you TR!!