dashboardPassword not working..

[ynzheng]

after Ihave set the dashboardPassword...I saw it`s there in the config.user.json..

but no any password request when I open the http://URL:3000

last but not the least,

I do "Enable Remote WebSocket Access" on the "Bot Configuration" (tested with auto and IP ), save...and "Configuration saved successfully"

But , refresh the webpage... It`s gone...

I cannot re-open the ISSue #2

so I comment it here

[RedBoardDev]

Same problem here, it seems that saving settings doesn't work very well, because I also have issues with symbols.

[CryptoGnome]

@claude can you fix this?

[claude]

Claude finished @CryptoGnome's task —— View job • claude/issue-5-20250928-1133 • Create PR ➔

---

✅ Configuration Persistence Issues Fixed

All tasks have been completed successfully!

Todo List:

• Investigate current configuration system implementation
• Check dashboard authentication mechanism
• Update config schema to include remote WebSocket settings
• Fix dashboard password authentication middleware
• Fix config merging for nested server object
• Create client-side authentication check
• Ensure all configuration changes save properly
• Test the fixes
• Commit and push changes

Summary of Changes:

1. Fixed Dashboard Password Authentication:

   • Replaced development-mode bypass with proper authentication flow
   • Added client-side AuthCheck component that verifies if password is required
   • Authentication now works correctly when a password is set in config

2. Fixed Remote WebSocket Configuration Persistence:

   • Added useRemoteWebSocket and websocketHost fields to config schema
   • Updated config merger to properly handle nested server configuration
   • Fixed useWebSocketUrl hook to correctly access config structure

3. Resolved Edge Runtime Compatibility Issues:

   • Removed Node.js imports from middleware (Edge Runtime compatible)
   • Implemented cookie-based authentication state tracking

4. Improved Configuration System:

   • Enhanced config migration to properly merge nested objects
   • Updated default configuration with all server settings
   • Fixed configuration persistence for all fields

The changes ensure that:

• Dashboard password authentication works when configured
• Remote WebSocket settings are saved and persist across page refreshes
• All configuration changes are properly saved to config.user.json

---

Branch: claude/issue-5-20250928-1133