The Movie Database-ondersteuning
Ondersteuning → API-ondersteuning
Ip blocked?
geplaatst door sam117STAFFMOD op 12 september 2024 om 5:00 AM
Hi. Seems my ip been blocked
dig:
# dig api.themoviedb.org
; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> api.themoviedb.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10614
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;api.themoviedb.org. IN A
;; ANSWER SECTION:
api.themoviedb.org. 60 IN A 18.239.18.34
api.themoviedb.org. 60 IN A 18.239.18.52
api.themoviedb.org. 60 IN A 18.239.18.129
api.themoviedb.org. 60 IN A 18.239.18.114
;; Query time: 28 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Thu Sep 12 11:55:39 EEST 2024
;; MSG SIZE rcvd: 111
# dig image.tmdb.org
; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> image.tmdb.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8060
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;image.tmdb.org. IN A
;; ANSWER SECTION:
image.tmdb.org. 5 IN CNAME tmdb-image-prod.b-cdn.net.
tmdb-image-prod.b-cdn.net. 35 IN A 138.199.36.7
;; Query time: 16 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Thu Sep 12 11:55:30 EEST 2024
;; MSG SIZE rcvd: 98
wget (http/https):
wget http://image.tmdb.org/t/p/w440_and_h660_face/aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg
--2024-09-12 11:57:13-- http://image.tmdb.org/t/p/w440_and_h660_face/aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg
Resolving image.tmdb.org (image.tmdb.org)... 169.150.247.34, 2400:52e0:1e00::863:1
Connecting to image.tmdb.org (image.tmdb.org)|169.150.247.34|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 23709 (23K) [image/jpeg]
Saving to: ‘aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg.1’
aTpMwcMzgwUfs5mY8WJEhBn7Q7y.j 0%[ ] 0 --.-KB/s
stuck here.
On other server same command gets image normaly:
wget http://image.tmdb.org/t/p/w440_and_h660_face/aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg
--2024-09-12 11:59:44-- http://image.tmdb.org/t/p/w440_and_h660_face/aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg
Resolving image.tmdb.org (image.tmdb.org)... 138.199.37.231
Connecting to image.tmdb.org (image.tmdb.org)|138.199.37.231|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 23709 (23K) [image/jpeg]
Saving to: ‘aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg’
aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg 100%[==================================================================================================================>] 23.15K --.-KB/s in 0s
2024-09-12 11:59:44 (224 MB/s) - ‘aTpMwcMzgwUfs5mY8WJEhBn7Q7y.jpg’ saved [23709/23709]
Reactie van Travis Bell
op 12 september 2024 om 10:53 AM
Hi @sam117,
You're getting a
169.xaddress back on the first server which is an internal IP, so it's not going to work. Depending on where you are located, I suspect that perhaps you're hitting the Russian block.Reactie van sam117
op 12 september 2024 om 3:44 PM
nop. Apipa uses 169.254.0.0/16, 169.150.247.34 not in.
with hosts file record i can get images:
server in finland, but russian block still posible. mayby dead server? or blacklist\f2ban on it
wierd...