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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I get the error message
We can't check the status of your index, you may have lost your connection, refresh the page to try again
I see the hint on page Content Index Administration | Confluence Data Center and Server 7.17 | Atlassian Documentation
If the content indexing page does not load properly, and you see a "We can't check the status of your index, you may have lost your connection, refresh the page to try again" error, try updating your browser to the latest version.
Im testing with edge
What newer, other browser is needed?
I finally made it with the rest api
/rest/questions/1.0/admin/edges/reindex
Popular content missing after reindexing from scratch | Confluence | Atlassian Documentation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anton Maag ,
Welcome to Atlassian community.
We have seen such errors in the past and you might want to check on the below KB article which has some solution for you.
I hope the above info helps. Have a good day.
Thanks,
Srinath T
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
I tried it out, but it did not resolve my issue.
Do you have any other idea?
Thanks
Anton
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my case, indexing is in progress. I can see that from atlassian-confluence-index.log. But UI does not reflect the same. It says "Rebuild index" even while indexing is at 70% as per index log.
And when I inspect the requests, I found the following request returns 404:
/rest/rebuildindex/latest/job
Our server does run behind a reverse proxy, but as I see the 404 error is actually coming from the application itself. Any ideas why?
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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.