You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Need your help to resolve issue i am facing while creating application link from cloud JIRA to on-prem Confluence.
for my confluence instance have 2 url one is to access from internal network and other is to access from external world.
ERROR -
Invalid OAuth signature
We couldn't connect to HI Confluence, possibly because that instance is behind a misconfigured proxy.
could someone provide me any guidance as how to resolve this issue.
My initial guess is that this is the problem:
>for my confluence instance have 2 url
I suspect you've got your proxy config mostly correct for the external site, but then it's going wrong because your Confluence base url is set to the internal one. You will need your Confluence, Oauth, the proxy and the rest all to be set to run on the external url. (And then you might as well forget the internal one, apart from a placeholder page that redirects old bookmarks to the actual Confluence site)
Hi Nic,
Thanks for the response, YES my base url is set to internal URL, I tried changing base url to external url it works however it breaks the other application link to my ON-Prem JIRA,STASH etc..
Looking for option if i can keep Both url so it won't break anything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Confluence can only run on a single URL.
You will need to choose one and use it consistently.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does this also apply to ON-prem JIRA DC?
We have an issue from Jira Cloud to Jira on-prem.
We've got this set up to run on external URL: stage-services.sunlife.com instead of the base: stage-jira.ca.sunlife
Creating a link for from Cloud Jira does not even send any traffic to stage-services.sunlife.com
Is this an issue on the Jira Cloud side?
Thanks.
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.