I'm using Confluence 6.2.2 and when I'm trying to attach a file to a page, either in edit mode or drag and drop the attachment on the page, I will get a session expired message (See pictures below).
When I close the upload window, I don't have to login again.
Note that the time that I've been logged in does not matter.
What do I need to change to fix this?
To assist, can you please tail your Confluence logs, replicate the error, and send us the lines that occur when you do this?
Please also confirm your database type and version and confirm if the Server Base URL matches the URL that you use to access Confluence.
Thank you for your quick response. I tried to do some things this morning (2017-08-23) between 07.30 and 9.00.
Yes, we use a proxy with SSL certificate and we used the settings at page https://confluence.atlassian.com/doc/using-apache-with-mod_proxy-173669.html
Thank you! We have a team looking into issues with Collaborative Editing so I've added the appropriate tag to this issue so they can step in and assist us.
One thing I did notice was this:
javax.net.ssl.SSLPeerUnverifiedException: Host name 'pww.jira.philips.com' does not match the certificate subject provided by the peer (CN=www.jira.intra.lighting.com, OU=Lighting, O=Philips Lighting B.V., L=Eindhoven, ST=Noord-Brabant, C=NL)
It could prevent things from not working properly so you may want to look into that. In the meantime, we will continue to investigate via your logs.
Thanks Rudy! I was just letting you know about that since when certs don't match the URL it does cause other problems so I wanted to make sure you were aware of that.
We've properly tagged the issue now so the team handling the Synchrony issues will be able to have a look at this.
This problem is usually caused by a bug in Synchrony, which we can check below:
I personally recommend the third workaround of renaming the session cookie and restarting Confluence to fix this issue.
I ran into a similar problem, however; my issue was caused by an external proxy that didn't support session persistence (due to a config problem).
This was an F5 LTM. On the LTM I had to configure the virtualserver's "Default Persistence Profile" to "cookie" which causes the F5 to insert its own cookie into the HTTP header that tracks which node was in use for that session.
Mea culpa, didn't heed the warning in Atlassian's documentation which states, "Use a load balancer with session affinity and..."
Adding here for any others that encountered the same mistake, but aren't affected by the bug referenced in @Andreeti's comment.
Hindsight might be 2020 but looking back, a lot of cool new features rolled out in 2019. From new collaboration and organizational powers to fresh templates and handy integrations, it’s been quite th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events