Bitcoin Forum

Other => Meta => Topic started by: Patatas on September 11, 2015, 05:03:26 PM



Title: How to fix this?
Post by: Patatas on September 11, 2015, 05:03:26 PM
Hello, I keep on getting this error just today and refreshing my browser fixes the problem but it does come back and I need to refresh my browser again multiple times just to get rid of this error. I find it annoying and causes incovenience sometimes. Is there any way to fix this other than refreshing the site? Any relevant answer is appreciated. Thanks :)
Here's a screenshot :
https://i.imgur.com/PbF3JDI.jpg


Title: Re: How to fix this?
Post by: onemorexmr on September 11, 2015, 05:07:30 PM
i get that too sometimes. today a little more often

i guess ( !) many people are loading the coinwallet stresstest thread over and over again; putting huge load on the servers.


Title: Re: How to fix this?
Post by: harizen on September 11, 2015, 05:15:44 PM
Im expecting a thread about this since the error always prompting a hour ago. Continous refreshing don't work on me. Im waiting for about 10 seconds before refreshing up then it will load up. This is not the solution though. I know, we users can't fixed this by our own since it's server sided*.

*I think


Title: Re: How to fix this?
Post by: okae on September 11, 2015, 05:46:55 PM
Continous refreshing don't work on me.

exactly this, when this happens don't refresh again, seems like if you refresh faster the error 502 will remain, so just w8 some minutes and try again, you will see how the forum works again.

it happened to me few times and thats the only way i know that works, also if im not wrong i remember that theymos already reply the same about it, but cant find the thread now :(


Title: Re: How to fix this?
Post by: Cyrus on September 11, 2015, 06:23:14 PM
The error is indeed server side and can be caused by a number of things. I wouldn't recommend continuously refreshing, just wait a few minutes and try again.


Title: Re: How to fix this?
Post by: Patatas on September 11, 2015, 07:09:43 PM
The error is indeed server side and can be caused by a number of things. I wouldn't recommend continuously refreshing, just wait a few minutes and try again.

Ok I see. I hope it will be fixed soon and I'll consider your advice. Will be locking this thread now. Thanks for the answers