How to use several connectors with Stash?

Hello,

I'm running Stash in a reverse proxy setup behind Nginx and it is working on HTTPS.

Now I'd like to have JIRA connect to Stash through internal network over HTTP.

I assume I have to add a new connector for Stash server.xml file. So this new connector will listen on a different port. However there is a file called scripts.cfg that has set:

stash_httpport=8888

And I'm not sure how to make it know about this new port.

How do I define a new connector so I don't have to connect JIRA and Stash over public internet?

Thank you

3 answers

I am not sure what the setting in scripts.cfg does, but I am fairly sure you should not touch that for this purpose.

As you guessed already, you need to do this in the server.xml, as described here. You can have as many listening ports as you need.

Hi Eras,

I think you're looking for this guide:

This should you help you achieve this outcome.

Let us know how you go!

Best regards,
Thiago Bomfim
Atlassian DevTools Support

Hello Eras! If your AppLinks are working, it could be you're hitting the bug described on https://confluence.atlassian.com/display/STASHKB/Can't+display+issues. Please review this article and let us know how you go.

Hi Thiago, I don't think it is the same bug since I don't see any errors in the stash logs when it says it can't display the issue. Do I need to make the logs more verbose? Btw I'm on Stash 3.8.1

What's your JIRA version?

If your JIRA is on a version prior to 6.2.2, you could be hitting it and I'd advise upgrading your JIRA. If you can't get around that, I'd encourage you to raise a support issue with us: https://support.atlassian.com.

Notice from the KB that errors are not shown on Stash logs if you're hitting that issue but in JIRA.

Jira is 6.4.4. I'm looking into the Jira logs now.

I don't see any errors showing up in Jira logs. All I see is that the https://stash.myserver.com/rest/jira-integration/latest/issues?issueKey=11 is returning an empty list []

Hi Eras, Please raise an issue with us so we can collect your logs and help you further.

Hi Balazs and Thiago,

Thanks for the info. It is working now. Most of the functionality is there, however there is some weird thing between Stash and JIRA link that when clicking on tickets in Stash, it says:

Can't display issues

Either you don't have access to view them or they don't exist. Please contact your system administrator if you believe this is incorrect.

 

---------------

 

What I see is that https://stash.myserver.com/rest/jira-integration/latest/issues?issueKey=11&fields=*all,-comment&minimum=10 returns [] and there are no errors in stash logs. Any ideas what is going on?

 

Thanks again!

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

705 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot