JIRA Base URL Issue

[William Wells]

In the past I've installed JIRA on a few VMs, but didn't bother worrying with a DNS or anything because it was an evaluation. Now I've been working with another team and during my installation setup for JIRA 5.0.2, we are running into a problem where the Base URL is not accepted if we use a full system name (i.e., myJIRAserver.domain.com). However, if I use the IP or the short host name (i.e., myJIRAserver). From my understanding, Atlassian is using a java class provided by Apache commons that is causing the fail because the end of our URL is not part of the TLD (Top Level Domains). Is there some way we can modify a file somewhere so it can identify our URL TLD?

[William Wells · Accepted solution]

I found out what the real problem is. We have a special suffix to our URL that is NOT considered to be part of the recognized TDL. (For instance, something like .will or .dew). Apparently there's no real way to fix this at this point, but an Atlassian ticket has been submitted to have it fixed in future releases. For now, we just have to use the IP or short name without the suffix to get the base URL accepted.

So for instance, http://192.168.1.1:8080 or http://myJIRAserver:8080 will work, but http://myJIRAserver.dew:8080 will not.

[Dieter]

You have to use the bsse url in the browser. Jira won't work properly if you don't, please read http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Options . i'm quoting from there:

  You can only configure JIRA to respond to a single URL and this setting must match the URL that your users request for accessing your JIRA site.
 You cannot (for example) have a different hostname or URL for internal and external users.

 This is especially important for JIRA 4.0.x or higher, as any mismatch between this Base URL setting and the URL requested by your JIRA users will cause problems with dashboard gadgets. 

This URL is also used in outgoing email notifications as the prefix for links to JIRA issues.