<@U04S8PLJWMT> After upgrading to <1.3.to> we are ...
# ask-ai
k
@kapa.ai After upgrading to 1.3.to we are seeing error /usr/share/nginx/html/api/v1/instance_configuration" failed (2: No such file or directory)
k
The error
/usr/share/nginx/html/api/v1/instance_configuration" failed (2: No such file or directory)
after upgrading to Airbyte 1.3.x is a known issue reported by several users. This error typically appears as a 404 Not Found when the frontend tries to access backend API endpoints like
/api/v1/instance_configuration
or
/api/v1/health
. The root cause is usually related to configuration changes between Airbyte versions, especially around Nginx and API routing. Key points from the knowledge sources: - The error occurs because Nginx is trying to serve API requests as static files, which means the requests are not being properly routed to the backend API service after the upgrade. This is often due to outdated or incompatible configuration files (such as
values.yaml
or Nginx config) being used during the upgrade process. - One contributor specifically mentioned that using a minimal, up-to-date
values.yaml
file (instead of copying an old, full version) resolved the issue, as older files may contain deprecated or incompatible settings, especially around security context and routing. It is recommended to start with a minimal config and only add necessary customizations for your deployment. Outdated ingress or Nginx settings can break API routing after an upgrade [Error upgrading Airbyte helm chart from 0.63.11 to 1.3.0](https://github.com/airbytehq/airbyte/issues/49843). - The Nginx error log you provided matches exactly with the known issue:
Copy code
open() "/usr/share/nginx/html/api/v1/instance_configuration" failed (2: No such file or directory)
This confirms that the API requests are being routed to the static file server instead of the backend API service [Error upgrading Airbyte helm chart from 0.63.11 to 1.3.0](https://github.com/airbytehq/airbyte/issues/49843). Recommended actions: 1. Review your
values.yaml
and Nginx configuration. Start with a minimal, up-to-date
values.yaml
as recommended in the upgrade documentation or by the Airbyte team. 2. Check your ingress and service routing settings to ensure API requests are correctly forwarded to the backend, not the static file server. 3. Avoid reusing old configuration files from previous major versions without reviewing changes in the new version. If you continue to experience issues, consider sharing your custom configuration and upgrade steps with the Airbyte community for more targeted troubleshooting. For more details and user experiences, see the related discussion: [Error upgrading Airbyte helm chart from 0.63.11 to 1.3.0](https://github.com/airbytehq/airbyte/issues/49843).