You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When directly accessing from IP, it will show "Invalid Host header."
However, my machine is in a Tailscale network and comfiguring hosts of every machine is much too difficult and unrealistic. I understand currently API needs subdomain api.example.com but as a self-hostable service accessing through IP is still needed as setting up local DNS or domains in a local network is needless in most cases I think.
I 've noticed there's already #230 which includes this suggestion, and I really hope accessing via IP feature would be available soon.
The text was updated successfully, but these errors were encountered:
The issue you linked mentions the experimental_no_subdomain config property. I think if you set this to true, and also set domain to the IP address, it will let you access "via IP". Let me know how this goes. I agree we definitely need to make this simper, but it seems very difficult to do that without compromising security.
but it seems very difficult to do that without compromising security.
Well, I don't see how is this related to security at all. First of all, worst that can happen, you can have conflicts with other hostnames served under your IP, but that is clearly your own fault as a hoster. If you want security, you should enable and configure it manually. And, for example, all containers that I tried before - like they all don't care what host header you using for them.
When directly accessing from IP, it will show "Invalid Host header."
However, my machine is in a Tailscale network and comfiguring hosts of every machine is much too difficult and unrealistic. I understand currently API needs subdomain
api.example.com
but as a self-hostable service accessing through IP is still needed as setting up local DNS or domains in a local network is needless in most cases I think.I 've noticed there's already #230 which includes this suggestion, and I really hope accessing via IP feature would be available soon.
The text was updated successfully, but these errors were encountered: