REST service always returns 404 resource not found on cloud node

As the title says, a rest service I’ve deployed to a cloud environment always returns a 404 status with “resource not found”. It works fine locally, and the rest path is allow all in the network config, but even using the generated swagger function I always get the 404 error. I never get to the actual resource. It doesn’t matter whether I am logged in or not.   Any ideas?
1 answers

You can use this documentation page to see reasons why you might get a 404 error. Like Robert mentions in his comment, setting REST Publish lognode to trace will give you additional information.