Unable to access scout book

https://scoutbook.scouting.org/mobile/dashboard/admin

@SharatMandava well yes - that is a bad URL - to go to LEgacy scoutbook the URL is Scoutbook.scouting.org - or Scoutbook+ at advancements.scouting.org

@SharatMandava- or advancements.scouting.org

1 Like

I’m able to access this page, but I don’t have access to Scoutbook starting this morning. Since I’m the finance in-charge and need to update scout payments, I need to be able to log in to Scoutbook.

@SharatMandava - clear your cache for scouting.org sites

1 Like

@SharatMandava - I am now seeing the same thing

Yeah, I can confirm I get a 403 when directly connecting to scoutbook.scouting, and a 404 when linking in from advancements.scouting. Sounds like a systemic outage of some sort.

@SharatMandava - was able to access legacy scoutbook just now

I think you just hit it in a hick up - I have no issues

i am stuck with scoutbook.scouting,org also with the 403 Permission Denied

do you know when it might be back up?

@BrianFlachs

We have done multiple tests in the last 30 minutes and have not seen any 403 errors. Are you able to log in to advancements.scouting.org or my.scouting.org?

I restarted my system and tried accessing it using the Chrome browser, but I am still facing the same issue. However, I am able to log in successfully using Safari. This indicates that the issue appears to be specific to Chrome.

@SharatMandava

Please try a chrome Incognito window or clear your cache. I have had no trouble accessing Scoutbook via Chrome today.

both of those work. however, i tried clearing my cache and that did restore my access to the page

Earlier, I tried both methods and it didn’t work. However, when I tried again using a Chrome Incognito window, it worked. This seems to have been a temporary hiccup, possibly related to the browser cache or session.

I was able to resolve this without a browser/system restart by selectively clearing the cached data for scouting.org. I concur that it appears some bad data got cached (since forcing a refresh of the page didn’t resolve the issue by itself).

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.