-
Notifications
You must be signed in to change notification settings - Fork 36
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
I can't use the web UI anymore after upgrading to 4.2.8~ynh2 #450
Comments
Looks like this happened during testing too: |
Same issue here. :-/ |
Same here. I am happy that it seems a solution is on the way #449 (review) - thank you guys! |
Same issue here, but it is inconsistent between browsers where I've been logged in prior to the upgrade. On some I get the UI but without any working icons. On some I get the screen shown above and can't even log in. Using Mastodon via Apps works. Seems like some style or template stuff isn't working. |
Is there any quick fix for this? :/ |
Same here. Hope there will be a quick fix. Thx! |
Same here. Refused to execute script from 'https://.../packs/js/common-b94cebf75788414c0723.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. |
same here too, |
I have no way to test or reproduce here, but if any of the above have the possibility to check whether upgrading to the testing 4.2.9 release via
would solve this, and report back, that would maybe speed up merging that version into main and hopefully solve this problem. |
Hi @panomaki, I upgraded to the test branch, but unfortunately this doesn't solve the issue :/ |
The update went through without an error message, but the error still occurs (as with @sdfoersn490). A new Mastodon installation (on the same server) is not affected by the error and runs without any problems. So something must have gone wrong with the last update. |
Thanks for trying. It looks similar to #341, so it'd be interesting to see what
shows. If it looks like mentioned in this comment (#341 (comment)), an option could be to recompile the assets:
(If the permissions look differently, so not owned by mastodon:www-data, fix that first) |
ls -lah /var/www/mastodon/live/public/packs/css/
same as mentioned here but node -v says: v20.15.0 |
EDIT: (but i'm not on testing branch) |
link to #429 |
Upgrading to the testing 4.2.10 release via |
Can confirm, upgrading to the 4.2.10 testing branch fixed the issue for me too! Not relevant for this ticket, but maybe for 4.2.10 testing: I got some warnings during the upgrade:
However, the building process was completed without any errors. |
better on firefox yes, but not on chromium : https://masto.krashboyz.org/ is still buging |
On my Chromium all looks good. Make sure you clear your browser's cache. |
@tio-trom : correct ! thx :) |
Can confirm. Issue solved after upgrading fdrom 4.2.8 to 4.2.10-ynh1 |
Same here updating to 4.2.10-ynh1 fixes it. |
Describe the bug
Hi guys, I can't use the web UI anymore after upgrading to 4.2.8~ynh2
Context
Steps to reproduce
*If you performed a command from the CLI, the command itself is enough.
sudo yunohost app upgrade mastodon -u https://github.com/YunoHost-Apps/mastodon_ynh --debug
*If the error occurs in your browser, explain what you did:
All I see is this:
Expected behavior
LDAP Login or Timeline view
Note: Access via Apps like IceCubes is still working fine
Logs
No Errors in logs:
https://paste.yunohost.org/raw/fatuzapola
How can I fix this?
The text was updated successfully, but these errors were encountered: