-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hledger-web cannot serve on 0.0.0.0 #2099
Comments
klockeph
added
the
A-BUG
Something wrong, confusing or sub-standard in the software, docs, or user experience.
label
Oct 15, 2023
Maybe also setting --base-url helps ? |
Well yes, but then it would still only work for the particular interface that has the matching IP to the base url. |
Coming to think of it, it probably just needs relative paths in the frontend. I'll try to see if I can create a PR. |
"just" you say. :-) Great, thanks for looking at it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I run
hledger-web --serve --host 0.0.0.0
on my Raspberry Pi to expose web-hledger on all interfaces (in my case WiFi and VPN), some things break:Most notably, opening
192.168.1.<Pi>:5000
redirects to0.0.0.0:5000/journal
.Navigating to the journal directly does not help, since it still tries to load additional resources from
0.0.0.0
- the browser console is flooded withFailed to load resource: net::ERR_CONNECTION_REFUSED 0.0.0.0:5000/<resource>
.The text was updated successfully, but these errors were encountered: