Skip to content

Instantly share code, notes, and snippets.

@maxguzenski
Created August 1, 2019 03:02
Show Gist options
  • Save maxguzenski/b6dc0736e0c42cfd49dea2d8ad02a88a to your computer and use it in GitHub Desktop.
Save maxguzenski/b6dc0736e0c42cfd49dea2d8ad02a88a to your computer and use it in GitHub Desktop.
dropframe
Seguinte, o episodio "Graficos importam" (A) segue nao baixando para mim, os demais baixam.
Irei compara-lo com o ultimo "Pre venda ps5" (B)
A url é de (A) é
https://mcdn.podbean.com/mf/download/ynkz9i/Gr_fico_Importa_-_DropFrame_-_EP_-_60.mp3
que na verdade é redirecionado para:
https://s158.podbean.com/pb/437293e4defe046d22bf23becdf0d420/5d42525e/data2/fs7/2965107/uploads/Gr_fico_Importa_-_DropFrame_-_EP_-_60.mp3?pbss=eb5e966c-ed90-558d-92f6-a342c7f23812&download=1
A Url de (B) é
https://mcdn.podbean.com/mf/download/qrcb49/Drop_-_16_Pr_-venda_Do_Ps5_The_Outer_Worlds_No_Switch.mp3
que na verdade é redirecoinado para:
https://s111.podbean.com/pb/6e870593f406235967b4a337a95cd724/5d42514a/data1/fs7/2965107/uploads/Drop_-_16_Pr_-venda_Do_Ps5_The_Outer_Worlds_No_Switch.mp3?pbss=eb9d6599-f025-5b37-8315-5ee47bb08dab&download=1
Um ping em (A, do erro) da timeout:
```
PING s158.podbean.com (198.255.88.170): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
^C
--- s158.podbean.com ping statistics ---
8 packets transmitted, 0 packets received, 100.0% packet loss
```
Um ping em (B, que funciona):
```
PING s111.podbean.com (23.237.42.26): 56 data bytes
64 bytes from 23.237.42.26: icmp_seq=0 ttl=43 time=191.619 ms
64 bytes from 23.237.42.26: icmp_seq=1 ttl=43 time=187.928 ms
^C
--- s111.podbean.com ping statistics ---
3 packets transmitted, 2 packets received, 33.3% packet loss
```
O que acontece é que este servidor (s158) nao existe ou deixou de existir ou é inalcançável desde o Brasil.
Pode ser um erro de CACHE DE DNS do lado deles.
Recomendo passar essa info de PING para eles, comparado o sucesso com o do erro. As infos abaixo podem ser uteis tbm:
TRACERT EM (A) do erro (o comando nao encontra o server final):
```
traceroute s158.podbean.com
traceroute to s158.podbean.com (198.255.88.170), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 3.324 ms 2.233 ms 1.546 ms
2 172.21.0.0 (172.21.0.0) 6.386 ms 8.358 ms 5.721 ms
3 172.21.0.250 (172.21.0.250) 4.597 ms 6.604 ms 6.561 ms
4 172.21.0.249 (172.21.0.249) 5.297 ms 4.870 ms 5.131 ms
5 172.30.255.12 (172.30.255.12) 6.444 ms 7.411 ms 9.599 ms
6 xe7-1-1.sanpaolo8.spa.seabone.net (149.3.181.92) 25.675 ms 56.158 ms 35.142 ms
7 et1-1-0.miami19.mia.seabone.net (89.221.41.187) 129.495 ms
et0-3-0.miami19.mia.seabone.net (89.221.41.161) 129.986 ms
et0-1-0.miami19.mia.seabone.net (89.221.41.171) 130.429 ms
8 be6762.ccr21.mia03.atlas.cogentco.com (154.54.9.17) 132.017 ms 132.948 ms 134.567 ms
9 be3401.ccr22.mia01.atlas.cogentco.com (154.54.47.29) 136.118 ms 132.872 ms 133.447 ms
10 be3482.ccr41.atl01.atlas.cogentco.com (154.54.24.145) 139.584 ms 138.806 ms 139.504 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 147.786 ms
be2113.ccr42.dca01.atlas.cogentco.com (154.54.24.221) 147.498 ms 148.698 ms
12 be2892.ccr22.cle04.atlas.cogentco.com (154.54.82.253) 156.820 ms 165.101 ms 155.317 ms
13 be2993.ccr31.yyz02.atlas.cogentco.com (154.54.31.226) 161.132 ms 161.061 ms 163.390 ms
14 be2094.rcr22.yyz03.atlas.cogentco.com (154.54.81.13) 171.868 ms 173.408 ms 172.261 ms
15 core01.aggr0.tor.fdcservers.net (38.140.220.154) 173.647 ms 173.507 ms 173.413 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * *^C
```
tracert do que funciona (ele chega no servidor final):
```
traceroute s111.podbean.com
traceroute to s111.podbean.com (23.237.42.26), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.165 ms 0.901 ms 3.340 ms
2 172.21.0.0 (172.21.0.0) 9.762 ms 10.020 ms 6.053 ms
3 172.21.0.250 (172.21.0.250) 5.364 ms 4.412 ms 7.939 ms
4 172.21.0.249 (172.21.0.249) 4.607 ms 3.786 ms 4.948 ms
5 172.30.255.12 (172.30.255.12) 5.185 ms 6.723 ms 8.531 ms
6 xe7-1-1.sanpaolo8.spa.seabone.net (149.3.181.92) 21.373 ms 21.196 ms 35.611 ms
7 et2-1-0.miami19.mia.seabone.net (89.221.41.181) 126.320 ms
et1-1-0.miami19.mia.seabone.net (89.221.41.187) 128.060 ms
et2-1-0.miami19.mia.seabone.net (89.221.41.181) 128.821 ms
8 be6762.ccr21.mia03.atlas.cogentco.com (154.54.9.17) 134.505 ms 133.980 ms 132.653 ms
9 be3400.ccr21.mia01.atlas.cogentco.com (154.54.47.17) 128.759 ms 128.880 ms 130.617 ms
10 be3570.ccr42.iah01.atlas.cogentco.com (154.54.84.1) 152.381 ms 153.482 ms 159.937 ms
11 be2928.ccr21.elp01.atlas.cogentco.com (154.54.30.162) 172.285 ms
be2927.ccr21.elp01.atlas.cogentco.com (154.54.29.222) 168.382 ms 169.957 ms
12 be2930.ccr32.phx01.atlas.cogentco.com (154.54.42.77) 177.256 ms
be2929.ccr31.phx01.atlas.cogentco.com (154.54.42.65) 176.554 ms 177.272 ms
13 be2932.ccr42.lax01.atlas.cogentco.com (154.54.45.162) 189.161 ms
be2931.ccr41.lax01.atlas.cogentco.com (154.54.44.86) 187.144 ms
be2932.ccr42.lax01.atlas.cogentco.com (154.54.45.162) 191.491 ms
14 be3069.rcr21.b014796-1.lax01.atlas.cogentco.com (154.54.25.66) 187.611 ms 185.626 ms
be3070.rcr21.b014796-1.lax01.atlas.cogentco.com (154.54.25.70) 191.219 ms
15 * * *
16 * * *
17 23.237.42.26 (23.237.42.26) 190.701 ms !Z 188.464 ms !Z 187.419 ms !Z
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment