-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Extension Page Not Loading #468
Comments
You are probably downloading the jar release of tachidesk, it doesn't work with Java installed from Oracle. Download and install the msi release or the zip release and open launchers instead of tachidesk jar |
duplicate of #237 |
@AriaMoradi I downloaded both msi and zip and tried using the launcher only, nothing happened , only then I raised the query |
logfile.log |
Same issue on Ubuntu 22.04 with a package from the official ppa. I’m using only the official launchers @AriaMoradi are you sure this is the same issue? Description of the issues are different after all....
Full Logs: tachidesk-server-debug.txt |
Device information
Steps to reproduce
Expected behavior
It should have showed different extensions to install
Actual behavior
It showed the loading circle than blank page
Other details
I downloaded tachidesk's latest version on my pc when I ran it my pc showed warning I clicked continue anyway than a firewall block I allowed that also it landed me on the home page of tachidesk in my browser I navigated to the extension page when I opened it it showed me the loading circle and then it stopped it didn't showed me even a single extension and it didn't showed me any error or issue that has been occurring I searched the GitHub page and used the methods mentioned there but nothing happened then I removed all tachidesk file from my pc and reinstalled it and tried it in different browser but the same thing happened and again same for the third browser. I thought it was a server error so I stopped trying and tried again today but back to square one the same glitch.
The text was updated successfully, but these errors were encountered: