Broken dashboard on alpine-traefik configuration file #1033

Closed
opened 2026-02-04 22:42:03 +03:00 by OVERLORD · 9 comments
Owner

Originally created by @Redplcs on GitHub (May 29, 2025).

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

alpine-traefik

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-traefik.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Alpine

📝 Provide a clear and concise description of the issue.

I've spend whole day trying to enable dashboard that somehow does not returns anything. Browser drops closed connection, so I've managed to check the configuration file and found out that dashboard listens on 8080 under localhost. My container gets ip from dhcp and has other ip address, not localhost. I've run netstat -tuln and it showed that 80 and 443 listens on :::80 and :::443, but the dashboard itself under localhost:8080. I don't think this is a correct behaviour when I was agreed with enabling dashboard and didn't expect that it will be listen inside of lxc container.

Is yaml file correct and this behavior is meant to be or not?

Also traefik --configFile=/etc/traefik/traefik.yaml didn't worked to reload configuration. I had to reboot whole container

🔄 Steps to reproduce the issue.

  • Run script using this configuration file:
# alpine-traefik Configuration File
# Generated on Mon May 26 11:10:27 PM MSK 2025

CT_TYPE="1"
DISK_SIZE="1"
CORE_COUNT="1"
RAM_SIZE="512"
HN="traefik"
BRG="vmbr0"
APT_CACHER_IP="none"
DISABLEIP6="yes"
PW="none"
SSH="no"
SSH_AUTHORIZED_KEY=""
VERBOSE="no"
TAGS="alpine"
VLAN="none"
MTU="1500"
GATE="none"
SD="none"
MAC="none"
NS="none"
NET="dhcp"
  • Try to get into dashboard under 'ip address given by dhcp:8080/dashboard/'
  • Live with pain

Paste the full error output (if available).

Traefik logs are empty

🖼️ Additional context (optional).

No response

Originally created by @Redplcs on GitHub (May 29, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? alpine-traefik ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-traefik.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Alpine ### 📝 Provide a clear and concise description of the issue. I've spend whole day trying to enable dashboard that somehow does not returns anything. Browser drops closed connection, so I've managed to check the configuration file and found out that dashboard listens on 8080 under localhost. My container gets ip from dhcp and has other ip address, not localhost. I've run `netstat -tuln` and it showed that 80 and 443 listens on `:::80` and `:::443`, but the dashboard itself under `localhost:8080`. I don't think this is a correct behaviour when I was agreed with enabling dashboard and didn't expect that it will be listen inside of lxc container. Is yaml file correct and this behavior is meant to be or not? Also `traefik --configFile=/etc/traefik/traefik.yaml` didn't worked to reload configuration. I had to reboot whole container ### 🔄 Steps to reproduce the issue. - Run script using this configuration file: ``` # alpine-traefik Configuration File # Generated on Mon May 26 11:10:27 PM MSK 2025 CT_TYPE="1" DISK_SIZE="1" CORE_COUNT="1" RAM_SIZE="512" HN="traefik" BRG="vmbr0" APT_CACHER_IP="none" DISABLEIP6="yes" PW="none" SSH="no" SSH_AUTHORIZED_KEY="" VERBOSE="no" TAGS="alpine" VLAN="none" MTU="1500" GATE="none" SD="none" MAC="none" NS="none" NET="dhcp" ``` - Try to get into dashboard under 'ip address given by dhcp:8080/dashboard/' - Live with pain ### ❌ Paste the full error output (if available). Traefik logs are empty ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 22:42:03 +03:00
Author
Owner

@Redplcs commented on GitHub (May 29, 2025):

I'm not familiar with traefik. I know basis of reverse proxy, but never worked with them. I might be wrong in deployment

@Redplcs commented on GitHub (May 29, 2025): I'm not familiar with traefik. I know basis of reverse proxy, but never worked with them. I might be wrong in deployment
Author
Owner

@tremor021 commented on GitHub (May 29, 2025):

Image
that file doesnt exist

@tremor021 commented on GitHub (May 29, 2025): ![Image](https://github.com/user-attachments/assets/237436e2-1211-45aa-9b35-1eafc3babd4d) that file doesnt exist
Author
Owner

@Redplcs commented on GitHub (May 29, 2025):

@tremor021 I think it's because that repo is hidden. I thought this would work. Updated issue

# alpine-traefik Configuration File
# Generated on Mon May 26 11:10:27 PM MSK 2025

CT_TYPE="1"
DISK_SIZE="1"
CORE_COUNT="1"
RAM_SIZE="512"
HN="traefik"
BRG="vmbr0"
APT_CACHER_IP="none"
DISABLEIP6="yes"
PW="none"
SSH="no"
SSH_AUTHORIZED_KEY=""
VERBOSE="no"
TAGS="alpine"
VLAN="none"
MTU="1500"
GATE="none"
SD="none"
MAC="none"
NS="none"
NET="dhcp"
@Redplcs commented on GitHub (May 29, 2025): @tremor021 I think it's because that repo is hidden. I thought this would work. Updated issue ``` # alpine-traefik Configuration File # Generated on Mon May 26 11:10:27 PM MSK 2025 CT_TYPE="1" DISK_SIZE="1" CORE_COUNT="1" RAM_SIZE="512" HN="traefik" BRG="vmbr0" APT_CACHER_IP="none" DISABLEIP6="yes" PW="none" SSH="no" SSH_AUTHORIZED_KEY="" VERBOSE="no" TAGS="alpine" VLAN="none" MTU="1500" GATE="none" SD="none" MAC="none" NS="none" NET="dhcp" ```
Author
Owner

@tremor021 commented on GitHub (May 29, 2025):

The config file you pasted is the one to create the container. It has nothing to do with traefik the app

@tremor021 commented on GitHub (May 29, 2025): The config file you pasted is the one to create the container. It has nothing to do with traefik the app
Author
Owner

@Redplcs commented on GitHub (May 29, 2025):

Yea. The traefik yaml was neven changed. The cli asked would i like to add dashboard and i said yes. After that i've tried to connect into it and browser said closed connection or something like that. i've checked all opened ports and found out that it listens on localhost. I think it's the problem with configuration file that script generates

@Redplcs commented on GitHub (May 29, 2025): Yea. The traefik yaml was neven changed. The cli asked would i like to add dashboard and i said yes. After that i've tried to connect into it and browser said `closed connection` or something like that. i've checked all opened ports and found out that it listens on localhost. I think it's the problem with configuration file that script generates
Author
Owner

@Redplcs commented on GitHub (May 29, 2025):

This is what helper script generates for static configuration

global:
  checkNewVersion: false
  sendAnonymousUsage: false

log:
  filePath: /var/log/traefik/traefik.log

accessLog:
  filePath: /var/log/traefik/access.log

entryPoints:
  http:
    address: ':80'
  https:
    address: ':443'
  traefik:
    address: 'localhost:8080'

api:
  insecure: true
  dashboard: true

ping: {}

#certificatesResolvers:
#  sample:
#    acme:
#      email: ''
#      storage: traefik/acme/account
#      dnsChallenge:
#        provider: cloudflare
#        delayBeforeCheck: 10
@Redplcs commented on GitHub (May 29, 2025): This is what helper script generates for static configuration ``` global: checkNewVersion: false sendAnonymousUsage: false log: filePath: /var/log/traefik/traefik.log accessLog: filePath: /var/log/traefik/access.log entryPoints: http: address: ':80' https: address: ':443' traefik: address: 'localhost:8080' api: insecure: true dashboard: true ping: {} #certificatesResolvers: # sample: # acme: # email: '' # storage: traefik/acme/account # dnsChallenge: # provider: cloudflare # delayBeforeCheck: 10 ```
Author
Owner

@tremor021 commented on GitHub (May 29, 2025):

Seems like they changed a bit the default config.

do:

rc-service traefik stop

remove localhost from localhost:8080 so it just says :8080

then do:

rc-service traefik start
@tremor021 commented on GitHub (May 29, 2025): Seems like they changed a bit the default config. do: ```bash rc-service traefik stop ``` remove `localhost` from `localhost:8080` so it just says `:8080` then do: ```bash rc-service traefik start ```
Author
Owner

@Redplcs commented on GitHub (May 29, 2025):

yea i already did it. i've changed entrypoint from localhost:8080 to :8080 and rebooted container. i was just curious is it bug or "feature"

@Redplcs commented on GitHub (May 29, 2025): yea i already did it. i've changed entrypoint from `localhost:8080` to `:8080` and rebooted container. i was just curious is it bug or "feature"
Author
Owner

@tremor021 commented on GitHub (May 29, 2025):

They now create the default config themselves, hence why our script fails. Script makes traefik.yml config file in the /etc/traefik/ directory, but traefik.yaml created by the app takes precedence.
You can also fix your container just by deleting traefik.yaml created by the app.

Anyway, we gonna fix it on a script level. Thanks for noticing this

@tremor021 commented on GitHub (May 29, 2025): They now create the default config themselves, hence why our script fails. Script makes `traefik.yml` config file in the `/etc/traefik/` directory, but `traefik.yaml` created by the app takes precedence. You can also fix your container just by deleting `traefik.yaml` created by the app. Anyway, we gonna fix it on a script level. Thanks for noticing this
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1033