immense / immense/Remotely

Linux Remotely Server Installer Build Actions fails

Open
#502 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
5.1k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

Build using latest linux installer binary fails (**v2022.08.02.0428**)

**To Reproduce**
Steps to reproduce the behavior:
1. Forked immense/Remotely repo
2. enabled Actions
3. added new token for authentication
4. checked pinging the target url
5. downloaded latest linux "Remotely_Server_Installer" binary
6. called the installer with the following arguments from bash on my ubuntu host:

````bash

./Remotely_Server_Installer -b false -r latest -u Basti-Fantasti -p ghp_xxxxx -s https://my.remotely.install -i /var/www/remotely/ -w 1 -c true

````

and here's the output:

````
Performing server install. GitHub User: Basti-Fantasti. Server
URL: https://my.remotely.install/. Installation Directory: /var/www/remotely/.
Web Server: UbuntuNginx. Create New Build: True. Git Reference:
v2022.08.02.0428

Get artifacts response status code: OK

Trigger GitHub Actions build.

Dispatch response status code: UnprocessableEntity

[PerformInstall] GitHub API call to trigger build action failed.
Do you have Actions enabled on your forked Remotely repo on
the Actions tab? If not, enable them and try again. Otherwise,
please check your input parameters.

Installation completed.

````

**Remotely Version**
Linux Installer: v2022.08.02.0428

**Expected Behavior**
smoothly run the installation 😄

**Screenshots**

enabled actions in my repo

![2022-08-02 21_46_42-Actions · Basti-Fantasti_Remotely](https://user-images.githubusercontent.com/1663072/182460437-0447b5f6-afb2-4b17-96ed-900522f0cc0e.png)

privileges of access token

![2022-08-02 21_49_29-Edit personal access token](https://user-images.githubusercontent.com/1663072/182460938-12589f15-9942-4903-a30a-e152f5b35b95.png)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Remotely_Server_Installer invocation with the reported arguments and inspect the GitHub Actions dispatch that returns UnprocessableEntity. Done means the installer successfully triggers the build action and completes the Linux installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, github-actions, linux
Domain
build-system, ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.