While transferring Portainer stacks to Komodo (saving each stack in separate folders), encountered issues with KOMODO_JWT_SECRET containing an @ symbol:
Steps to reproduce
Set KOMODO_JWT_SECRET with @ symbol in the value
Attempt to save/update environment configuration
Restart Komodo service
Expected behavior
Environment variables should save correctly regardless of special characters
Existing compose.yml files should remain intact after restart
Actual behavior
Komodo logs show JWT secret text after the @ symbol as unset env variable. Using "abc@zyxwt" as a JWT secret would log "zyxwt" is unset.
New environment value fails to update through KOMODO UI - required manual editing via nano on server
After restart via Terminal, some previously saved compose.yml files were deleted while retaining env files and stack names (stacks show as DOWN status)
Impact
Data loss of existing compose configurations
Manual server access required for environment variable updates
Environment
Komodo version: 1.18.4
Server OS: Ubuntu 24.04 LTS arm64
Thanks!
Originally created by @rmiller-gd on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/697
## Description
While transferring Portainer stacks to Komodo (saving each stack in separate folders), encountered issues with `KOMODO_JWT_SECRET` containing an @ symbol:
## Steps to reproduce
1. Set `KOMODO_JWT_SECRET` with @ symbol in the value
2. Attempt to save/update environment configuration
3. Restart Komodo service
## Expected behavior
- Environment variables should save correctly regardless of special characters
- Existing compose.yml files should remain intact after restart
## Actual behavior
1. Komodo logs show JWT secret text after the @ symbol as unset env variable. Using "abc@zyxwt" as a JWT secret would log "zyxwt" is unset.
3. New environment value fails to update through KOMODO UI - required manual editing via nano on server
4. After restart via Terminal, _some_ previously saved compose.yml files were deleted while retaining env files and stack names (stacks show as DOWN status)
## Impact
- Data loss of existing compose configurations
- Manual server access required for environment variable updates
## Environment
- Komodo version: 1.18.4
- Server OS: Ubuntu 24.04 LTS arm64
Thanks!
I cannot reproduce this issue, i just started up Komodo using KOMODO_JWT_SECRET with @ symbol and it worked fine. There aren't even any paths Komodo would delete any files on your host. Maybe you could try again to explain the issue, I am having some trouble following it.
<!-- gh-comment-id:3238979630 -->
@mbecker20 commented on GitHub (Aug 30, 2025):
I cannot reproduce this issue, i just started up Komodo using KOMODO_JWT_SECRET with @ symbol and it worked fine. There aren't even any paths Komodo would delete any files on your host. Maybe you could try again to explain the issue, I am having some trouble following it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rmiller-gd on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/697
Description
While transferring Portainer stacks to Komodo (saving each stack in separate folders), encountered issues with
KOMODO_JWT_SECRETcontaining an @ symbol:Steps to reproduce
KOMODO_JWT_SECRETwith @ symbol in the valueExpected behavior
Actual behavior
Impact
Environment
Thanks!
@mbecker20 commented on GitHub (Aug 30, 2025):
I cannot reproduce this issue, i just started up Komodo using KOMODO_JWT_SECRET with @ symbol and it worked fine. There aren't even any paths Komodo would delete any files on your host. Maybe you could try again to explain the issue, I am having some trouble following it.