JIRA 3.13.5 is inaccessible after unexpected server restart

[Adam Rofer]

I'm using 3.13.5 (we're also currently investigating an upgrade to 4.4 in the near future), and an unexpected VM power cycle caused the instance to restart unexpectedly.

Now JIRA refuses to be accessible via web page, even though the logs don't complain. I've verified the MySQL DB is up and accessible. Cannot even access it via localhost. I've manually added 127.0.0.1 localhost in the HOSTS file to see if that would help, to no avail.

JIRA manages to export every time I start it (quartz scheduled), so I know it's accessing the DB. It's possible Windows Updates installed after the reboot, but I can't think of what would cause this issue.

Any ideas?

(Windows Server 2008 R2 Standard)

[Jo-Anne MacLeod]

if its now working via localhost, check to see if it is relaying. I'll pull up my instance and get the exact command for you.

[Adam Rofer]

Yes, it is now working on localhost only (didn't for quite some time, though). Let me know how I can check relaying.

I think my network is having issues since I cannot even ping the IP - thanks for the quick response but I think it's up to my IT department now.

[Jo-Anne MacLeod]

Yup, it sounds like its a network issue. You IS dept should be able to sort it out.

[Adam Rofer]

FIXED. It was *%&$ing Windows Firewall, of course. Disabling it brought everything back to functional.

Thanks for the quick assistance!

[Jo-Anne MacLeod]

Did you try to do a clean shutdown, and a reboot, just to see if that would clear up the problem?

[Jo-Anne MacLeod]

can you access it from the browser on the machine? http://localhost

d'oh, you just said that you can't. Sorry, should have read better.

[Adam Rofer]

YES, now.

ARGH it just showed up on localhost as I was double checking! It wasn't working a minute ago.

Now the issue is just that I can't access from other machines...