Simply cannot get airbyte-webapp to work 100% behi...
# replication-troubleshooting
j
Simply cannot get airbyte-webapp to work 100% behind NGINX reverse proxy. Has anyone successfully done this with Windows and local deployment in docker with NGINX in wsl on same localhost? airbyte-webapp on localhost:8000 nginx on localhost listening on localhost:200 proxy_pass to http://localhost:8000/; airbyte-webapp successfully receiving the get requests when hitting localhost:200 manifest.json, random static/js/chunks timing out basically instantly on the airbyte-webapp side nginx timeouts are set to 1200 (proxy_connect_timeout, proxy_send_timeout, proxy_read_timeout, fastcgi_send_timeout, fast_cgi_read_timeout, send_timeout DevTools failed to load source map: Could not load content for http://localhost:200/static/css/224.e564b584.chunk.css.map: Load canceled due to load timeout ChunkLoadError: Loading chunk 107 failed. (timeout: http://localhost:200/static/js/107.9e468796.chunk.js) 2022/08/31 122844 [error] 2195#2195: *4870 upstream timed out (110: Connection timed out) while reading upstream, client: localhost, server: localhost, request: "GET /static/css/224.e564b584.chunk.css.map HTTP/1.1", upstream: "http://127.0.0.1:8000/static/css/224.e564b584.chunk.css.map", host: "localhost:200"
j
It was not. Have deployed the same, but locally, same issue.
u
Hi @Jordan Fox, I'm wondering if did you manage to solve the issue? I periodically have the same problem, in particular after adding the MS SQL connector
[error] upstream timed out (110: Operation timed out) while reading response header from upstream
I eventually created a new node pool with more powerful sku, increased the default resource limits for the worker and the Airbyte server and redeployed it, also added all these timeouts for nginx, and now everything is ok:
Copy code
<http://nginx.ingress.kubernetes.io/client-body-timeout|nginx.ingress.kubernetes.io/client-body-timeout>: "7200"
<http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>: "7200"
<http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>: "7200"
<http://nginx.ingress.kubernetes.io/send_timeout|nginx.ingress.kubernetes.io/send_timeout>: "7200"
j
My issue was more around containerization and orchestration of the network. I resolved it as well, just differently.
b
Hello @Jordan Fox can you explain please what you did to fix the error ?