Skip to content
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

Cannot clone repo with non-standard port #14

Open
Abraxos opened this issue Feb 7, 2016 · 3 comments
Open

Cannot clone repo with non-standard port #14

Abraxos opened this issue Feb 7, 2016 · 3 comments

Comments

@Abraxos
Copy link

Abraxos commented Feb 7, 2016

I have sandstorm configured to use HTTPS on port 44344 (I dont know whether this is actually the cause of the issue, its merely a suspcicion). When I first create a repo it tells me to use the following commands:

 echo url=https://<random id>:<random data>@api.marvin.sandcats.io:44344/gitlab/repo.git | git -c credential.helper=store credential approve
 git clone -c credential.helper=store https://<random id>@api.marvin.sandcats.io:44344/gitlab/repo.git repo_<random id>_RENAME_ME

Note that this is what it outputs, including the repo.git whereas the actual name of the repo is "tech_reference". The only thing that was changed was the ID and key.

I tried to execute the exact commands above and I get the following error:

Cloning into 'repo_<random id>_RENAME_ME'...
fatal: repository 'https://<random id>@api.marvin.sandcats.io:44344/gitlab/repo.git/' not found

Or if I try to use the repo's actual name I get:

Cloning into 'repo_<random id>_RENAME_ME'...
fatal: repository 'https://<random id>@api.marvin.sandcats.io:44344/gitlab/tech_reference.git/' not found

I don't know if this is a coding issue or whether I have a misconfiguration, but please advise.

@dwrensha
Copy link
Owner

dwrensha commented Feb 7, 2016

Looks like this is the same problem as was reported in #7. For now, I recommend keeping the default name for the repository.

@Abraxos
Copy link
Author

Abraxos commented Feb 7, 2016

That should work for now. Thanks!

Are there any plans to fix this issue though? If not then maybe a friend of mine and I could take a look at it.

@xet7
Copy link

xet7 commented Jul 31, 2018

This issue was moved to sandstormports/gitlab-sandstorm#9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants