We’re doing a proof of concept with the Balsamiq plugin in our Confluence Server install and we’re having a few issues.
We run AWS EC2 instance servers, and we’ve configured the Confluence instance behind an AWS LB reverse proxy, as well as using a context path.
This means we use a generic url ( ex: atlassian.mycorp.com ) with a context for each atlassian app (ex: https://atlassian.mycorp.com/confluence and https://atlassian.mycorp.com/jira ). We believe this context value is causing the balsamiq plugin to not work as the FQDN we provide does not, and can not, handle the context required on the URL.
Is there a way to fix this, or is it supported ?