-
-
Notifications
You must be signed in to change notification settings - Fork 887
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ERROR: Your Owncast installation did not complete successfully. #3902
Comments
here is the full print out To run a command as administrator (user "root"), use "sudo ". owncast@owncast-virtual-machine: Created directory [✓] ERROR: Your Owncast installation did not complete successfully. owncast@owncast-virtual-machine:~$ |
You might try un-installing curl (sudo snap remove curl), and try with 'sudo apt install -y curl' If that doesn't help, are you able to write to /tmp as your regular (non-root) user? What is the output of this command? touch /tmp/foo (There should be no output if the command succeeds.) |
Yes I am able to write to it, there is no output of it owncast@owncast-virtual-machine: The text file that it created was blank. |
i did the the "sudo snap remove curl" at a different window and appeared to work just fine, I restarted the VM, here is the output of this screen. owncast@owncast-virtual-machine:~$ sudo apt install -y curl owncast@owncast-virtual-machine:~$ curl -s https://owncast.online/install.sh | bash Existing install found in this directory. Will update it to v0.1.3. If this is incorrect remove the directory and rerun the installer. ERROR: Your Owncast installation did not complete successfully. owncast@owncast-virtual-machine:~$ |
It creates the 'data' directory the first time you run owncast, so the backup failed because it doesn't exist.
Also, it looks like 128 packages are out of date, might want to update those with
|
that seem to do it, its working now, thank you owncast@owncast-virtual-machine:~$ rm -rf Created directory [✓] Success! Run owncast by changing to the owncast directory and run ./owncast. owncast@owncast-virtual-machine: |
looks like i am having the same issue.... [root@localhost owncast-1]# curl -s https://owncast.online/install.sh | bash Created directory [✓] ERROR: Your Owncast installation did not complete successfully. [root@localhost owncast-1]# rm -rf ~/owncast Existing install found in this directory. Will update it to v0.1.3. If this is incorrect remove the directory and rerun the installer. ERROR: Your Owncast installation did not complete successfully. [root@localhost owncast-1]# rm -rf ~/owncast Existing install found in this directory. Will update it to v0.1.3. If this is incorrect remove the directory and rerun the installer. ERROR: Your Owncast installation did not complete successfully. [root@localhost owncast-1]# |
I am using Rocky linux |
It mentions in the log what's going on:
It thinks Owncast is already setup there because there's probably a directory called |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this was a feature request that others have shown no interest in, then it's unlikely to get implemented due to lack of interest. If others also want to see this feature then now is the time to say something! If this is a bug report or you have questions that still need answering, please say something. Feel free to drop by our chat if you'd like to discuss in real-time with people. |
Share your bug report, feature request, or comment.
wncast@owncast-virtual-machine:~$ curl -s https://owncast.online/install.sh | bash
Owncast Installer v0.1.3
Created directory [✓]
Downloaded Owncast v0.1.3 for linux [✓]
unzip: cannot find or open /tmp/tmp.OaHVPPGsg0/owncast-0.1.3-linux-64bit.zip, /tmp/tmp.OaHVPPGsg0/owncast-0.1.3-linux-64bit.zip.zip or /tmp/tmp.OaHVPPGsg0/owncast-0.1.3-linux-64bit.zip.ZIP.
ERROR: Your Owncast installation did not complete successfully.
Please report your issue at https://github.com/owncast/owncast/issues
This is a brandnew VM, I do not know what the issue is.
The text was updated successfully, but these errors were encountered: