nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

500 error when trying to upload project avatar

Sarunas Strasevicius

After JIRA migration i faced that some project avatars are not visible and then i am trying to upload a new one and submit after resizing - window just blinks and do nothing. Browser console show this error:

Failed to load resource: the server responded with a status of 500 ()
batch.js?locale=en:596 ajax[56257501] error : {
successful : false,
status : 500,
statusText : error,
hasData : true,
readyState : 4,
requestId : 56257501,
aborted : undefined,
}

I guess this looks like a permission error just don't understand how to resolve it.

Accepted answers

Sarunas Strasevicius

The problem was that after migration attachments and avatars was uploaded manually and write permissions for directories was set to "root:root". Write access to user "jira:jira" solved the issue.

All comments

Jakub Sławiński

Hi @Sarunas Strasevicius ,

can you share some logs?

Sid_kvhzt3

Hi @Sarunas Strasevicius ,

Avatars are saved in the Jira-home directory, So make sure those directories have read and write access to the account you are running JIRA

Sarunas Strasevicius

I am not a very beginner user, so Yes i know all that stuff. My question is mostly about specific problem only with project avatars, so my concerns is:

1. Did a put all permissions to all needed directories? What is the list of all directories to be checked?

2. If it's really a problem of a permissions? Because user avatars and attachments works fine

Sarunas Strasevicius

Could you define which logs you would like to see?

Jakub Sławiński

You should look for stack-traces in your server logs, probably atlassian-jira.log.

You can find more regarding logging here: https://confluence.atlassian.com/adminjiraserver/logging-and-profiling-938847671.html

Sarunas Strasevicius

I found it, just i see there are plenty of different logs

Which should i look at?

Sarunas Strasevicius

The problem was that after migration attachments and avatars was uploaded manually and write permissions for directories was set to "root:root". Write access to user "jira:jira" solved the issue.