nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Companion App issues with Confluence Server 7.5.1

Rosalind BANWELL

Hi all,

I've read about issues up to 7.2, but has anyone had issues with the 7.5.1 version? We are currently testing on our development server. it took several goes for me to get the Companion App working and other testers have not had success at all.

In my case I can edit files however I still get the message "If nothing happens, download the Atlassian Companion app and try again.".

For other users it is not opening the associated apps at all, but most users seem to have managed to install the app...

Is there a step I'm missing somewhere?

Thanks for your help!

Rosalind

Accepted answers

Alex K

Hi @Rosalind BANWELL ,

Is your development server using a self-signed certificate? Companion can fail silently in this case.

The message you are seeing in Confluence indicates that Companion is not able to communicate back with Confluence to notify it that the file has been launched. You said that you were eventually able to get it to work, are you able to upload the file back to Confluence?

All comments

Alex K

Hi @Rosalind BANWELL ,

Is your development server using a self-signed certificate? Companion can fail silently in this case.

Rosalind BANWELL

Hi Alex,

Thanks for replying. After reading the other articles I was wondering if it could be linked to certificates... not even self-signed at the moment, as far as I can tell!

Yes, it works fine for me after a few goes... and I don't know why that is! Perhaps as I already have the Companion App running...

I just don't feel confident about upgrading the server if others are going to run into issues, but if it's the certificate, then we should have not issues with the production version.

Alex K

Hi @Rosalind BANWELL ,

Editing on Confluence with Companion should work even if Companion is not already running. May I check, which version of Companion are you using? Also, which installer did you use (MSI, EXE, DMG)?

If you are worried about the production upgrade, I would suggest raising a support request and include the Companion log file (right click Companion tray icon -> View Logs) from when the edit fails. We should be able to troubleshoot further with the extra logging.