Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Rest Endpoint giving 404 error

Dishant Sharma
Contributor
January 26, 2023

I created a custom plugin for confluence 7.13.7 and made two other endpoints. In my local Confluence setup, I can access those endpoints and get the desired result successfully. But, when I installed that plugin in my client’s instance, it gave a 404 error. The client is using the data center version of Confluence. What can be the reason for this?

2 answers

1 vote
Vamsi Kandala
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 26, 2023

Hi @Dishant Sharma

The 404 error generally meant for content or url that could not be found.  Did you check whether the API call url is correct and if proper authentication details were given?

If you don't mind, can you list the API call url here?

Did you also try calling the normal REST API call to the client's instance without using your plugin?  Is that working fine?

Thanks,
Vamsi

Dishant Sharma
Contributor
January 26, 2023

@Vamsi Kandala thank you so much for the reply. Yes, I tried with the standard REST API in the confluence server system. 

 

/rest/api/user/memberof?username={username_of_user}

 

This API is working fine and is giving the groups to which a user belongs.

 

My previous custom plugin API endpoint is:

 

rest/userpermissions/1.0/spaceGroup?spaceKey=ds 

 

This endpoint gives all the groups that were applied to a space. This endpoint is working fine on my local Confluence instance. But, is not opening on the client's instance. 

 

I changed the API URL to the following URL:

 

rest/api/1.0/spaceGroup?spaceKey=ds 
0 votes
Michael Rieger (Scandio) February 23, 2023

@Dishant Sharma 

We are facing a similar issue. However, in our case, the custom REST endpoint is found on one node of the cluster, but not on the other.

Unfortunately, we don't have a solution yet either...

Michael Rieger (Scandio) February 23, 2023

Restarting node on which REST endpoints were not available, with cleared plugin caches actually helped in our case.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events