Skip to content

Restricting IP Access 8080 port #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
CloudStrifer opened this issue Jun 13, 2025 · 1 comment
Open

Restricting IP Access 8080 port #551

CloudStrifer opened this issue Jun 13, 2025 · 1 comment

Comments

@CloudStrifer
Copy link

Dear Author:
Thank you very much for your work. I quickly set up Bookstack using Docker, but I have a question now. I deployed it in CentOS and enabled a policy to restrict access to port 8080 on the firewall, but it did not take effect.
I have looked into it and it may be related to Docker's network. I added the strategy to docker-compose.yml, but it didn't work. Is there any other way?
Thanks you so much.

@HJF9w
Copy link

HJF9w commented Jun 13, 2025

Hi,
What are you trying to do?
If you don't want it to be available on port 8080, you can just change the port number before the colon to whatever you want or remove the whole port: block to not publish any ports.
(Though that makes Bookstack completely unavailable.)

Normaly ip/nftables rules for your public interface (typically ethX or enpXsX) should still work, independently of what Docker does.

There is a document from Docker that might be helpful.
https://docs.docker.com/engine/network/packet-filtering-firewalls/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants