mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 03:09:39 +03:00
Visitors origin IP not shown in audit log - dockerized installation #3905
Closed
opened 2026-02-05 07:49:28 +03:00 by OVERLORD
·
6 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#3905
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 @towerplease on GitHub (Jul 6, 2023).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
I use a dockerized installation, which i migrated 2 months ago from a classic installation.
Earlier, i used a nginx proxy to access bookstack and i have added header-forward-rules to nginx proxy, so the origin ip is shown in audit log.
After migration, i only see the docker-network gateway in audit log. I guess i need to confige something similar in docker-network to get real origin ip-address?
Exact BookStack Version
23.06.1
Log Content
PHP Version
docker -> No idea which php-Version this uses
Hosting Environment
VPS with ubuntu 22.04 and docker-compose (portainer).
Docker-compose.yml:
version: "2"
services:
bookstack:
image: lscr.io/linuxserver/bookstack
container_name: bookstack
environment:
# Konfiguration über .env File in app_data/www/.env
- PUID=1000
- PGID=1000
- APP_URL=https://doku.madgeeks.de
- DB_HOST=bookstack_db
- DB_PORT=3306
- DB_USER=bookstack
- DB_PASS=AAAAAAAAAAA
- DB_DATABASE=bookstackapp
volumes:
- /mnt/docker/volume/bookstack/app_data:/config
ports:
- 6875:80
restart: unless-stopped
depends_on:
- bookstack_db
labels:
- "com.centurylinklabs.watchtower.enable=true"
bookstack_db:
image: lscr.io/linuxserver/mariadb
container_name: bookstack_db
environment:
- PUID=1000
- PGID=1000
- MYSQL_ROOT_PASSWORD=AAAAAAAAAAA
- TZ=Europe/Berlin
- MYSQL_DATABASE=bookstackapp
- MYSQL_USER=bookstack
- MYSQL_PASSWORD=AAAAAAAAAAA
volumes:
- /mnt/docker/volume/bookstack/db_data:/config
restart: unless-stopped
labels:
- "com.centurylinklabs.watchtower.enable=true"
@ssddanbrown commented on GitHub (Jul 6, 2023):
Hi @towerplease, Couple of questions:
Additionally, If using, I'd advise against using watchtower to auto-update the bookstack or bookstack database containers.
If possible (I'm not familiar with watchtower) have it just alter you so you can run the upgrade yourself.
@towerplease commented on GitHub (Jul 6, 2023):
Hi @ssddanbrown
thanks for the fast reply.
Yeah, i use Cloudflare via cloudflared (also dockerized) in cloudflare-tunnels. Its configured via Cloudflare Access. But i think i have no issue there, because cloudflared is routing without masquerading the origin IP. No other proxies are currently in between (except default docker-routing from my home-network to the docker-IP -> 192.168.178.0/24<->172.26.0.0/16)
As written, i think i need to "configure" the docker-network to not masquerade the origin IP, if this is even possible(?).
Sure, i know the risk of auto-updating. But i have multiple backups:
But thanks for the advice, regarding auto-updates.
@ssddanbrown commented on GitHub (Jul 6, 2023):
@towerplease Ah, Okay, fair enough if you have solid backups. I just get nervous as I've see a pattern of issues due to interrupted updates.
For the IP, It's hard to see where exactly things might be getting dropped, but I'll point to a couple of elements that may help:
APP_PROXIESoption as can be seen here, which when configured can allow BookStack to take the IP from the"X-Forwarded-For"header, providing an alternative path of IP travel (Would have to check if the other parts in play provide, or can provide, this).nginxpath of the mounted container/configvolume. If you can find a header with the right IP you could use nginxrealiplike shown in this stack overflow page.This linuxserver thread may also provide some extra clues.
Otherwise, I'm not too familiar with how docker networks themselves may interact with the incoming IP. I wouldn't have expected that to be an issue but could totally depend on the type of networking at play.
@towerplease commented on GitHub (Jul 6, 2023):
@ssddanbrown
It's alright, also this environment is private, just for me, so non-productive :) Otherwise, i am 100% with you, should never have prod-applications on auto-update.
I see, i have some configurable option within the mounted volume (nginx).
I will try some configuration the next days and reply when i found a solution :)
Thank you very much for providing support and the possible configs.
@towerplease commented on GitHub (Jul 11, 2023):
Hey @ssddanbrown
i just want to let you know, that the info you provided helped me to get it working.
What i changed:
I added APP_PROXIES in ".env" and configured my Host-IP and the Docker-Gateway-IP -> 192.168.178.10,172.26.0.1
Then i added the following config in the nginx-config inside the bookstack-volume:
"nginx/site-confs/default.conf"
After that, i restarted the containers.
And it is working. Now my real IPv6/IPv4 address is shown in Audit-Log instead of the docker-gateway.
Again, thank you very much for your help. Isse solved!
@ssddanbrown commented on GitHub (Jul 11, 2023):
Good to hear you get things working, thanks for sharing the solution for your environment!