Question on creating self-hosted application to Github

[benlarr]

Folks, I am trying to deploy a self-application to github using my personal windows machine. I create the repo, added the self-hosted runner and start executing the commands. All the commands executed successfully except for the config command. I am getting the following errors:
PS C:\action-runner> ./config.cmd --url https://github.com/benlarr/jcrepo --token BTDEX3RTPXET6KL54M5BKNTIHQCWW

Http response code: NotFound from 'POST https://api.github.com/actions/runner-registration' (Request Id: D22B:3294A1:7A4FAF7:7E7E188:683C5A6C)
{"message":"Not Found","documentation_url":"https://docs.github.com/rest","status":"404"}
Response status code does not indicate success: 404 (Not Found).

[juan-miii]

Hi there! 👋

Just a heads-up: GitHub Actions runners are used to execute your workflows (CI/CD pipelines) by running jobs defined in your .github/workflows directory. A self-hosted runner means you're running those jobs on your own machine (like your Windows PC), rather than on GitHub's hosted infrastructure.

Regarding your issue: the error you're seeing (404 Not Found) usually means that the repository URL is incorrect or the token is invalid/expired. I cannot check that the repository URL https://github.com/benlarr/jcrepo is correct (as it seems to be private) and that the token hasn’t expired or is not meant for another repo.

⚠️ Also — be careful! You’ve shared a registration token publicly. This token is sensitive and allows others to register runners to your repo. Revoke it immediately from your repository's Actions settings and generate a new one.

[benlarr]

Hello, Thanks for your insight! I do understand that I run those jobs on my windows my machine. However, after executing the run.cm command from my machine, the machine connects to github. Also, in the current example, I have xxx.yml file which contains the script that runs the job. To run the job, I go to my repo, and workflow, locate the xxx.yml file and run it. That’s the process I have followed and it seems to work. Let me know if this makes sense. Thanks, JC From: Juan Miguel ***@***.***> Sent: Friday, June 6, 2025 11:11 PM To: community/community ***@***.***> Cc: benlarr ***@***.***>; Author ***@***.***> Subject: Re: [community/community] Question on creating self-hosted application to Github (Discussion #161223) Hi there! 👋 Just a heads-up: GitHub Actions runners are used to execute your workflows (CI/CD pipelines) by running jobs defined in your .github/workflows directory. A self-hosted runner means you're running those jobs on your own machine (like your Windows PC), rather than on GitHub's hosted infrastructure. Regarding your issue: the error you're seeing (404 Not Found) usually means that the repository URL is incorrect or the token is invalid/expired. I cannot check that the repository URL https://github.com/benlarr/jcrepo is correct (as it seems to be private) and that the token hasn’t expired or is not meant for another repo. ⚠️ Also — be careful! You’ve shared a registration token publicly. This token is sensitive and allows others to register runners to your repo. Revoke it immediately from your repository's Actions settings and generate a new one. — Reply to this email directly, view it on GitHub <#161223 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BTDEX3SKQLMICUMRSAWSA5L3CJ7A7AVCNFSM6AAAAAB6LFR5UWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZZGU4DIMA> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BTDEX3X6RVPIKIT6LV5TSR33CJ7A7A5CNFSM6AAAAAB6LFR5UWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAZRTYA.gif> Message ID: ***@***.*** ***@***.***> >

[juan-miii]

Yeah, that makes sense! Sorry for the misunderstanding — I thought you were trying to deploy the application directly on a runner, but as it stands, runners are just for CI/CD with their current capabilities.

As for the setup, it does make sense. Just keep in mind that typical CI/CD workflows are usually triggered by a push or pull request to the repo. That can simplify your workflow by running automatically on each push, instead of having to manually go to Actions and trigger a workflow (this implies having your machine working so it can process the request). But of course, since I don’t know the specifics of your case, your current setup is totally fine as it is.