Bitcoin Forum

Other => Meta => Topic started by: mishax1 on October 30, 2019, 04:53:44 PM



Title: So what's up with the Watchlist ?
Post by: mishax1 on October 30, 2019, 04:53:44 PM
Quote
Down for maintenance, be back soon (503)
The forum is down for maintenance. Try again in a few minutes.

503 via master1


Title: Re: So what's up with the Watchlist ?
Post by: TheBeardedBaby on October 30, 2019, 05:01:30 PM
Working good with me, delete the cache of the browser and try again.


Title: Re: So what's up with the Watchlist ?
Post by: TryNinja on October 30, 2019, 05:03:56 PM
Ctrl + F5 fixes it. Your browser is showing a cached version of the page from when it was down for maintenance. The same happened on my phone last week.


Title: Re: So what's up with the Watchlist ?
Post by: mishax1 on October 30, 2019, 05:12:32 PM
Ctrl + F5 fixes it. Your browser is showing a cached version of the page from when it was down for maintenance. The same happened on my phone last week.

Thanks


Title: Re: So what's up with the Watchlist ?
Post by: theymos on October 30, 2019, 06:32:42 PM
I have no idea why people are still seeing that. Are you using some weird browser, like Opera Mini or similar?

There was a bug on my end where those error pages were being returned with HTTP 200 instead of 503 (as intended and as the error claimed), and in some cases they could've been marked cacheable for up to 4 hours. But nobody should still be seeing them now.


Title: Re: So what's up with the Watchlist ?
Post by: mishax1 on October 30, 2019, 06:39:14 PM
I have no idea why people are still seeing that. Are you using some weird browser, like Opera Mini or similar?

There was a bug on my end where those error pages were being returned with HTTP 200 instead of 503 (as intended and as the error claimed), and in some cases they could've been marked cacheable for up to 4 hours. But nobody should still be seeing them now.

Updated Chrome.


Title: Re: So what's up with the Watchlist ?
Post by: SM23031997 on October 30, 2019, 06:40:19 PM
Try incognito window and check if you are still getting the same message.
If not, there is some issue with your browser otherwise it's a server issue.

Did I forget to mention it is working fine for me?