BrowseDns lagging out on switch
-
sometimes trying to log onto browseDns on switch the site will not load and a blue screen that pops up saying error 503 forum isn't available due to excessive loading it takes a few tries trying to get bdns to load on switch not olny that I'll have issues where when I log in it doesn't give me my full side bar and still display the login arrows on the side it takes so long for bdns to fully load and work on the switch and it sucks when bdns timeouts and you can't open it up back as quickly
@Hollyday preach because its so annoying trying to text and it just DOESNT LOAD OR SAYS ERRROR 503
-
nintendo prolly gave us the finger again atm
-
nentendo constantly trying to cancel our fun party
-
fr tho ong
-
It's NINTENDO what can you expect?
-
I don't believe it is a Nintendo issue or something Nintendo has caused. Typically when you login and you get redirected to your profile page you should have your sidebar displayed. If not, you will get redirected to your profile page and it will appear as if you aren't logged in but in reality "you are". It just takes time for the site to realize that you have already logged in. You get redirected to your profile but still have access to the options that allow you to edit your profile settings but not to other features.
I tested this issue and it only seems to occur when you login successfully and you click the back button multiple times to the point where you went back to a page that you were on before you were logged in to your account. Just go back to the BrowseDNS Homepage and click the big blue login button, it should work.
Edit: The 503 Errors is basically you getting rate limited. It occurs typically when the site starts to bug due to database issues, slowness of the site, your device sending multiple requests to the server (common for botnets to do), etc. I'm sure the @administrators will take a look into that when they get a chance.
-
undefined Raven marked this topic as a question on
-
I don't believe it is a Nintendo issue or something Nintendo has caused. Typically when you login and you get redirected to your profile page you should have your sidebar displayed. If not, you will get redirected to your profile page and it will appear as if you aren't logged in but in reality "you are". It just takes time for the site to realize that you have already logged in. You get redirected to your profile but still have access to the options that allow you to edit your profile settings but not to other features.
I tested this issue and it only seems to occur when you login successfully and you click the back button multiple times to the point where you went back to a page that you were on before you were logged in to your account. Just go back to the BrowseDNS Homepage and click the big blue login button, it should work.
Edit: The 503 Errors is basically you getting rate limited. It occurs typically when the site starts to bug due to database issues, slowness of the site, your device sending multiple requests to the server (common for botnets to do), etc. I'm sure the @administrators will take a look into that when they get a chance.
@Raven ight thx for the info
-
I don't believe it is a Nintendo issue or something Nintendo has caused. Typically when you login and you get redirected to your profile page you should have your sidebar displayed. If not, you will get redirected to your profile page and it will appear as if you aren't logged in but in reality "you are". It just takes time for the site to realize that you have already logged in. You get redirected to your profile but still have access to the options that allow you to edit your profile settings but not to other features.
I tested this issue and it only seems to occur when you login successfully and you click the back button multiple times to the point where you went back to a page that you were on before you were logged in to your account. Just go back to the BrowseDNS Homepage and click the big blue login button, it should work.
Edit: The 503 Errors is basically you getting rate limited. It occurs typically when the site starts to bug due to database issues, slowness of the site, your device sending multiple requests to the server (common for botnets to do), etc. I'm sure the @administrators will take a look into that when they get a chance.
@Raven I see other than that just the error 503 thing is still occuring
-
It happened to me three times so it finnally worked now so hopefully Its doesn't happened again
-
Admins are aware and have stated that they will work on it.
