debug info? #1

New Issue

2026-10-05T03:11:17+02:00

adam commented

2026-10-05 03:11:17 +02:00

First of all; thanks for the awesome work!

Quick question; Sending messages, joining channels, everything works, but received messages aren't showing up. I can confirm the node (companion USB) is receiving them, as I can also see them with the mesh-cli, but nothing shows on the web app.

I've enabled debugging, but cannot find the log file, any clue where to look?

Thanks!

First of all; thanks for the awesome work! Quick question; Sending messages, joining channels, everything works, but received messages aren't showing up. I can confirm the node (companion USB) is receiving them, as I can also see them with the mesh-cli, but nothing shows on the web app. I've enabled debugging, but cannot find the log file, any clue where to look? <img width="497" height="347" alt="Image" src="https://github.com/user-attachments/assets/c6a5024b-8b55-4911-b6ba-dc8de9dfa832" /> Thanks!

adam closed this issue

2026-10-05 03:11:17 +02:00

adam commented

2026-10-05 03:11:18 +02:00

Hi
Thanks for your input!

Could you please try to switch to the dev branch of the project rebuild your app with the following commands:

# 1. Stop current containers
cd ~/mc-webui
docker compose down

# 2. Switch to dev branch
git fetch origin
git checkout dev

# 3. Pull latest changes
git pull origin dev

# 4. Rebuild and start containers
docker compose up -d --build

# 5. Monitor logs to verify msgs_subscribe is working
docker compose logs -f

After updating your application from the latest dev repository I highly recommend checking out these diagnostic tools:
https://github.com/MarekWo/mc-webui/blob/dev/technotes/API-Diagnostic-Commands.md

It is also very helpful to set up password-less ssh login prior to that so that you do not have provide ssh password each time you remote to your server:
https://wiki.wojtaszek.it/pl/home/general-linux/ssh-paswordless-login

Let me know if it was helpful.

Marek

Hi Thanks for your input! Could you please try to switch to the dev branch of the project rebuild your app with the following commands: ```bash # 1. Stop current containers cd ~/mc-webui docker compose down # 2. Switch to dev branch git fetch origin git checkout dev # 3. Pull latest changes git pull origin dev # 4. Rebuild and start containers docker compose up -d --build # 5. Monitor logs to verify msgs_subscribe is working docker compose logs -f ``` After updating your application from the latest dev repository I highly recommend checking out these diagnostic tools: https://github.com/MarekWo/mc-webui/blob/dev/technotes/API-Diagnostic-Commands.md It is also very helpful to set up password-less ssh login prior to that so that you do not have provide ssh password each time you remote to your server: https://wiki.wojtaszek.it/pl/home/general-linux/ssh-paswordless-login Let me know if it was helpful. Marek

adam commented

2026-10-05 03:11:19 +02:00

Hi Marek,

The logs were helpful, I guess my node name was the issue, it had a space in the name and that resulted in a 'file not found' error;
app.meshcore.parser - WARNING - Messages file not found: /root/.config/meshcore/Remo WebUI.msgs

Changed the name, restarted, everything working as expected 🙌

Thanks!

Hi Marek, The logs were helpful, I guess my node name was the issue, it had a space in the name and that resulted in a 'file not found' error; `app.meshcore.parser - WARNING - Messages file not found: /root/.config/meshcore/Remo WebUI.msgs` Changed the name, restarted, everything working as expected 🙌 Thanks!

adam commented

2026-10-05 03:11:19 +02:00

This is an great catch! I will fix that in the next release as it should be immune to spaces in the name. Thanks for sharing that!

This is an great catch! I will fix that in the next release as it should be immune to spaces in the name. Thanks for sharing that!

adam commented

2026-10-05 03:11:20 +02:00

GitHub Issue Response: Spaces in MC_DEVICE_NAME

Issue: User @remowashere reported that the application fails when MC_DEVICE_NAME contains spaces (e.g., "Remo WebUI"), resulting in "file not found" errors for .msgs files.

Hi @remowashere,

Thanks for reporting this issue! I've investigated the problem with spaces in MC_DEVICE_NAME and did some testing.

Good news: The current version of mc-webui (on both dev and main branches) handles spaces in device names correctly. I tested with MC_DEVICE_NAME="MarWoj Test" and the application successfully reads the .msgs file without any issues:

mc-webui | INFO - Loaded 1 messages from /root/.config/meshcore/MarWoj Test.msgs

The application uses Python's pathlib.Path for file operations, which properly handles spaces and special characters in filenames.

Possible causes of your issue

Outdated version - You might be running an older version of the application
meshcore-cli version - Older versions of meshcore-cli might have had issues creating files with spaces
Configuration issue - The MC_DEVICE_NAME environment variable might not match the actual device name used by meshcore-cli
File permissions - The .msgs file might not have been created yet or lacks proper permissions

Recommended steps

1. Update to the latest version

cd ~/mc-webui
git pull origin main
docker compose down
docker compose up -d --build

2. Verify your configuration

# Check your .env file
cat .env | grep MC_DEVICE_NAME

# List actual .msgs files
ls -la ~/.config/meshcore/*.msgs

Important: Make sure the value of MC_DEVICE_NAME in your .env file matches the device name configured in meshcore-cli. The .msgs file is created by meshcore-cli using the device name you configured on the device itself.

3. Check logs for more details

docker compose logs -f mc-webui | grep -i "messages file"

Look for log lines indicating which file path the application is trying to access and whether it exists.

4. Verify meshcore-cli version

The application requires meshcore-cli >= 1.3.12. The Docker container installs the latest version automatically, but if you're running an older version, please update.

Additional troubleshooting

If you're still experiencing issues after updating, please share:

Docker logs:

docker compose logs --tail=100 mc-webui
docker compose logs --tail=100 meshcore-bridge

Git version:
```
git log -1 --oneline
```
Environment configuration (with sensitive data redacted):
```
cat .env
```

Actual .msgs files on disk:

ls -la ~/.config/meshcore/ | grep .msgs

This information will help me understand exactly what's happening in your environment.

Let me know if updating resolves the issue!

Best regards,
Marek

# GitHub Issue Response: Spaces in MC_DEVICE_NAME **Issue:** User @remowashere reported that the application fails when `MC_DEVICE_NAME` contains spaces (e.g., "Remo WebUI"), resulting in "file not found" errors for `.msgs` files. --- Hi @remowashere, Thanks for reporting this issue! I've investigated the problem with spaces in `MC_DEVICE_NAME` and did some testing. **Good news:** The current version of mc-webui (on both `dev` and `main` branches) handles spaces in device names correctly. I tested with `MC_DEVICE_NAME="MarWoj Test"` and the application successfully reads the `.msgs` file without any issues: ``` mc-webui | INFO - Loaded 1 messages from /root/.config/meshcore/MarWoj Test.msgs ``` The application uses Python's `pathlib.Path` for file operations, which properly handles spaces and special characters in filenames. ## Possible causes of your issue 1. **Outdated version** - You might be running an older version of the application 2. **meshcore-cli version** - Older versions of meshcore-cli might have had issues creating files with spaces 3. **Configuration issue** - The `MC_DEVICE_NAME` environment variable might not match the actual device name used by meshcore-cli 4. **File permissions** - The `.msgs` file might not have been created yet or lacks proper permissions ## Recommended steps ### 1. Update to the latest version ```bash cd ~/mc-webui git pull origin main docker compose down docker compose up -d --build ``` ### 2. Verify your configuration ```bash # Check your .env file cat .env | grep MC_DEVICE_NAME # List actual .msgs files ls -la ~/.config/meshcore/*.msgs ``` **Important:** Make sure the value of `MC_DEVICE_NAME` in your `.env` file matches the device name configured in meshcore-cli. The `.msgs` file is created by meshcore-cli using the device name you configured on the device itself. ### 3. Check logs for more details ```bash docker compose logs -f mc-webui | grep -i "messages file" ``` Look for log lines indicating which file path the application is trying to access and whether it exists. ### 4. Verify meshcore-cli version The application requires meshcore-cli >= 1.3.12. The Docker container installs the latest version automatically, but if you're running an older version, please update. ## Additional troubleshooting If you're still experiencing issues after updating, please share: 1. **Docker logs:** ```bash docker compose logs --tail=100 mc-webui docker compose logs --tail=100 meshcore-bridge ``` 2. **Git version:** ```bash git log -1 --oneline ``` 3. **Environment configuration** (with sensitive data redacted): ```bash cat .env ``` 4. **Actual .msgs files on disk:** ```bash ls -la ~/.config/meshcore/ | grep .msgs ``` This information will help me understand exactly what's happening in your environment. Let me know if updating resolves the issue! Best regards, Marek

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/mc-webui#1