mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-06 09:09:38 +03:00
Internal LAN Works, Tailscale Broken #3452
Closed
opened 2026-02-05 06:45:22 +03:00 by OVERLORD
·
5 comments
No Branch/Tag Specified
development
further_theme_development
l10n_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
No Label
🐕 Support
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#3452
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Insan0 on GitHub (Jan 15, 2023).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
I am able to access Bookstack locally by going to 172.16.0.100:6000. The APP_URL is
http://172.16.0.100I'm on CGNAT, and so I'm using Tailscale to access my network when away from home.
However, when I'm remote and try to access Bookstack through the Tailscale domain (machine.tailunique.ts.net:6000) or the Tailscale IP (10.xxx.xxx.xxx:6000) it doesn't work. When trying on my iPhone, the address bar switches to show 172.16.0.100, and eventually says the server stopped responding.
Access to my other apps works fine using Tailscale this way (e.g. plex, photoprism, etc.). I tried Wiki.js, and that works also with this method, but I really much prefer the structure, intuitiveness of Bookstack.
I suspect this is related to open issue 1342, but not sure.
Exact BookStack Version
v22.11.1
Log Content
No response
PHP Version
No response
Hosting Environment
Synology NAS through docker.
@ssddanbrown commented on GitHub (Jan 15, 2023):
Hi @Insan0,
BookStack only supports being hosted on one hostname/IP at a time. Since you mention:
It sounds like the request is resolving but BookStack, with the APP_URL set to
http://172.16.0.100/, will redirect to that local IP.I'd advise standardizing on a single domain/scheme for usage, so the tailscale domain I'd guess in this case since that should be accessible for everything?
@Insan0 commented on GitHub (Jan 15, 2023):
Hi @ssddanbrown ,
Thanks for the quick reply. Yes, i suppose I'll need an internal DNS server to route the tailscale domain when used internally to the correct IP? The tailscale domain is only available if the device is on the tailscale tunnel. Local devices (e.g. desktops) wouldn't need to be on the tailscale tunnel. Am I understanding this right? Thanks again.
@ssddanbrown commented on GitHub (Jan 15, 2023):
Ah, Yeah, Sorry, I'm not too familiar with tailscale, have only quickly used it once before.
I had it in mind they provide some way to expose a public domain/IP though, might be an add-on service of sorts?
@Insan0 commented on GitHub (Jan 15, 2023):
Great thanks, I'll look into it. Am I right that this is the same as issue 1342? If so, I'll keep my eye on that to see if things might change on Bookstack end, and you can close this one.
By the way, I was so happy and excited to use Bookstack, I created a Github account just for this. Great work!
@ssddanbrown commented on GitHub (Jan 15, 2023):
Thanks!
If your intention is to use the system on multiple IPs/hosts, yes. To be honest though, I don't see the status of that issue changing anytime soon. The current system is based upon decisions I made early on and have since reinforced usage of. It would be a painful process to make changes to that and one I don't see being relatively worthwhile right now.