Today i upgraded my mastodon.
And I got 404 error when load resources on packs folder.
Some thing like following image

I check mastodon-streaming.service and get error
mastodon-streaming.service stop-final-sigterm timed out. Killing.
Unit mastodon-streaming.service entered failed state.
mastodon-streaming.service failed.
Please help me
master (If you're a user, don't worry about this).What do you see inside the public/packs folder? Is nginx configured to serve files from the public directory?
@Gargron
What do you see inside the public/packs folder?
Inside pack folder have some css and js files. Files in above image are being included.
Is nginx configured to serve files from the public directory?
Yes it is. It worked fine before upgrade
It appears nginx have read permission on public folder.
I check on nginx log and see errors like this:
2017/06/06 12:29:12 [crit] 28119#28119: *1 stat() "/home/mastodon/live/public/packs/common-da0b8691fb2398ab5a51.css" failed (13: Permission denied)....
Maybe my nginx run base on nginx user and mastodon application on mastodon user
--> Nginx cant access to mastodon.
But I dont know why before update it worked so smoothly!!!
I m so sorry.
Did you fix this issue? I'm having the same problem. What was the solution?
Yes i did. Maybe your nginx server and mastodon app are running on 2 user.
Soluton 1: setting for nginx running base on mastodon user.
Solution 2: setting permission read for nginx user on mastodon user's home directory
'''
chmod +x /home/mastodon
'''
Most helpful comment
Yes i did. Maybe your nginx server and mastodon app are running on 2 user.
Soluton 1: setting for nginx running base on mastodon user.
Solution 2: setting permission read for nginx user on mastodon user's home directory
'''
chmod +x /home/mastodon
'''