Opening application to network #157
Unanswered
adrian-purnama
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I've successfully built and started OpenWA on Ubuntu. Initially the container was only exposed as
127.0.0.1:2785->2785/tcp, so I made some code changes and was able to expose it to my local network (http://192.x.x.x:2785).However, I'm now running into an issue where OpenWA appears to be validating or redirecting against an HTTPS origin (e.g.
https://192.x.x.x) while I'm accessing it over plain HTTP (http://192.x.x.x). This causes requests to be rejected, and I suspect it may be related to Helmet, CSP, HSTS, origin validation, or another security middleware.What is the recommended way to expose OpenWA to other devices on a local network? Is there a supported configuration for binding to
0.0.0.0and allowing HTTP access on private networks, or should it always be deployed behind a reverse proxy with HTTPS?Also, would it be possible to provide OpenWA as a fully self-contained Docker image so deployment can be as simple as:
This would greatly simplify server deployments by removing the need to clone the repository, build locally, or run from a specific directory. Is there an official image available, or are there plans to support this deployment model?
Beta Was this translation helpful? Give feedback.
All reactions