Voyager suddenly stopped working with SJW today. The last time this happened, it was because SJW needed an update of some sort. Is that the case this time too?
Voyager suddenly stopped working with SJW today. The last time this happened, it was because SJW needed an update of some sort. Is that the case this time too?
Hey @westingham
Thanks for starting a post about this.
Our traffic today jumped 4x our previous daily high. I had to enable some extra protection to give the server some breathing room to recover. One of the side effects is the mobile apps are temporarily unavailable until I get everything tweaked. It will be back in a few days. The good news is that I already got my hands on a newer more powerful server that will be going into production in the next few weeks.
For the next few days if you want to scroll the site you will need to use your mobile browser. I understand its totally not the same experience as voyager but I promise you i’ll get everything back up as it was as soon as I can.
Thanks for your trust and patience!
Edit: Access via the mobile app Voyager has been reinstated.
Thank you for all you do!
Reading this and posting on Voyager right now, nothing happening only minutes ago. That’s the shortest “couple of days” I’ve encountered. Good effort - hope the traffic spike was all human. You provide an amazing service.
Glad things are under control. Is there a Mastodon or something where we can go to find status information like this? I was unable to access sh.itjust.works from any platform in order to find out what was going on until this morning.
An out-of-band means of communication is indeed very useful to have.
We have a matrix channel, which is linked in the instance sidebar after the rules.
Here: https://matrix.to/#/#sh.itjust.works:matrix.org
Appreciate the update!
I thought you were getting attacked. I couldn’t get in most of the day on browser. Glad it wasn’t