-
Notifications
You must be signed in to change notification settings - Fork 13
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
failing fetch from https server with unknown ssl certificate #3
Comments
That doesn't look like an SSL error. I'm pretty sure urllib2 doesn't even try to verify certificates by default. |
The computed URL is probably not the right one. You can set a custom one in a |
I think that goes in the right direction. I looked into the bitbucket url and modified the .lfsconfig file (see below).
I know that the final url looks like: So it would be good if I could print the url which the script attempts to get, to then find out what I need to set in .lsfconfig.
Note: the git repo address contains lower case: "username" whereas the url for LFS has capital letters: "USERNAME" - the "standard" git lfs client resolves this url correctly. I don't know anything about the internals, so I don't know how this is done correctly. |
The script is showing you the URL it's attempting to get, it's |
You can find the right URL through the official client: |
git lfs env gives me: I assume that's what I should look for?
and getting back the same error as initially with:
I would really like to isolate the problem more or add more debug output, but I don't know how to get more out of this. If what I have set in .lfsconfig was correct, the same fetch address ( |
What does |
--> manually adding the port changes this a little:
With chrome I get:
Firefox gives me:
Lynx gives me:
Interestingly bitbuckets webinterface is on another port than the git url. and the bitbucket url works fine (apart from the need to ignore the ssl certificat warnings) And - using the normal git lfs client just works... |
Is your repository private? The output of |
The repository is not private - it is public:
-> is enabled in the Bitbucket UI. Although it may be a requirement to work in long term I believe. But I'd rather solve the current problem first... I'll prepare an output of |
Since the repo is public can you give me its real URL so I can try things myself? |
Since the repo is public can you give me its real URL so I can try things
myself?
Sorry,
It is only public in an internal network.
I'm happy to run more debugging.
|
I'm trying to fetch the LFS files with:
python -m git_lfs -vv
but then I get:
For git via https I have to set
to make clones and pulls work.
It could be, that the reason of the problem is the same, but git_lfs doesn't recognize this setting.
The text was updated successfully, but these errors were encountered: