PDA

View Full Version : Bad Gateway



jig_saw86
15-02-2010, 12:57 PM
knp kadang2 suka muncul ky gini :


502 Bad Gateway

nginx

audeh
15-02-2010, 01:30 PM
gak tau bro W jg suka kayak gitu (gak sering" amat)

di refresh lagi aja biasanya udah bisa lagi...

jig_saw86
15-02-2010, 01:33 PM
aku reload sampe 3x baru bisa lg :nangis:

namsadin
15-02-2010, 02:28 PM
beberapa hari ini kejadian tersebut engga terlalu sering terjadi, paling pas abis posting doank, tapi koq tadi siang sempet kejadian seperti yg TS alami sampe 1/2jam lebih,... di refresh juga gag bisa,

kemudian sekarang, setelah kejadian tadi, untuk ngakses forum terasa berat,. :nangis: :tolong:

skydragon
15-02-2010, 02:43 PM
Nginx adalah webserver utama di indowebster...
Bila terjadi error itu kemungkinan webserver idws belum pulih 100%...
Jika skrg hanya terjadi sekali atau 2x dan tidak terlalu lama, mungkin memang belum sempurna...Dulu pada saat sedang banyak gangguan, hal ini bs terjd seharian, bahkan beberapa hari...

Jadi harap bersabar, admin pasti juga terus melakukan perbaikan...:piss:

CMIIW...

jig_saw86
15-02-2010, 02:52 PM
yg lbh sering sk log out sendiri itu kenapa kk???

blue_lionx
15-02-2010, 03:06 PM
http://1.bp.blogspot.com/_HbRZwpPnFNs/SXkXGxPGTbI/AAAAAAAAAXE/NFeCJ3XZh04/s400/502_bad_gateway001.png



Error 502 Bad gateway

Introduction
A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request.

This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed.

502 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:

Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '502'.

Fixing 502 errors - general
This problem is due to poor IP communication between back-end computers, possibly including the Web server at the site you are trying to visit. Before analysing this problem, you should clear your browser cache completely.
If you are surfing the Web and see this problem for all Web sites you try to visit, then either 1) your ISP has a major equipment failure/overload or 2) there is something wrong with your internal Internet connection e.g. your firewall is not functioning correctly. In the first case, only your ISP can help you. In the second case, you need to fix whatever it is that is preventing you reaching the Internet.
If you get this problem for only some of the Web sites you try to visit then it is likely to be a problem at those sites i.e. one of their pieces of equipment is failing/overloaded. Contact the people at those sites.

Fixing 502 errors - CheckUpDown
Use of proxies and caching is increasing on the Web. Our CheckUpDown robot will always try to 'drill through' to the real computer that actually hosts the Web site, but we do not have complete control over where our HTTP request actually ends up. If only one link in the chain of computers dealing with our HTTP request is broken, then an error such as 502 can easily occur.
Please contact us (email preferred) whenever you encounter 502 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of the Web server software so that they can review the flow of IP data traffic between various computers under their control.

:em0100:
=============
kalau soal ke logout sendiri, kemungkinan gara2 dah lama login.. coba di centang remember ID pas mau login.. :hahai:

jig_saw86
15-02-2010, 03:19 PM
itu apa kk??
bhs inggris smua.
aku g tau :hehe:

Ryuwafi
15-02-2010, 03:21 PM
Gak ngerti? khan ada goggle translete :piss::piss:

ordinary
15-02-2010, 03:47 PM
kalo pake firefox, sering banget dapet error itu.
tp kalo pake chrome lancar2 aja, apa ada addons firefox yang ga kompatibel sama IDWS???

jig_saw86
15-02-2010, 03:52 PM
Q pake cometbird.
firefox kerjanya lambat

summonedskull
15-02-2010, 04:15 PM
tadi siang pake chrome & firefox sampai belasan kali refresh baru kebuka :nangis:

jig_saw86
15-02-2010, 04:24 PM
sebnrnya bkn pengaruh dr SW browsing kali ya.
tp dr idws yg lg main tenis :haha:

erickstrad
15-02-2010, 05:08 PM
iya, bkn mslh browser, sama aja ah, sya pk chrome/ff jg ttep keluar tuh bad gateway :em0400:
server IDWS nampaknya blm sembuh bnar pasca long maentenance wktu libur natal-tahun baru kmaren :em0400:

jig_saw86
15-02-2010, 05:38 PM
kasian........ aku jd :terharu:
mungkin perlu cuti dulu ya?

terus gmn mau upload????

g up2date lg dong info di idws :ngambek:

Animers
15-02-2010, 08:56 PM
tapi soal browser kayaknya iya deh, kemaren2 sih, sekarang udah nggak, kalau pake FF lebih sering keluar Bad Gateway malah seharian , gw kira IDWS nya lagi gak bener /down / maintenis , ternyata pake browser lain bisa, malahan FF yang gw pake versi 3.5 ke atas itu yang suka bad gateway

tapi pas gw coba di kompi lain yang make FF 3.0 malah bisa masuk

tapi itu kemaren2 sih, sekarang udah nggak kayaknya

sYntic
16-02-2010, 01:35 AM
mohon maaf atas ketidak nyamanannya menghadapi bad gateway

kami masih mencari setting server terbaik untuk menanggulangi error ini, tapi masih perlu banyak pembenahan lebih lanjut :)

jadi harap bersabar dan maklum jika menemukan error ini.

jika menemukan error bad gateway, silahkan di refresh lagi.

jika tetap error, harap hubungi admin terdekat :piss:

jig_saw86
16-02-2010, 01:39 AM
mohon maaf atas ketidak nyamanannya menghadapi bad gateway

kami masih mencari setting server terbaik untuk menanggulangi error ini, tapi masih perlu banyak pembenahan lebih lanjut :)

jadi harap bersabar dan maklum jika menemukan error ini.

jika menemukan error bad gateway, silahkan di refresh lagi.

jika tetap error, harap hubungi admin terdekat :piss:
iya nih bnr2 g nyaman.
mana mau UL g bs lg!
jgnkan UL kadang2 jg DL g bs
:kecewa:

terus kpn :idws: pulih kembali???

makanya :idws: jgn byk begadang nanti masuk angin. :hehe:

:piss: