Unable to link crucible to jira cloud

Question

I have only started , I cannot get this working. When I create application link to jira, I get the below error (image 1). Then if i continue anyways and create one manually at both crucible and Jira. image 2 is what i am seeing on crucible end.

on jira end

I am stuck and not sure what to do. Any help is much apreciated. Thanks

Nic Brough -Adaptavist- · Answer

Localhost means "this computer", you can't get to it from a remote computer. You will need to turn your local installation into a server, and put it somewhere that Atlassian Cloud can access it. You can do this with your current machine if you want, "server" just means "computer that runs a service for other computers to talk to" in this answer. To do that, you will need to * Work out what your current external IP address or domain name is * Make sure the outside world can see it on the internet * Route incoming connections to your Fisheye/Crucible server * Run your Fisheye/Crucible on the external IP address or domain name (change the base url) As an example, I run some Atlassian stuff at home. * My home has a router, and the internet knows the IP for it, so when I'm away from home, I can use that IP address to connect to my router. * My router knows to pass all inbound HTTPS traffic to a machine that is running a proxying web server. * My web server proxies my Atlassian from their servers (running on other machines) to relevant URLs, so that I can say: https:///jira https:///confluence and so-on

revathink · Answer

Crucible is running on my computer and the url i am accessing for crucible is localhost.  There is no error on 503 when i try to access cruible alone. The jira is not behind vpn or anything nor is crucible. I thought it might be firewall issue.  I have also added rule to firewall. That did not help either.

Nic Brough -Adaptavist- · Answer

A 503 error means that Jira tried to reach your Fisheye/Crucible, and was successful in the sense that something responded with "I'm here", but it got no further, Fisheye/Crucible did not respond further.

This means that either Fisheye/Crucible has failed (check the service is running) or that it is running on a service that is not set up to be fully accessible to the internet (which is where Jira Cloud is running from)

A very quick test - can you get to Fisheye Crucible on your computer, and see if that 503s.  If it works ok, then try exactly the same url from an address outside your network - go to a coffee shop or internet cafe, or shared workspace and try to log into it (without using any VPNs)