starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #642] [Bug]: Setting up SMTP | Authentication > Email Authentication. Enabling Error #419

New issue

Closed

opened 2026-05-06 12:29:17 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

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

Owner

Originally created by @bwp85 on GitHub (Mar 7, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/642

Originally assigned to: @maziggy on GitHub.

Bug Description

Bug Description
When attempting to enable Email Authentication a message is presented when selecting the "Enable" button. Message "Please configure and Test SMTP settings first".
SMTP settings are greyed out and cannot be configured before enabling the feature

Expected Behavior
Enable the setting and then provide configuration information for SMTP

Steps to Reproduce
Navigate to "Settings" > "Authentication" > "Email Authentication"
Click on "Enable"

Printer Model
Not relevant

Bambuddy Version
v0.2.2b1

Installation Method
Docker

Operating System
Linux (Ubuntu/Debian)

Relevant Logs
No log entries related to SMTP settings

Expected Behavior

Enable the setting and then provide configuration information for SMTP

Steps to Reproduce

Navigate to "Settings" > "Authentication" > "Email Authentication"
Click on "Enable"

Printer Model

P2S

Bambuddy Version

v0.2.2b1

Printer Firmware Version

01.01.03.00

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

Screenshots

Additional Context

Image 1 is the error. Image 2 shows the greyed out fields that cannot be edited.

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 @bwp85 on GitHub (Mar 7, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/642 Originally assigned to: @maziggy on GitHub. ### Bug Description **Bug Description** When attempting to enable Email Authentication a message is presented when selecting the "Enable" button. Message "Please configure and Test SMTP settings first". SMTP settings are greyed out and cannot be configured before enabling the feature **Expected Behavior** Enable the setting and then provide configuration information for SMTP **Steps to Reproduce** Navigate to "Settings" > "Authentication" > "Email Authentication" Click on "Enable" **Printer Model** Not relevant **Bambuddy Version** v0.2.2b1 **Installation Method** Docker **Operating System** Linux (Ubuntu/Debian) **Relevant Logs** No log entries related to SMTP settings ### Expected Behavior Enable the setting and then provide configuration information for SMTP ### Steps to Reproduce 1. Navigate to "Settings" > "Authentication" > "Email Authentication" 2. Click on "Enable" ### Printer Model P2S ### Bambuddy Version v0.2.2b1 ### Printer Firmware Version 01.01.03.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots <img width="427" height="80" alt="Image" src="https://github.com/user-attachments/assets/2e0f2fab-9f16-496c-8a59-1123b7f6ebe2" /> <img width="693" height="883" alt="Image" src="https://github.com/user-attachments/assets/084ec681-6dad-43b2-b311-79d0ff30704f" /> ### Additional Context Image 1 is the error. Image 2 shows the greyed out fields that cannot be edited. ### 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:29:17 +02:00

closed this issue
added the
invalid
label

BreizhHardware commented

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

Author

Owner

@maziggy commented on GitHub (Mar 7, 2026):

I guess this was already fixed, because I cannot reproduce. Please use latest beta branch 0.2.2b3.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Mar 7, 2026): I guess this was already fixed, because I cannot reproduce. Please use latest beta branch 0.2.2b3. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!

BreizhHardware commented

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

Author

Owner

@stwalkerster commented on GitHub (Mar 16, 2026):

I am experiencing this issue too, and I'm on 0.2.2b3 (via the :latest tagged Docker image), and it's repeatedly recreatable for me.

Steps:

Deploy Bambuddy in Docker. I've used the below docker-compose file for repeatability, assuming a brand new, clean environment:

services:
  bambuddy:
    image: ghcr.io/maziggy/bambuddy:latest
    container_name: bambuddy
    user: "${PUID:-1000}:${PGID:-1000}"
    cap_add:
      - NET_BIND_SERVICE
    ports:
      - "${PORT:-8000}:8000"
    volumes:
      - bambuddy_data:/app/data
      - bambuddy_logs:/app/logs
    environment:
      - TZ=${TZ:-Europe/Berlin}
      - PORT=${PORT:-8000}
volumes:
  bambuddy_data:
  bambuddy_logs:

Browse to http://localhost:8000 to start the first-time setup. I used the following form values:

Enable Authentication: yes
Admin username: admin
Password: admin123

Proceed to log into the application using the credentials you just set
Go to Settings -> Authentication -> Email Authentication
Observe that the SMTP Configuration form is fully disabled, and cannot be used.
Click the Enable button on Advanced Authentication. Observe a message stating "Please configure and test SMTP settings first"

Relatedly, the documentation on this option at https://wiki.bambuddy.cool/features/authentication/#advanced-auth-via-email appears to be out-of-date, as there is no obvious email tab.

@stwalkerster commented on GitHub (Mar 16, 2026): I am experiencing this issue too, and I'm on 0.2.2b3 (via the `:latest` tagged Docker image), and it's repeatedly recreatable for me. Steps: 1. Deploy Bambuddy in Docker. I've used the below docker-compose file for repeatability, assuming a brand new, clean environment: ```yaml services: bambuddy: image: ghcr.io/maziggy/bambuddy:latest container_name: bambuddy user: "${PUID:-1000}:${PGID:-1000}" cap_add: - NET_BIND_SERVICE ports: - "${PORT:-8000}:8000" volumes: - bambuddy_data:/app/data - bambuddy_logs:/app/logs environment: - TZ=${TZ:-Europe/Berlin} - PORT=${PORT:-8000} volumes: bambuddy_data: bambuddy_logs: ``` 2. Browse to http://localhost:8000 to start the first-time setup. I used the following form values: * Enable Authentication: yes * Admin username: `admin` * Password: `admin123` 3. Proceed to log into the application using the credentials you just set 4. Go to Settings -> Authentication -> Email Authentication 5. Observe that the SMTP Configuration form is fully disabled, and cannot be used. 6. Click the Enable button on Advanced Authentication. Observe a message stating "Please configure and test SMTP settings first" Relatedly, the documentation on this option at https://wiki.bambuddy.cool/features/authentication/#advanced-auth-via-email appears to be out-of-date, as there is no obvious email tab.

BreizhHardware commented

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

Author

Owner

@stwalkerster commented on GitHub (Mar 16, 2026):

It's probably also worth noting that changing the docker image to ghcr.io/maziggy/bambuddy:0.2.2b4-daily.20260315 and doing a docker compose down -v / docker compose up -d reveals the exact same issue; this isn't something that's been fixed in the latest daily release

@stwalkerster commented on GitHub (Mar 16, 2026): It's probably also worth noting that changing the docker image to `ghcr.io/maziggy/bambuddy:0.2.2b4-daily.20260315` and doing a `docker compose down -v` / `docker compose up -d` reveals the exact same issue; this isn't something that's been fixed in the latest daily release

BreizhHardware commented

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

Author

Owner

@maziggy commented on GitHub (Mar 16, 2026):

This is already fixed and available in the next release (very soon).

@maziggy commented on GitHub (Mar 16, 2026): This is already fixed and available in the next release (very soon).

BreizhHardware referenced this issue

2026-05-06 12:34:40 +02:00

[PR #455] [MERGED] Allow external materials/brands to be used when adding spool #1045