Понадобилость с консоли дергнуть по https внутри сетки, но там естественно смысла в домене не было, поэтому самоподписной сертификат для айпишки.
curl https://10.0.15.5/nginx.tgz
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Я понимаю, что частенько листать man обломно, и проще поисковику задать вопрос - "curl игнорировать валидность сертификата"
Вот побыстрому нужный опции curl:
curl -k [URL]
или curl --insecure [URL]
А вот интересующий кусок man curl-а :
-k, --insecure
(TLS SFTP SCP) By default, every secure connection curl makes is verified to be secure before the transfer takes place.
This option makes curl skip the verification step and proceed without checking.
When this option is not used for protocols using TLS, curl verifies the server's TLS certificate before it continues: that
the certificate contains the right name which matches the host name used in the URL and that the certificate has been
signed by a CA certificate present in the cert store. See this online resource for further details:
https://curl.se/docs/sslcerts.html
For SFTP and SCP, this option makes curl skip the known_hosts verification. known_hosts is a file normally stored in the
user's home directory in the .ssh subdirectory, which contains host names and their public keys.
WARNING: using this option makes the transfer insecure.
Example:
curl --insecure https://example.com
See also --proxy-insecure, --cacert and --capath.
возможно у Вас отключен javascript, если включен - просто обновите страницу