You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
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 @Bernardo Andreeti's comment.
For now, we've surrendered. We've disabled collaborative editing. It has probably to do with proxy configurations.
Thank you for confirming that! Are you able to pinpoint what time you attempted this so I can go to the location in your logs?
Can you confirm with us if you're running any proxy or firewall?
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.
I've removed the external gadget entries which caused the javax.net.ssl.SSLPeerUnverifiedException, but that has no effect on the problem. Do you have already any insight in what causes the upload problem?
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.
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.