create account

스팀잇 504 Gateway Time-out 에러 by hsalbert

View this thread on: hive.blogpeakd.comecency.com
· @hsalbert · (edited)
스팀잇 504 Gateway Time-out 에러
오늘 오후 중에 steemit.com으로 접속하시는 분들 가운데 "504 Gateway Time-out" 오류로 접속이 안 되었던 분들 계시나요? 

브라우저에 따라서, "HTTP 504", "504 ERROR", "Gateway Timeout (504)", "HTTP Error 504 - Gateway Timeout", "Gateway Timeout Error" 등으로 표시되는 접속 실패는 모두 같은 종류의 접속 장애라고 합니다. 

1. 아이폰의 사파리 브라우저로는 steemit.com이 평소 속도 그대로 접속이 원활했고, 
2. 동일한 무선랜 망에서 동일한 PC로 steemkr.com에 접속할 때는 속도가 평소보다 느렸지만 접속에 장애는 없었습니다.

어느 설명에서는,

> Also, please know that 504 Gateway Timeout errors can appear in any internet browser, on any operating system, and on any device. This means that it's possible to get a 504 Gateway Timeout error on your Android or iPhone phone or tablet, in Safari on a Mac, in Chrome on Windows 10 (or 8, or 7, ...), etc.

> **Causes of 504 Gateway Timeout Errors**

> Most of the time, a 504 Gateway Timeout error means that whatever other server is taking so long that it's "timing out," is probably down or not working properly. Since this error is usually a network error _**between servers on the internet**_ or an _**issue with an actual server**_, the problem probably is not with your computer, device, or internet connection. (한 출처)

그리고,

> Since the 504 Gateway Timeout Error indicates that something has gone wrong within the server of your application, we can largely disregard the client side of things. If you’re trying to diagnose an issue with your own application, you can immediately ignore most client-side code and components, such as HTML, cascading style sheets (CSS), client-side JavaScript, and so forth. This doesn’t apply solely to web sites, either. Many smart phone apps that have a modern looking user interface are actually powered by a normal web application behind the scenes; one that is simply hidden from the user. If you’re using such an application and a 504 Gateway Timeout Error occurs, the issue isn’t going to be related to the app installed on your phone or local testing device. Instead, it will be something on the _**server-side, which is performing most of the logic and processing behind the scenes, outside the purview of the local interface presented to the user.**_ (다른 출처) 

라고 하여, _**'네트워크상에서 서버 사이(between servers on the internet)'**_의 네트워크 오류이거나 '웹 서버의 문제(an issue with an actual server)'라고 합니다. 또한 _**'사용자 쪽의 인터페이스에서 떨어진 무대의 배후에서 대부분의 로직과 프로세스를 처리하는 서버 쪽(server-side...performing most of the logic and processing behind the scenes, outside the purview of the local interface presented to the user)'**_에서 무언가 장애가 생긴 것이라고 합니다.

그렇다면, 아이폰으로 steemit.com이 접속이 원활했다는 것은 웹 서버 자체의 문제가 아니라는 뜻이므로 한국 내 어느 네트워크상에서 steemit.com을 중계하는 서버 사이에 time-out 오류가 났는데, steemkr.com을 중계하는 서버 사이에는 time-out 오류가 없었다는 이야기가 됩니다. steemit의 접속 장애가 지금도 발생하는 걸 보면 한두 시간이 아니라, 아마도 네댓 시간 동안 지속됐던 것 같습니다.

이게 뭐 중요할까요? ㅎㅎ 뭔가 이상한 듯해서 그냥 적어봤습니다. 

![504 Gateway Timeout(1).png](https://steemitimages.com/DQmd6w823j98dVWiUzogX2awtkV6Y7rJ6BiJKNk7QS43zKN/504%20Gateway%20Timeout(1).png)
👍  , ,
properties (23)
authorhsalbert
permlink504-gateway-time-out
categorysteemit
json_metadata{"tags":["steemit","kr-steemit","timeout-504","kr-dev","kr"],"image":["https://steemitimages.com/DQmd6w823j98dVWiUzogX2awtkV6Y7rJ6BiJKNk7QS43zKN/504%20Gateway%20Timeout(1).png"],"app":"steemit/0.1","format":"markdown"}
created2018-04-24 10:28:00
last_update2018-04-24 11:29:21
depth0
children2
last_payout2018-05-01 10:28:00
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,868
author_reputation413,205,063,862
root_title"스팀잇 504 Gateway Time-out 에러"
beneficiaries[]
max_accepted_payout0.000 HBD
percent_hbd10,000
post_id51,842,016
net_rshares3,067,741,922
author_curate_reward""
vote details (3)
@hsalbert · (edited)
이틑날인 2018년 4월 25일 오전 11시 10분경 현재까지 steemit.com은 똑같은 오류를 지속하며 접속 장애를 보이고 있다. ![504 Gateway Timeout(2).png](https://gateway.ipfs.io/ipfs/QmUQvrQnsYqjuwTbsTyuLUNF1ASAhxxMeHGN7ycFEYP3er)
properties (22)
authorhsalbert
permlinkre-hsalbert-504-gateway-time-out-20180425t021647730z
categorysteemit
json_metadata{"tags":["steemit"],"community":"busy","app":"busy/2.4.0"}
created2018-04-25 02:16:57
last_update2018-04-25 02:18:33
depth1
children0
last_payout2018-05-02 02:16:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length183
author_reputation413,205,063,862
root_title"스팀잇 504 Gateway Time-out 에러"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id51,973,675
net_rshares0
@hsalbert ·
The steemit.com site continues to suffer from "504 Gateway Time-out" disorder, from late aftertoon yesterday up to now, 10h00 PM today. This network error spans more than 24 hours now. It's weirdly interesting to see that someone in charge takes no responsibility for it, for more than 24 hours. 
 
My machine accesses the interent from very small local wireless device through the fixed LAN to the Internet. All the other web sites function well, except for steemit.com within my regular surfing, which is very wide. So the problem must be related to someone in Korea who is in charge of the steemit.com connection over Korea, or perhaps some wide area in it.

![504 Gateway Timeout(3).png](https://gateway.ipfs.io/ipfs/QmauJG3iL9E87EBWPerHaN4KAN4vF1bqxrCcntejj7VXNu)
properties (22)
authorhsalbert
permlinkre-hsalbert-504-gateway-time-out-20180425t131202138z
categorysteemit
json_metadata{"tags":["steemit"],"community":"busy","app":"busy/2.4.0"}
created2018-04-25 13:12:09
last_update2018-04-25 13:12:09
depth1
children0
last_payout2018-05-02 13:12:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length769
author_reputation413,205,063,862
root_title"스팀잇 504 Gateway Time-out 에러"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id52,063,477
net_rshares0