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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What's your JIRA version?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Notice from the KB that errors are not shown on Stash logs if you're hitting that issue but in JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 []
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eras, Please raise an issue with us so we can collect your logs and help you further.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.