hiddify-redis fails to start after visiting proxy status page, dashboard returns 503

[xgs87762GH]

Describe the bug

Hiddify-manager version: v12.0.0

Reproduction steps

1. Open Hiddify web panel
2. Navigate to Settings > Proxy Status
3. The page returns 503 Service Unavailable
4. After this operation, hiddify-redis crashes and cannot start automatically anymore.

Full error log

Can't open the log file: Permission denied
hiddify-redis.service: Main process exited, code=exited, status=1/FAILURE
hiddify-redis.service: Failed with result 'exit-code'.
Failed to start Hiddify Redis.
hiddify-redis.service: Scheduled restart job, restart counter is at 1.
Stopped Hiddify Redis.
Starting Hiddify Redis...
*** FATAL CONFIG FILE ERROR (Redis 6.0.16) ***
Reading the configuration file, at line 8
>>> 'logfile /opt/hiddify-manager/log/system/redis-server.log'
Can't open the log file: Permission denied
hiddify-redis.service: Main process exited, code=exited, status=1/FAILURE
hiddify-redis.service: Failed with result 'exit-code'.
Failed to start Hiddify Redis.
hiddify-redis.service: Scheduled restart job, restart counter is at 2.
Stopped Hiddify Redis.
Starting Hiddify Redis...
*** FATAL CONFIG FILE ERROR (Redis 6.0.16) ***
Reading the configuration file, at line 8
>>> 'logfile /opt/hiddify-manager/log/system/redis-server.log'
Can't open the log file: Permission denied
hiddify-redis.service: Main process exited, code=exited, status=1/FAILURE
hiddify-redis.service: Failed with result 'exit-code'.
Failed to start Hiddify Redis.
hiddify-redis.service: Scheduled restart job, restart counter is at 3.
Stopped Hiddify Redis.
Starting Hiddify Redis...
*** FATAL CONFIG FILE ERROR (Redis 6.0.16) ***

Root Cause

1. hiddify-redis runs under unprivileged redis user.
2. Default log path /opt/hiddify-manager/log/system/ is owned by root.
3. The redis user lacks write permission to this shared log directory.
4. When accessing Proxy Status page, panel interacts with Redis; Redis attempts to write log, hits permission error and exits immediately, leading to 503 error on frontend.
5. It is unsafe to change the owner of /opt/hiddify-manager/log/system/ to redis, as the main hiddify-manager process running as root also writes logs here, which will trigger new permission conflicts.

Suggested Solutions

Option 1
Create an independent log directory for Redis e.g. /opt/hiddify-manager/log/redis/, set ownership to redis:redis, and modify logfile path inside redis.conf.

Option 2 (simpler)
Set logfile "" in redis.conf to disable file logging, redirect all Redis logs to systemd journal, completely avoid file permission problems.

Environment

• OS: Ubuntu
• Hiddify-manager version: 12.0.0
• Redis version: 6.0.16