No image when AUTH_RELAY set to hashed
Posted: Mon Dec 14, 2020 1:21 pm
Dear all,
I've been running ZoneMinder 1.32 for a while, but now want to migrate on Docker.
I used the dlandon image and everything went more or less good, except when I set the AUTH_RELAY option to hashed. I that case, I don't get any image and the log file shows the following :
Unable to authenticate user from https:[...]
getStreamCmdResponse stream error: Socket /run/zm/zms-014132s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit.
As suggested by some users having a similar issue, I checked the timezone parameter => ok, the AUTH_HASH_SECRET does not contain any special character,...
But still have the issue, unless I set the parameter AUTH_RELAY to none...
I've also an issue (un able to login at all) when I enable the parameter AUTH_HASH_LOGINS...
Any idea how I could fix that ? I remember it was working fine in the previous version (not dockerized).
Cheers,
Raj.
I've been running ZoneMinder 1.32 for a while, but now want to migrate on Docker.
I used the dlandon image and everything went more or less good, except when I set the AUTH_RELAY option to hashed. I that case, I don't get any image and the log file shows the following :
Unable to authenticate user from https:[...]
getStreamCmdResponse stream error: Socket /run/zm/zms-014132s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit.
As suggested by some users having a similar issue, I checked the timezone parameter => ok, the AUTH_HASH_SECRET does not contain any special character,...
But still have the issue, unless I set the parameter AUTH_RELAY to none...
I've also an issue (un able to login at all) when I enable the parameter AUTH_HASH_LOGINS...
Any idea how I could fix that ? I remember it was working fine in the previous version (not dockerized).
Cheers,
Raj.