Mastodon shows only logo (Tried some fixes from other posts)

[akama-aka]

Hello, everytime I try to open mastodon I get this:

I already viewd and tried these solutions:
#22758,
#20747,
#21169

I hope someone can help me. If more informations needed just send what I should provide

[StrangeMinds1960]

Don't know if this will work for you (if you haven't already found it). I'm sure this is the solution which fixed it for me

'I solved it by including www-data into the mastodon group and viceversa'

[akama-aka]

I linked another discussion in this message and I also tried this but its still not working

We also restarted the Server but still no changes

[rbairwell]

How have you installed Mastodon? From source, from Docker, from DigitalOcean 1-click or some other way?

It looks like the CSS and Javascript hasn't been compiled - have you Installed the latest dependencies and then generated the configuration? Are/were there any errors when you did so?

[akama-aka]

I downloaded from source and it should installed and compiled everything. But I can try again

[akama-aka]

The error at the bottom is because the user already exists in the database

But still same issue:

[selflessmind]

I had the same issue, following the steps from joinmastodon.org. After a lot of searching online it turned out the permissions needed tweaking to access the core files. This is what I had to enter
chown mastodon:www-data /home/mastodon/
chmod 0710 -v /home/mastodon/

[akama-aka]

nope

[flth]

chmod +x /home/mastodon should help.
Fixed it for me right now

[akama-aka]

Nope

[snullp]

This is because nginx unable to read /home/mastodon directory. chmod +rx /home/mastodon/ works for me.

[leopo17]

Using this works for me. Server DigirtalOcean Mastodon Image Droplet. Debian Mastodon 4.2.1, Debian 6.1.
Thanks for help

[shehackedyou]

I have the same issue, works fine in development mode. So I assume it has something to do with assets not being prepared correctly.

[shehackedyou]

RAILS_SERVE_STATIC_FILES=true RAILS_ENV=production bundle exec rails server

This solved it for me, you can add the RAILS_SERVER_STATIC_FILES env to your production.env file, or alias it, or ~/.bashrc since it is outside the project.

There are a lot of solutions each with its own caveats.

Probably best to stick with the production.env file; I would presume it is already in the .gitignore.

I'm pretty confident that will help you too; these wack ideas of changing the permissions on a mastodon user that shouldn't even have a user folder is a bit mind boggling.

[snullp]

Can you try chmod +rx /home/mastodon/ while keep using nginx. This is because nginx unable to read /home/mastodon directory.