mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 03:09:39 +03:00
Docker bookstack installation is not loading properly and causing no css issues #3366
Closed
opened 2026-02-05 06:30:03 +03:00 by OVERLORD
·
11 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#3366
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 @9ieR on GitHub (Nov 26, 2022).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
I followed all the steps from the recommended docker-compose installation of linuxserver docker-bookstack github .
I used the docker-compose file there which is
After running
docker-compose up -d, everything went well but when I connect to APP_URL (docs.something.com), I get the 'cannot find this page' error. I haven't used any reversed proxy. I'm also not sure where to pin point the errors since I'm not very familiar with php and apache stuffs. It is a completely clean install. I haven't done anything to the containers yet.I've also tried adding http:// and https:// in front of my app_url environmental variable but they didn't work.
Another weird thing is that the url changed into
http://X.X.X.X:6875/docs.something.com/docs.something.com/loginwhen I just usedX.X.X.X:6875instead of app_url.https://X.X.X.X:6875doesn't work. Onlyhttp://does.This weird long url works and the page shows but there is no css in the page. I've found some closed issues here similar to that no css loading problem but they are on host installations and seemed to be caused by something entirely different from mine.
Can you help me?
Exact BookStack Version
v22.10.2-ls50
Log Content
No response
PHP Version
8.0.25
Hosting Environment
installed using official installation script(no proxies used for docker containers)
@ssddanbrown commented on GitHub (Nov 26, 2022):
Hi @9ieR,
APP_URLmust be the exact base URL used to access your BookStack instance in the browser, sohttp://X.X.X.X:6875unless you're using a domain/host name when accessing in browser. Also ensure you are re-upping the compose stack, rather than just restarting, to ensure env changes are used.@9ieR commented on GitHub (Nov 26, 2022):
Hi @ssddanbrown
Yep, I've done that. When I up the yaml compose file, I made sure that I deleted the existing containers, images, volumes and even networks related to the compose file.
I've also just tried using IP address in place of URL. Still no luck though. The url just changed into
http://X.X.X.X:6875/X.X.X.X:6875/X.X.X.X:6875/login. And css still missing.@ssddanbrown commented on GitHub (Nov 26, 2022):
Just to confirm, does the current value definitely start with
http://orhttps://. The only times I've seen the IP/host duplication, as you describe, is specifically when theAPP_URLdoes not start with the protocol.@9ieR commented on GitHub (Nov 26, 2022):
http://https://doesn't work. It causes the page to not load up at all. I'm also wondering why it's working with https but with http. Seems like I can't also call apache's default index.html of my host with https but only with http.@ssddanbrown commented on GitHub (Nov 26, 2022):
I would not expect
https://to work unless you've done specific setup to support it.So you currently have
APP_URL=http://X.X.X.X:6875defined for the bookstack container? Where are you setting this? Via theenvironmentof the docker-compose.yaml or via an.envfile?@9ieR commented on GitHub (Nov 26, 2022):
Yep! I changed it in the docker-compose.yaml file. I don't try to change environmental variables after the containers are up and running.
Whenever I want to test something different, I just delete everything about the current containers/images and go back making changes to compose file and up it again.
Currently, the environment variable APP_URL in the docker-compose.yml is
APP_URL=http://X.X.X.X:6875@ssddanbrown commented on GitHub (Nov 26, 2022):
Okay, in that configuration, can you load BookStack (In its broken design state).
View the page source (Right click page > View source).
Find the lines towards the top (About 20 lines down) that look something like this:
Look at the
hrefvalue in the second line of that part, and compare exactly to the URL you've used forAPP_URL. Do these differ?@9ieR commented on GitHub (Nov 26, 2022):
Oh hey! It worked. But I'm still not satisfied because it's still not working in the way I wanted it to. I also want to know what's the cause of it.
When I changed the APP_URL in the compose file to
http://X.X.X.X:6875, it started working normally. But what if I just to use the domain name? Likedocs.something.com. How can I make it so?@ssddanbrown commented on GitHub (Nov 26, 2022):
@9ieR From the perspective of the BookStack, and the linuxserver.io image, you just need to set your
APP_URLto behttp://docs.something.com, but networking would need to be in place so requests to the domain on port 80 are routed to the container as expected.It it helps, I created a full end-to-end video for using the linuxserver image and setting it up on a domain with HTTPS:
https://www.youtube.com/watch?v=dbDzPIv8Cf8
@9ieR commented on GitHub (Nov 26, 2022):
@ssddanbrown
Thanks a ton. I'm checking it out.
By the way, am I supposed to close this issue now? This is my first time creating an issue on github. I'll just open a new one if something isn't working. I can right?
@ssddanbrown commented on GitHub (Nov 26, 2022):
Yeah, If there's nothing further to discuss here this can be closed off, I'll go ahead and do this.
If preferred, there's also a help/support channel in our discord server. Can be a little easier to request support there and often more people active there to help out.