Confluence Data Center 9.2.5 – ZDU REST API endpoints returning 404

[Asmaa Elsayed]

Context:

• Running Confluence Data Center v9.2.5, which officially supports the Zero Downtime Upgrade (ZDU) REST API community.atlassian.com+15confluence.atlassian.com+15community.atlassian.com+15.

• Remote API (XML-RPC & SOAP) is enabled in the Further Configuration settings.

• All REST calls (including GET /rest/api, GET /rest/zdu/cluster/zdu, and /rest/zdu/cluster/zdu/state) return 404 Not Found.

• No known context path (e.g. /confluence) is confirmed; both with and without prefix return errors.

What I’ve tried:

• Curling https://<host>/rest/api

• Curling https://<host>/confluence/rest/api

• Curling GET and POST to /rest/zdu/cluster/zdu, /state, /start, etc.

• Verified Data Center license and admin permissions

Issue:
Unable to access any ZDU endpoints, despite official documentation stating they should be available in this release community.atlassian.com+3confluence.atlassian.com+3community.atlassian.com+3developer.atlassian.com+1confluence.atlassian.com+1.

Questions:

1. Are there known configuration issues or feature flags in v9.2.5 that disable ZDU REST APIs?

2. Could custom context path or reverse‑proxy routing omit the /rest/zdu/cluster/zdu endpoints?

3. How can I verify if the ZDU endpoint plugin/module is enabled on my Confluence cluster?

4. Any community experience diagnosing missing REST endpoints in Confluence Data Center?

[Brant Schroeder]

@Asmaa Elsayed are you able to access any of the web services?  Can you connect to any Confluence API?  Just want to make sure that it is not a firewall rule.

[Aron Gombas _Midori_]

@Asmaa Elsayed  Exactly my idea. Why don't you test the most trivial end-point first? There is a "server info" one which may not even require authentication...

With that you could learn if all end-points are failing, or only ZDU. That's important for your troubleshooting.

[Asmaa Elsayed]

I tested this one and it returned a response /rest/api/content. but for zdu it's always 404. If you have a url for the valid apis it'll be good.

[Chand Chandrasegaram]

These old REST end points will work on Confluence 9.2.x 

{code}
Approve upgrade -> POST /rest/zdu/approve
Cancel upgrade -> POST /rest/zdu/cancel
Get cluster -> GET /rest/zdu/cluster
Get node by id -> GET /rest/zdu/nodes/{nodeId}
Start upgrade -> POST /rest/zdu/start
Get state -> GET /rest/zdu/state
{code}

Tested on Confluence data centre version 9.2.9 

Here is the documentation : docs.atlassian.com/ConfluenceServer/rest/7.9.0/#zdu-startUpgrade 

[Marc -Devoteam-]

Hi @Asmaa Elsayed 

Do you have a cluster setup, I mean do you have multiple Confluence servers running or do you only run a single instance?

[Asmaa Elsayed]

Yes, I have cluster setup

[Marc -Devoteam-]

Hi @Asmaa Elsayed 

If you are running with a proxy NGINX, APache etc..

In the documentaiton you need to disconnect, this or make a change in the config.

ZDU needs to be reached via <host>:<port>