You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
π Provide a clear and concise description of the issue.
Upon finishing the installation (regardless of default or advanced settings), the script gives http://lxcipaddress:9442 as the frontend URL, however this seems to be a mistake since by default, port 8080 is used for frontend as per Zigbee2MQTT official documentation, and no modification to the configuration.yaml file is made by the script to enforce port 9442.
Screen captures attached from a test run made while creating this post.
Maybe I'm just dumb but it bothered me when I ran tests before migrating my main Z2M instance to 2.0.0 the other day, so I wanted to report on what seems to me like an issue.
βοΈ What settings are you using?
Default Settings
Advanced Settings
π₯οΈ Which Linux distribution are you using?
Debian 12
π Steps to reproduce the issue.
Running the script with default or advanced settings (gives the same result).
β Paste the full error output (if available).
No error messages per se, just erroneous port information (IMHO).
πΌοΈ Additional context (optional).
The text was updated successfully, but these errors were encountered:
β Have you read and understood the above guidelines?
yes
π What is the name of the script you are using?
Zigbee2MQTT
π What was the exact command used to execute the script?
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zigbee2mqtt.sh)"
π Provide a clear and concise description of the issue.
Upon finishing the installation (regardless of default or advanced settings), the script gives http://lxcipaddress:9442 as the frontend URL, however this seems to be a mistake since by default, port 8080 is used for frontend as per Zigbee2MQTT official documentation, and no modification to the configuration.yaml file is made by the script to enforce port 9442.
Screen captures attached from a test run made while creating this post.
Maybe I'm just dumb but it bothered me when I ran tests before migrating my main Z2M instance to 2.0.0 the other day, so I wanted to report on what seems to me like an issue.
βοΈ What settings are you using?
π₯οΈ Which Linux distribution are you using?
Debian 12
π Steps to reproduce the issue.
Running the script with default or advanced settings (gives the same result).
β Paste the full error output (if available).
No error messages per se, just erroneous port information (IMHO).
πΌοΈ Additional context (optional).
The text was updated successfully, but these errors were encountered: