Set-up in Docker fails: time-out resolving ftp.pcre.org

[maticserc]

Hi, I'm trying to set up API Umbrella in Docker according to documentation on https://api-umbrella.readthedocs.io/en/latest/developer/dev-setup.html and it fails in the process, as it can't resolve one of the ftp hosts.

• clean_task_working_dir
• set +x
• [[ -d /app/build/work/tasks/deps/openresty ]]
• [[ '' != \t\r\u\e ]]
• cd /app/build/work/tasks/deps/openresty
• find /app/build/work/tasks/deps/openresty -mindepth 1 -maxdepth 1 -not -name _persist -print -exec rm -rf '{}' ';'
• download https://ftp.pcre.org/pub/pcre/pcre-8.45.tar.bz2 md5 4452288e6a0eefb2ab11d36010a1eebb
• set +x
• curl --location --retry 3 --fail --output /app/build/work/tasks/deps/openresty/_persist/downloads/pcre-8.45.tar.bz2 https://ftp.pcre.org/pub/pcre/pcre-8.45.tar.bz2 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: ftp.pcre.org Warning: Problem : timeout. Will retry in 1 seconds. 3 retries left. 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: ftp.pcre.org Warning: Problem : timeout. Will retry in 2 seconds. 2 retries left. 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: ftp.pcre.org Warning: Problem : timeout. Will retry in 4 seconds. 1 retries left. 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: ftp.pcre.org task: Failed to run task "deps:openresty": exit status 6 make: *** [Makefile:24: task-passthrough] Error 1

[maticserc]

if I try with: https://api-umbrella.readthedocs.io/en/latest/getting-started.html#running-with-docker then I manage to run the API Umbrella, but when accessing the web interface, I get back "502 Bad Gateway" error.

Any hints on how to make it work are welcome.

[muzifeng1008]

按照文档中说的：运行curl https://bintray.com/nrel/api-umbrella-el7/rpm | sudo tee /etc/yum.repos.d/api-umbrella.repo 直接403 了，api-umbrella不是不是不在维护了

[AbhiPawar5]

Hi @maticserc, I am facing the same issue now. Did you resolve it? Thanks.