mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-07-16 05:33:49 +03:00
WEB经TCP/IP端口映射后,手机安卓端加载界面异常 #5389
Closed
opened 2026-02-05 10:01:46 +03:00 by OVERLORD
·
7 comments
No Branch/Tag Specified
development
l10n_development
release
snyk-action
ci_and_static
mfa_key
phpstan_june26
MilnerMart/development
GamerClassN7/impersonations-for-admin
Zhey-on/feature/csp-image-css-controls-6033
tortillas5/development
llm_only
vectors
McTom234/oidc-key-algorithms
captcha_example
v26.05.2
v26.05.1
v26.05
v26.03.5
v26.03.4
v26.03.3
v26.03.2
v26.03.1
v26.03
v25.12.9
v25.12.8
v25.12.7
v25.12.6
v25.12.5
v25.12.4
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#5389
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 @Sambaaaaaaa on GitHub (Aug 4, 2025).
Describe the Bug
WEB经TCP/IP端口映射后,手机安卓端加载界面异常
Steps to Reproduce
bookstack server ip:10.21.108.254 port:8080
netsh interface portproxy add v4tov4 listenport=8080 connectaddress=10.21.108.254 connectport=8080
Expected Behaviour
请看一下这个什么原因导致,如何解决?
Screenshots or Additional Context
Browser Details
No response
Exact BookStack Version
25.07
@Sambaaaaaaa commented on GitHub (Aug 4, 2025):
TCP/IP端口映射后的web,PC端打开是正常的,但是安卓端加载打开就异常了。
@ssddanbrown commented on GitHub (Aug 4, 2025):
Hi @Sambaaaaaaa,
When accessing via Android, are you also accessing using the same port number and protocol (
http:///https://part)?What is your
APP_URLenv option set to?@Sambaaaaaaa commented on GitHub (Aug 5, 2025):
@ssddanbrown 你好, 感谢你的回信!
一、/home/bookstack_data/www/.env Config:
APP_KEY=base64:3POTE674n/W9vSrwhzXf0A4Z5Xtw5FHRPWhtbKzJaxk=
APP_URL=http://10.21.108.254:8080/
APP_UPLOAD_LIMIT=4096
FILE_UPLOAD_SIZE_LIMIT=4096
DB_HOST=bookstack_db
DB_DATABASE=bookstack
DB_USERNAME=bookstackuser
DB_PASSWORD=bookstackpass
二、docker-compose Config:
Details
三、我使用了多台设备,以及尝试其他TCP/IP端口映射,测试结果都是一,以下是我截图
访问相同的协议地址:http://10.21.98.62:8080
3.1 安卓设备1 (MI 15,B ver:Chrome 131.0.6778.260,Android:15)
3.2 安卓设备2 (Samsung Note10,B ver:Chrome 138.0.7204.63,Android:12)
@ssddanbrown commented on GitHub (Aug 5, 2025):
Hi @Sambaaaaaaa,
I noticed you have
APP_URL: http://10.21.108.254:8080set (in both the compose config and the .env file) while you are accessing viahttp://10.21.98.62:8080. This mismatch would cause the issues you're seeing.Can you update any
APP_URLreferences to match the URL you're using the access via the mobile browser? (Sohttp://10.21.98.62:8080).Remember to re-up the container, as just restarting may not take into account any env option changes.
@Sambaaaaaaa commented on GitHub (Aug 6, 2025):
@ssddanbrown 你好,感谢您的指引,我成功解决了问题!我更新了 APP_URL 并且 重新删除再创建容器后,确实可以正常的显示了。
@Sambaaaaaaa commented on GitHub (Aug 6, 2025):
最后再问两个问题;①疑惑的是为什么 Windows PC端不会受此影响,不需要更正 APP_URL, 也可以正常浏览访问。②该项目以后是否会考虑推出移动手机客户端,希望以安装客户端的方式,实现与Windows PC端一样,不受 APP_URL 影响,也可以正常浏览访问。
@ssddanbrown commented on GitHub (Aug 6, 2025):
Good to hear that helped resolve things!
I'm not sure why the PC version was working. It could depend on which actual settings were in use at the time, and which URL was used. Hard to be sure.
I am not looking to develop a native application any time soon, it would be a lot of extra effort for limited benefit compared to just ensuring the web interface works well on mobile devices.
Since this was resolved, I'll therefore go ahead and close off this issue.