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

Private repo not working #39

Open
KammererTob opened this issue Jan 25, 2018 · 6 comments
Open

Private repo not working #39

KammererTob opened this issue Jan 25, 2018 · 6 comments

Comments

@KammererTob
Copy link

Not sure if the documenation is not accurate enough or i am doing something wrong, but i cannot get the setup to run properly.
This is my command:
now -e TOKEN=@github-token -e ACCOUNT="MyAccount" -e REPOSITORY="MyRespository" -e PORT="80" zeit/hazel

This is the message i get immediatly and i need to supply the password for my ssh file:

Didn't find directory. Searching on GitHub...

And this is the error i am getting after ~30 seconds:

Error! Unexpected error. Please try again later. (An unexpected internal error occurred)

What am i doing wrong?

@KammererTob
Copy link
Author

KammererTob commented Jan 26, 2018

I initially closed the issue, because i thought that it wasn't possible to proxy a private repo through to the application to update, but now i read that it should indeed be possible. So additionally to the problem above: Is it possible to use a private GitHub Repository with Hazel, without needing to own a server for a proxy?

@KammererTob KammererTob reopened this Jan 26, 2018
@KammererTob
Copy link
Author

I tried to debug now with a public repository and this is what it says:

[debug] Retrying: Error: An unexpected internal error occurred
Error: An unexpected internal error occurred
at module.exports.EventEmitter.create.deployment.retry (C:\snapshot\now-cli\dist\now.js:437:15)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
[debug] get files ready for deployment: 0.298ms
[debug] v2/now/deployments: 1266.614ms
[debug] Retrying: Error: An unexpected internal error occurred
Error: An unexpected internal error occurred
at module.exports.EventEmitter.create.deployment.retry (C:\snapshot\now-cli\dist\now.js:437:15)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
[debug] get files ready for deployment: 0.349ms
[debug] v2/now/deployments: 1211.761ms
[debug] Retrying: Error: An unexpected internal error occurred
Error: An unexpected internal error occurred
at module.exports.EventEmitter.create.deployment.retry (C:\snapshot\now-cli\dist\now.js:437:15)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
[debug] get files ready for deployment: 0.383ms
[debug] v2/now/deployments: 1143.849ms
[debug] error: Error: An unexpected internal error occurred
Error: An unexpected internal error occurred
at module.exports.EventEmitter.create.deployment.retry (C:\snapshot\now-cli\dist\now.js:437:15)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
Error! Unexpected error. Please try again later. (An unexpected internal error occurred)

Might be a problem with now rather than hazel. Hard to grasp what's going on, since the error is not very specific. I also tried to disable any firewall/anti-virus.

@onekiloparsec
Copy link

onekiloparsec commented Jan 29, 2018

I removed my comment because I actually succeeded, with a private repo. I use the workflow: now secret add github_token <token> then, now -e TOKEN=<github_token> zeit/hazel and... it worked.

My mistake was to include my username also in the repo name. Hence it appeared twice in the url.

@KammererTob
Copy link
Author

@onekiloparsec Yeah i think my problem is not related to the private repository since i also cannot deploy when using a public repository.

@mcverticchio
Copy link

mcverticchio commented Jan 30, 2018

I generated a token with private repo access. I am on a team that has access to our project. I was not able to deploy an update server following the workflow below, but my coworker was able to following the same steps. Sounds like a bug?

Workflow:
now secret add my_token <token>
now -e TOKEN=@my_token zeit/hazel

My error:

Didn't find directory. Searching on GitHub...

After a few seconds I am prompted for the passphrase to my ssh/id_rsa key.
(my coworker is not asked for this)

@backroot
Copy link

backroot commented Oct 4, 2020

This issue resolve in my pull request #98 .
Example for autoUpdater.ts.

import { autoUpdater } from "electron-updater";

const server = "https://hazel-xxxx.vercel.app";
const feed = `${server}/update/${process.platform}/${app.getVersion()}`;

autoUpdater.setFeedURL(feed);

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

4 participants