Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi there,
I've add my company intranet as a trusted domain when testing the deployment of the Atlassian Companion App. However, when I go to edit an attachment in Confluence, I am still prompted to trust the url. How should I be getting rid of this trust prompt?
Thank you!
Hi @James Fenton ,
Which method are you using to set the trusted domains?
See Administering the Companion app , section "Set trusted domains". Which version of Companion are you using?
Hi @Alex K ,
Thanks for your response. I am using the same method outline in the documentation you sent. I can actually even see the applied url/trusted domain listed as a Windows Environment Variable, but I still get the prompt. I am attempting to deploy version 1.4.1.
Thanks,
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please right click the Companion taskbar icon, and click "View logs", then open the companion.log file? Then do you see a log that begins with:
Initialise whitelist hostname from Environment Variable:
Could you make sure that looks fine? The next step will be to enable debug logs and check that there is no error loading the domain, however this is slightly more complex, we can do it here but it may be preferable to go through support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've found that log and it looks fine to me. If you have step-by-step instructions, I'm fine to follow the next step here. If I need to go through support, that's fine too. Please let me know what works.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@James Fenton Okay, we need to enable debug logging temporarily and then check the logs related to the trusted domains. If you find the Companion install directory, for you because it's the MSI it will be in Program Files (x86). Then within the Resources sub directory, there will be a companionConfig.json file. You need to change logLevel to "debug".
Then restart companion. We are looking for the logs, either:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @James Fenton ,
Companion has been discontinued from a while ( https://confluence.atlassian.com/doc/administering-the-atlassian-companion-app-958456281.html ) so my suggestion is to avoid to use it.
Fabio
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.
you're welcome @James Fenton
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is true for Confluence Cloud only. Companion is still supported on Server/DC, which this question is tagged as.
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.