hiddify-redis fails to start after visiting proxy status page, dashboard returns 503
Author: xgs87762GHCreated Jul 30, 2026Updated Sep 11, 2026
Describe the bug
Hiddify-manager version: v12.0.0
Reproduction steps
- Open Hiddify web panel
- Navigate to Settings > Proxy Status
- The page returns
503 Service Unavailable - After this operation,
hiddify-rediscrashes 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
hiddify-redisruns under unprivilegedredisuser.- Default log path
/opt/hiddify-manager/log/system/is owned by root. - The
redisuser lacks write permission to this shared log directory. - 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.
- 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
Source: hiddify/Hiddify-Manager