-
Notifications
You must be signed in to change notification settings - Fork 93
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
Can't access fresh install - Stylesheets fail integrity metadata check #31
Comments
Same issue here. Did you find solution? |
I went a different route back then, back as far as I know now it should be related to the assets not having been precompiled successfully. You can try manually running the command ```
|
UPDATE: purging Cloudflare's cache appears to have resolved this issue for me. I'm encountering this issue on multiple versions, including 4.2.3 but going back quite a ways. I see a warning when precompiling assets, but it doesn't appear to be the problem to me.
From browser console:
|
Thank you for posting this. I've spent an hour trying to figure out what's going on and it was Cloudflare. Cache cleared and my front-end is loading once more. |
Hi all,
I have installed Mastodon using this Helm Chart on my cluster and I am having trouble accessing it.
I have an Nginx Ingress Controller in front of the containers with Domain and a valid SSL cert configured.
Every time I navigate to the URL I only see 2 icons and receive a lot of errors regarding the integrity of the stylesheets in the console:
Judging by the network tab, the stylesheets are loading fine and the content looks okay as well.
I couldn't find any errors in any of the pods either and the precompile command ran successfully also.
Using Safari or Chrome result in the same issue.
Does anyone have an idea what the error could be or even just how I could go about debugging this?
I tried manually port-forwarding port 3000 from the web container to see if I could access the site that way, but my connection seems to get refused immediately.
Thanks a lot!
The text was updated successfully, but these errors were encountered: