Forum Discussion
Anonymous
6 years agoNot applicable
All Gateway-related API calls failing with 404 error
I recently moved my On-premises Gateway to a new machine. After that, all API calls I made which related to Gateways started failing. It doesn't matter which one I do (/gateways, GetBoundGatewayDataSources, BindToGateway, etc), it always returns this error: The remote server returned an error: (404) Not Found.
The same code worked fine the day before on the old machine. And I can still perform all of the other API calls that I use (/refreshes, /takeover, /datasets, etc). It's just anything having to do with a Gateway that fails now.
I transferred the Gateway using the recovery key and refreshes are working successfully. I just don't know why these API calls are failing.
Any ideas what could cause this?
No Replies