|
Bad Gateway
|
View this Thread in Original format
| Jon_Snow |
 |
|
|
| aquila |
 |
|
|
| Swamper |
Search this thread is now fixed.
Bad Gateway error is DNS related... it is taking longer than normal for the change to propagate which is frustrating (I'm having some issues too)
162.216.4.229 is the new address... that other one should be gone by now. :whip:
 |
|
|
| Lira |
| Ibotirama!? Did someone kidnap TA or something? Want me to go get it? I will destroy ISIS! |
|
|
| Redd |
| Chrome giving me bad gateway on all threads, Edge works fine. I guess clear cache and would fix it? |
|
|
| Mr.Mystery |
| Bad gateway! Bad! Hang your head in shame. |
|
|
| Woony |
| Im still getting errors on Chrome. |
|
|
| MSZ |
| I believe the only solution you guys can try is flushing your dns. I believe google chrome for some reason has its own dns cache, so you can try that. You can probably google "how to flush google chrome dns". |
|
|
| Swamper |
| quote: | Originally posted by Woony
Im still getting errors on Chrome. |
Really? No reason for that... all name servers have been updated for days.
 |
|
|
| Redd |
| quote: | Originally posted by MSZ
I believe the only solution you guys can try is flushing your dns. I believe google chrome for some reason has its own dns cache, so you can try that. You can probably google "how to flush google chrome dns". |
Yeah I've tried that, also flushed cache from ipconfig for good measure. Chrome still giving me bad gateway for all threads. |
|
|
| Woony |
| Works for me after clearing the cache (pain in the ass though!) |
|
|
| Mr.Mystery |
| All this talk about flushing and ass pain is making me... something. |
|
|
|
|
