TL;DR

• The issue can likely be resolved by configuring ollama to use the https protocol or setting the http_proxy environment variable to route traffic through the proxy.

Guidance

• Verify that the http_proxy environment variable is set correctly and that ollama is configured to use it.
• Check if the proxy server supports both http and https protocols and if there are any specific settings required for ollama to work behind the proxy.
• Test downloading models using https to confirm that the issue is specific to http requests.
• Consider setting the https_proxy environment variable as well to ensure that both http and https traffic is routed through the proxy.

Example

• No specific code snippet is provided as the issue seems to be related to configuration and environment variables rather than code.

Notes

• The issue seems to be specific to ollama version 0.20.2 and may not be present in other versions.
• The fact that models published via https work fine suggests that the issue is related to the protocol used rather than the proxy configuration itself.

Recommendation

• Apply workaround: Set the http_proxy and https_proxy environment variables to route traffic through the proxy, as this is a simpler and more immediate solution than upgrading ollama or modifying its configuration.