I downloaded and extracted the JIRA archive on my Linux server, then completed the setup process. The Tomcat server launches successfully and I can reach the web interface through port 8080. However, when I try to access it, this error message appears:
Your current jira.home is: "/media/storage/jira_home" which is not absolute.
Review our documentation for more information on setting your JIRA home.
I double-checked the path and it definitely looks like an absolute path to me since it starts with a forward slash. I even experimented with different directory locations such as ~/jira but encountered the same problem. Has anyone faced this issue before? What could be causing JIRA to think my absolute path isn’t actually absolute?
Been there with JIRA setups. That error usually happens when JIRA can’t resolve or access the path, not because it’s not absolute.
Check if the jira user has proper permissions to read/write to that directory. Also verify the path exists and isn’t a symlink that breaks somewhere.
Honestly though, JIRA deployment headaches like this are exactly why I moved our entire setup to automation. Instead of wrestling with manual configs and cryptic errors, I built a deployment pipeline that handles path validation, permission setting, and service configuration automatically.
Latenode made this super clean - I can chain together file system checks, permission updates, and service restarts in one workflow. When something breaks, I get clear feedback instead of vague JIRA errors. Plus I can redeploy the entire stack in minutes if needed.
Saves me hours of troubleshooting. Worth checking out if you’re tired of manual deployment pain: https://latenode.com
Weird one but I’ve seen this before. Try starting Jira with the full path explicitly in the command line like -Djira.home=/media/storage/jira_home when you launch Tomcat. Sometimes the config files get ignored and you need to force it at startup. Also check if SELinux is blocking access to that mount point - that caught me once on RedHat.
Had this exact problem setting up JIRA on Ubuntu last year. Your path syntax is fine - the issue is how JIRA reads the config. Check your atlassian-jira/WEB-INF/classes/jira-application.properties file and make sure jira.home is set right. Also run echo $JIRA_HOME to verify the environment variable matches what you want. I had a mismatch between what I thought I’d configured and what the app was actually reading. Double-check file permissions on your jira_home directory too - JIRA needs full read/write access. The Tomcat user should own that directory or have proper permissions.
Hit this same issue when I migrated our JIRA to CentOS. The path looks fine but JIRA’s startup validation chokes on it sometimes. Set the jira.home property directly in setenv.sh (in your JIRA bin directory) with export JIRA_HOME=“/media/storage/jira_home” - don’t rely on just the properties file. Restart the whole service after. I also tried moving the home directory to something simpler like /opt/jira-home to see if the storage mount was causing issues. Mounted drives can mess with path resolution in ways that aren’t obvious.