vercel / vercel/hyper

[bug] Running Ansible Playbook to install NextCloud server breaks Hyper for some reason on Ubuntu 18.

Open
#4,039 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
44.7k
Forks
3.6k
Avg merge
21m
Merged PRs (30d)
1

Description

  • I am on the latest Hyper.app version

  • I have searched the issues of this repo and believe that this is not a duplicate

  • OS version and name: Ubuntu 18.04.3

  • Hyper.app version: 3.02

  • Link of a Gist with the contents of your .hyper.js: just using default config. No modifications

  • Relevant information from devtools They won't pop up

  • The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue

Last year I installed Hyper on my linux machine that I was turning into a personal homelab/personal cloud server. At first it worked and then it stopped working. [I could not figure out why it wasn't working. It was very frustrating.] Eventually I just gave up.

But when I eventually decided to do a fresh Linux installation I had hopes that this would fix the problem. Hyper worked again! but then it didn't. And I realized after doing tests that it was because I installed a Nextcloud server on the machine using this ansible playbook: https://github.com/ReinerNippes/nextcloud

I don't know if it's just this particular playbook, or if it's a component of it, or if it's Nextcloud itself, but something weird is breaking Hyper.

I'm going to reinstall Ubuntu and see if I can manually install Hyper and get it to work.

Does Hyper require port access or something? Does it try to run as a server or something and that's what's creating this issue? I know Electron is based on Node so perhaps that's creating some kind of interference with the certbot or nextcloud installation?

This doesn't happen with any other electron based apps.

Here's a link to the bug I've logged with the Ansible playbook repo: https://github.com/ReinerNippes/nextcloud/issues/61

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

No source file or test is identified. Reproduce the failure on Ubuntu 18.04.3 with Hyper 3.02 before and after the linked NextCloud Ansible playbook, then compare the results with the linked playbook issue. Done should identify the component causing Hyper to break and define a reproducible fix or a clear incompatibility report.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, electron, node.js, ubuntu
Domain
desktop, devops, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.