[GH-ISSUE #915] [Bug]: 127.0.0.1 Bind Not being parsed to docker container #632

New issue

Closed

opened 2026-05-06 12:31:29 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-06 12:31:29 +02:00

Owner

Originally created by @ThevinduW on GitHub (Apr 8, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/915

Originally assigned to: @maziggy on GitHub.

Bug Description

Using the docker install script to only advertise Bambuddy on localhost is not working

Expected Behavior

The Bambuddy service should not be accessible from other devices on the network.

Steps to Reproduce

Install bambuddy using the docker-install script in a Linux environment
Set Address to 127.0.0.1 when prompted for port

Printer Model

Not printer-related

Bambuddy Version

0.2.2.2

Printer Firmware Version

Not printer related

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

No response

Screenshots

No response

Additional Context

It appears the BIND_ADDRESS never gets parsed into the container at Dockerfile

This is my first time contributing to a public repository. I am sorry in advance if I have raised this issue in haste. Happy to fix if assigned!

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @ThevinduW on GitHub (Apr 8, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/915 Originally assigned to: @maziggy on GitHub. ### Bug Description Using the docker install script to only advertise Bambuddy on localhost is not working ### Expected Behavior The Bambuddy service should not be accessible from other devices on the network. ### Steps to Reproduce 1. Install bambuddy using the docker-install script in a Linux environment 2. Set Address to 127.0.0.1 when prompted for port ### Printer Model Not printer-related ### Bambuddy Version 0.2.2.2 ### Printer Firmware Version Not printer related ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package _No response_ ### Screenshots _No response_ ### Additional Context It appears the BIND_ADDRESS never gets parsed into the container at [Dockerfile](https://github.com/maziggy/bambuddy/blob/2bb65e2d5c87693a28e488248ddb22f3045d0c34/Dockerfile#L73) This is my first time contributing to a public repository. I am sorry in advance if I have raised this issue in haste. Happy to fix if assigned! ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-06 12:31:29 +02:00

closed this issue
added the
wontfix
label

BreizhHardware commented

2026-05-06 12:31:30 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 8, 2026):

You're right — the BIND_ADDRESS from the install script is never actually passed through to the Docker container. The Dockerfile hardcodes --host 0.0.0.0 for uvicorn, so the setting has no effect.

That said, even if we wired it through, binding to 127.0.0.1 wouldn't really achieve the goal of making BamBuddy inaccessible from the network — the web UI is only one of several services (FTP, MQTT, SSDP) that listen on the network for printer communication.

I'll remove the --bind option from the install script since it's non-functional and misleading. If you need to restrict access to the web UI, a firewall rule or reverse proxy would be the way to go.

@maziggy commented on GitHub (Apr 8, 2026): You're right — the BIND_ADDRESS from the install script is never actually passed through to the Docker container. The Dockerfile hardcodes --host 0.0.0.0 for uvicorn, so the setting has no effect. That said, even if we wired it through, binding to 127.0.0.1 wouldn't really achieve the goal of making BamBuddy inaccessible from the network — the web UI is only one of several services (FTP, MQTT, SSDP) that listen on the network for printer communication. I'll remove the --bind option from the install script since it's non-functional and misleading. If you need to restrict access to the web UI, a firewall rule or reverse proxy would be the way to go.