It's hard to say for sure if this is a bug vs configuration. I suspect that it's configuration, but let's check it first. In Jira Server go to Settings -> Applications -> Under Integration on the left side navigation there is a link for Application Links. Edit the application link so you can see what values are stored there. What do you see here for application URL and display URL?
I'm betting that your site has an application URL of your internal hostname on port 8090. This setup is common because it tends to bypass HTTP proxies that might be in place, AND bypass any SSL that might be the limiting factor here. One possible solution here would be to use the FQDN for the application URL such as a confluence.example.com here.
But to make this work and over SSL, the Jira application has to actually be able to open a connection to that server on that address. There a few different things that can prevent that, such as if your network requires that outbound HTTP(S) requests have to be passed through an outbound proxy, then Jira tends to need these settings in the JVM startup options. More details in How to Configure an Outbound HTTP and HTTPS Proxy for JIRA applications.
If you're using HTTPS/SSL for these applications, it gets even more hairy, because in order for an application like Jira to make an outbound HTTPS request to another application like Confluence, it has to have the certificate of that application already in the truststore. Take a look at How to import a public SSL certificate into a JVM for more details.
These are the two major hurdles that we commonly see with setting up application links. You might have to try to configure the applications links to use the complete URLs in both applications though and then look at the application logs in order to better understand what the limitation is for your environment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.