Fix network API calls failing when Docker deployment is accessed remotely#324
Merged
Edwardvaneechoud merged 3 commits intomainfrom Feb 9, 2026
Merged
Conversation
…tely The frontend axios client was hardcoded to http://localhost:63578, which fails when accessing the Docker deployment from another machine on the network since the browser resolves localhost to the user's own machine. - Make flowfileCorebaseURL runtime-dynamic: use direct localhost URL in Electron mode, relative /api/ path in web/Docker mode - Add nginx.conf with reverse proxy rules that forward /api/* requests to flowfile-core:63578, including SSE support for log streaming - Update Dockerfile to use the external nginx.conf instead of inline config - Fix LogViewer.vue EventSource URL construction to handle relative paths - Add vite dev server proxy so npm run dev:web also works with /api/ paths https://claude.ai/code/session_01HtZJr4MnVSYw8MGuqgKiTq
navigator.clipboard is only available in secure contexts (HTTPS or
localhost). When accessing the Docker deployment over plain HTTP from
another machine on the network, navigator.clipboard is undefined.
Add a fallback using the legacy document.execCommand('copy') approach
for insecure contexts so the copy-to-clipboard buttons in SetupView
work regardless of the protocol.
https://claude.ai/code/session_01HtZJr4MnVSYw8MGuqgKiTq
…irects FastAPI issues 307 redirects to add trailing slashes (e.g. /editor/create_flow → /editor/create_flow/). When proxy_set_header Host $host was used, the redirect Location header used the external hostname without port (http://192.168.50.176/editor/create_flow/), bypassing both the /api/ prefix and the correct port (8080). Fix by removing the Host override so nginx uses the default $proxy_host (flowfile-core:63578). Now the backend's redirect points to the internal host, and nginx's built-in proxy_redirect default correctly rewrites it to http://<external-host>:8080/api/editor/create_flow/. Also remove premature WebSocket headers (Connection: "upgrade" was being sent on all requests) and add X-Forwarded-Host so the backend can access the original host if needed. https://claude.ai/code/session_01HtZJr4MnVSYw8MGuqgKiTq
✅ Deploy Preview for flowfile-wasm canceled.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The frontend axios client was hardcoded to http://localhost:63578, which
fails when accessing the Docker deployment from another machine on the
network since the browser resolves localhost to the user's own machine.
Electron mode, relative /api/ path in web/Docker mode
to flowfile-core:63578, including SSE support for log streaming
https://claude.ai/code/session_01HtZJr4MnVSYw8MGuqgKiTq