Blank Page on Install via Web Admin
Closed this issue · 8 comments
mrbenns commented
How to post a meaningful bug report
- Read this whole template first.
- Determine if you are on the right place:
- If you were performing an action on the app from the webadmin or the CLI (install, update, backup, restore, change_url...), you are on the right place!
- Otherwise, the issue may be due to the app itself. Refer to its documentation or repository for help.
- When in doubt, post here and we will figure it out together.
- Delete the italic comments as you write over them below, and remove this guide.
Describe the bug
Unable to install Nitter as all I get is a blank section of the App Catalog
Context
- Hardware: Yunohost Virtualbox running on Windows 10
- YunoHost version: 4.2.6.1
- I have access to my server: Through SSH | through the webadmin
- Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
- Using, or trying to install package version/branch: Tried via webadmin and using the github pull
Steps to reproduce
- If you performed a command from the CLI, the command itself is enough. For example:
sudo yunohost app install the_app
- If you used the webadmin, please perform the equivalent command from the CLI first.
- If the error occurs in your browser, explain what you did:
- Go to Applications
- Click on Search and enter Nitter and click Install
- See blank (image attached)
Logs
There is no error message, just a blank section
https://ibb.co/KLfrgNL
Jules-Bertholet commented
You can always install Nitter from the command line: sudo yunohost app install nitter
Jules-Bertholet commented
@dhuschde Logs?
Jules-Bertholet commented
What is the architecture of your Windows machine? (32 bit or 64 bit)
tomaytotomato commented
I am having the same issue on a Debian instance. Blank screen on Firefox and Chromium
changemenemo commented
Just my 2 cents. It s still happening on a up to date install
dumprop commented
I have same problem (ynh 4.2.8.3)
dumprop commented
Just my 2 cents. It s still happening on a up to date install
Installing via terminal helps
yalh76 commented
should be ok with last version