OpenWebUI/docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs synced 2025-06-10 00:27:43 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add linked headers

Browse Source
This commit is contained in:
Justin Hayes 2024-02-25 22:52:45 -05:00 committed by GitHub
parent 336345f09d
commit b04079be0c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/faq.md
View File

@ -5,16 +5,16 @@ title: "📋 FAQ"
# 📋 Frequently Asked Questions
**Q: Why am I asked to sign up? Where are my data being sent to?**
#### **Q: Why am I asked to sign up? Where are my data being sent to?**
**A:** We require you to sign up to become the admin user for enhanced security. This ensures that if the Open WebUI is ever exposed to external access, your data remains secure. It's important to note that everything is kept local. We do not collect your data. When you sign up, all information stays within your server and never leaves your device. Your privacy and security are our top priorities, ensuring that your data remains under your control at all times.
**Q: Why can't my Docker container connect to services on the host using `localhost`?**
#### **Q: Why can't my Docker container connect to services on the host using `localhost`?**
**A:** Inside a Docker container, `localhost` refers to the container itself, not the host machine. This distinction is crucial for networking. To establish a connection from your container to services running on the host, you should use the DNS name `host.docker.internal` instead of `localhost`. This DNS name is specially recognized by Docker to facilitate such connections, effectively treating the host as a reachable entity from within the container, thus bypassing the usual `localhost` scope limitation.
**Q: How do I make my host's services accessible to Docker containers?**
#### **Q: How do I make my host's services accessible to Docker containers?**
**A:** To make services running on the host accessible to Docker containers, configure these services to listen on all network interfaces, using the IP address `0.0.0.0`, instead of `127.0.0.1` which is limited to localhost only. This configuration allows the services to accept connections from any IP address, including Docker containers. It's important to be aware of the security implications of this setup, especially when operating in environments with potential external access. Implementing appropriate security measures, such as firewalls and authentication, can help mitigate risks.
**A:** To make services running on the host accessible to Docker containers, configure these services to listen on all network interfaces, using the IP address `0.0.0.0`, instead of `127.0.0.1` which is limited to `localhost` only. This configuration allows the services to accept connections from any IP address, including Docker containers. It's important to be aware of the security implications of this setup, especially when operating in environments with potential external access. Implementing appropriate security measures, such as firewalls and authentication, can help mitigate risks.
If you have any further questions or concerns, please don't hesitate to reach out! 🛡️