Error 404 on any API published in 4.0.0-rc

Description:

Any API deployed and published on 4.0.0-rc will return 404 when invoked through API gateway. Gateway returns error: {"code":"404","type":"Status report","message":"Not Found","description":"The requested resource is not available."} Log shows: INFO - LogMediator STATUS = Message dispatched to the main sequence. Invalid URL., RESOURCE = /testapi/1.0/test, HEALTH CHECK URL = /testapi/1.0/test

Steps to reproduce:

Download and extract API Manager 4.0.0-rc. Configure for MySQL database, add MySQL JDBC driver. Configure hostname, proxy ports for nginx as proxy server, and endpoint URLs in [[apim.gateway.environment]]. Start api-manager.sh.

Create new API of any kind, either new API or import OAPI definition file.

There will be no errors in logs or in API Publisher, API will be published without errors, but invoking, either via Publisher, Devportal or curl will produce 404 error as if API does not exist.

Affected Product Version:

4.0.0-rc

Environment details (with versions):

OS: Linux Debian 10
Env (Docker/K8s): Virtual machine

Suggested Labels:

4.0.0, Type/Bug

Issue Analytics

State:
Created 2 years ago
Comments:10

Top GitHub Comments

1reaction

marmo94commented, Oct 28, 2022

Help ! I’m facing same issue on 4.1.0. each time I publish a new API and then call it, I get 404 and when I restart the server it works then (so any time I need to add an API, I first add it and restart the server to get it ok). in the UI we get the error :

Failed to fetch.Possible Reasons:CORSNetwork FailureURL scheme must be “http” or “https” for CORS request.

</body> </html> and on the server side we can see :

{“code”:“404”,“type”:“Status report”,“message”:“Not Found”,“description”:“The requested resource is not available.”}

1reaction

danijeltcommented, Mar 25, 2022

I’m closing this issue since I’ve found the solution for my case.

Top Results From Across the Web

All requests to ASP.NET Web API return 404 error

The application pool is running with .NET 4.0 in integrated pipeline mode. In this production environment the MVC web site works, Web API...

Error 404: 4 Ways to Fix It - Hostinger

Error 404 is a response code, meaning the server could not locate the requested content. Check this article to learn 4 steps to...

API Connect V2018.x: 404 errors after publishing changes to a ...

Problem. It has been observed under certain circumstances that updating an already published catalog can result in an inability to access any resources...

elm-live - npm

A flexible dev server for Elm. Live reload included!. Latest version: 4.0.2, last published: 3 years ago. Start using elm-live in your project...

Solved: NSX API: 404 errors - possible bug, or documentati...

Sets the portal layout. Example 8-156. Apply layout configuration. Request: PUT https://<vsm-ip>/api/4.0/edges/<edgeId>/ ...