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; } } }

Installation on standalone network

Thomas Steck

Some pages are extremely slow loading, like the RapidBoard of GreenHopper, when installed on a standalone network that is unable to access atlassian.com. jira.atlassian.com access is attempted while trying to load the page, and this must time out before the page will load. Using Firefox 10.

The question is whether built-in pages can be made so they don't try to go to Atlassian.com, or other external networks? That way, users don't have to wait for a timeout, since they will never get to those sites.

NOTE: Didn't realize first post succeeded. Sorry. This is the title on same topic.

Installation on isolated network problems

Accepted answers

Pascal Schneide

Here is a workaround to avoid the slow loading:

* Setup a webserver under a virtual host for 'jira.atlassian.com'.

* Redirect all requests to this domain to a single PHP file. This PHP File should only send the status code header 500 and die.

* Edit the /etc/hosts file on your JIRA server and add 'jira.atlassian.com' with the IP address of the webserver

Now your JIRA should get a fast but very negative response and doesn't have to wait for a timeout.

(Not tested by myself)

All comments

Nic Brough -Adaptavist-

I'm not sure what the question is here. Sounds like your "standalone network" has some issues, but there's no detail to work with.

Norman Abramovitz

SInce you are on an isolated network, you can remove the gadgets on the dashboard that attempt to access the outside world. Also since you are on a private/isolated network you should be able to change your private/isolated DNS(maybe it is just your hosts file) and map the those domains to a localhost page to avoid the timeout as well.

Norman Abramovitz

Also check your greenhopper options that did not enable items that would attempt to access the outside world.

Pascal Schneide

Here is a workaround to avoid the slow loading:

* Setup a webserver under a virtual host for 'jira.atlassian.com'.

* Redirect all requests to this domain to a single PHP file. This PHP File should only send the status code header 500 and die.

* Edit the /etc/hosts file on your JIRA server and add 'jira.atlassian.com' with the IP address of the webserver

Now your JIRA should get a fast but very negative response and doesn't have to wait for a timeout.

(Not tested by myself)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira