-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: HTTP Proxy - App is stuck at downloading with error: tunneling socket could not be established #2080
Comments
louis-jan
changed the title
bug: HTTP Proxy - Users downloading models from the Hub when HTTPS proxy is turned ON: tunneling socket could not be established
bug: HTTP Proxy - App stuck at downloading with error: tunneling socket could not be established
Feb 22, 2024
louis-jan
changed the title
bug: HTTP Proxy - App stuck at downloading with error: tunneling socket could not be established
bug: HTTP Proxy - App is stuck at downloading with error: tunneling socket could not be established
Feb 22, 2024
3 tasks
@Van-QA , please help to validate this. Thank you! |
Tested and looking good on Jan Jan v0.4.7-295 ✅ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Users downloading models from the Hub encounter an error when HTTPS proxy is turned ON and Proxy endpoint is not working.
Model undefined download failed: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:9028
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
The model should download successfully even when HTTPS proxy is turned ON.
Screenshots
Environment details
Logs
If the cause of the error is not clear, kindly provide your usage logs:
tail -n 50 ~/jan/logs/app.log
if you are using the UItail -n 50 ~/jan/logs/server.log
if you are using the local api serverMaking sure to redact any private information.
Additional context
Add any other context or information that could be helpful in diagnosing the problem.
The text was updated successfully, but these errors were encountered: