Timemapper down

Open Knowledge Labs TimeMapper
1

Hello. TimeMapper is down from time to time. There is an archived / frozen thread from me on this topic.

We’re attempting to use in production, and upon an edit to the Google Doc, TM reports app unavailable.

Here is the publish-link

https://docs.google.com/spreadsheets/d/1zgOJOdOlHEz5hqSK8znMTkkZtzfr4UGgHzDrbvSUEaA/pubhtml?gid=218260677&single=true

and here is the document link, which only possibly is of use to you, on backend

https://docs.google.com/spreadsheets/d/1zgOJOdOlHEz5hqSK8znMTkkZtzfr4UGgHzDrbvSUEaA/edit#gid=218260677

Published sheet is called “aggregation”

Al

2 Likes
3

Timemapper has been down for about a week. I get a perpetual “loading data” screen in FF and Chrome for Timemaps I created as well as the demo Timemaps linked from the website.

4

Thanks for the report! I’m replying here for transparency - this has been fixed now :slight_smile: Timemaps won't load · Issue #545 · okfn/okfn.github.com · GitHub

1 Like
5

Looks like this issue is happening again

6

The server has been down for a while. Could you solve the problem soon? Thank you very much!

7

Hi all, thanks for the reports. The tech team has been notified and is investigating.

For future issues, please use the github repository issue tracker: Issues · okfn/timemapper · GitHub

Thanks all - I’ll post an update when there is one!

8

Hello, is TimeMapper down? A colleague and I are both trying to log on, and both of us are getting an error message on our screens. Please advise

9

Any chance of fixing TimeMapper?

Express

500 Error: Could not authenticate you.

  • at Strategy.parseErrorResponse (/app/node_modules/passport-twitter/lib/strategy.js:202:14)
  • at Strategy.OAuthStrategy._createOAuthError (/app/node_modules/passport-oauth1/lib/strategy.js:405:16)
  • at /app/node_modules/passport-oauth1/lib/strategy.js:252:41
  • at /app/node_modules/oauth/lib/oauth.js:543:17
  • at passBackControl (/app/node_modules/oauth/lib/oauth.js:397:13)
  • at IncomingMessage. (/app/node_modules/oauth/lib/oauth.js:409:9)
  • at IncomingMessage.emit (node:events:538:35)
  • at endReadableNT (node:internal/streams/readable:1345:12)
  • at processTicksAndRejections (node:internal/process/task_queues:83:21)
10

@gunnargr it seems to be working at the moment.

Just wondering: have any of the folks discussing this considered hosting their own Timemapper instance, and if so, were there any barriers / concerns about doing this?