Failed to connect to applist.heimdall.site

[Mangeloco]

Getting this in logs, using Portainer I can actually access it and curl it from the console of that docker, but I still get this error. When I try to open Heimdall in the browser, i get a 500 Server error probably because of it. Help please

[Mangeloco]

In CurlFactory.php line 210:

cURL error 28: Failed to connect to appslist.heimdall.site port 443 after 1

4090 ms: Operation timed out (see https://curl.haxx.se/libcurl/c/libcurl-er

rors.html) for https://appslist.heimdall.site/list.json

[webysther]

Same #909

[goosebumpage]

In CurlFactory.php line 210:

cURL error 28: Failed to connect to appslist.heimdall.site port 443 after 1

4090 ms: Operation timed out (see https://curl.haxx.se/libcurl/c/libcurl-er

rors.html) for https://appslist.heimdall.site/list.json

Getting the exact same issue after installing it in docker.

[maxage]

Same error message: cURL Error 6: Unable to resolve host: appslist.heimdall.site (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) https://appslist.heimdall.site/list.json

CURLE_COULDNT_RESOLVE_HOST (6) Could not resolve host. The given remote host was not resolved.

I can access https://appslist.heimdall.site/list.json

Error： SERVER ERROR

[keriati]

@maxage what version of heimdall did you use?

[svanhoutte]

I have the same issue. It seems the image cannot negotiate TLS correctly with applist.heimdall.site. From the docker standpoint internet works, and other websites in https are working such as google and facebook. Any idea on what issue this could be ? I m running 2.5.5 version in docker.

[iomarcovalente]

I have the same issue. It fails with error 500 when trying to connect to https://appslist.heimdall.site/list.json

   GuzzleHttp\Exception\ConnectException 

  cURL error 28: Operation timed out after 15001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://appslist.heimdall.site/list.json

  at /app/www/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:210
    206▕         }
    207▕ 
    208▕         // Create a connection exception if it was a specific error code.
    209▕         $error = isset($connectionErrors[$easy->errno])
  ➜ 210▕             ? new ConnectException($message, $easy->request, null, $ctx)
    211▕             : new RequestException($message, $easy->request, $easy->response, null, $ctx);
    212▕ 
    213▕         return P\Create::rejectionFor($error);
    214▕     }

      +13 vendor frames 
  14  /app/www/app/SupportedApps.php:157
      GuzzleHttp\Client::request()

  15  /app/www/app/Jobs/ProcessApps.php:42
      App\SupportedApps::getList()

In my case it might as well be that I am hitting corporate firewall and that site is not whitelisted, but after checking with "is it down", it seems that the website is down?

What's the purpose of that file and is it possible to mount it somewhere locally so to avoid that problem altogether?

[ghost]

I have the same problem. On Qnap with Docker-Compose. Any idea ?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[Gunb0at-Dipl0mat]

Hit this issue with Heimdall in Kubernetes. The URL https://appslist.heimdall.site/list.json is missing the last dot to become a full FQDN and it kept unsuccessfully looping through the domains in my /etc/resolv.conf with the default ndots value 5.

Manually curling in the pod showed the same error: kubectl exec -i -t heimdall-5b449d6554-g29xk -- curl -I https://appslist.heimdall.site/list.json | head -n 2 curl: (6) Could not resolve host: appslist.heimdall.site command terminated with exit code 6 Curling the FQDN including the dot works. kubectl exec -i -t heimdall-5b449d6554-g29xk -- curl -I https://appslist.heimdall.site./list.json | head -n 2 HTTP/2 200 server: GitHub.com

I tried setting the variable APP_SOURCE to the adjusted FQDN with the dot, but no success. Worked around the issue by reducing the ndot value for the pod.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue is locked due to inactivity