SOLVED: Forbidden You don't have permission to access /zm on this server.

[neuronetv]

I've been running zoneminder-1.29.0-3.el6.x86_64 on centos 6 for ages, it's always been fine. Today when trying to get the web gui I suddenly get:

Code: Select all

Forbidden
You don't have permission to access /zm on this server.
Apache/2.2.15 (CentOS) Server at 172.16.1.180 Port 80

this is puzzling because the web gui has always worked in the past and nothing has been done on the server to change anything.What would cause this?

[neuronetv]

bump.
anyone? please?
I've been trawling google and this forum for hours. I've got 'Require all Granted' in httpd.conf, I've even wiped and reimstalled zoneminder but I still get this error. Nothing works.

[SteveGilvarry]

Nothing more useful in apache logs? Not likely to be anything zoneminder itself just how you have apache configured. Maybe knnniggett will wander in here as he is Centos user.

And backup everything in case fixing it breaks it more.

[neuronetv]

hi & thanks, no nothing in the logs. While trying to log in I've done tail -f on /var/log/messages, /var/log/httpd/error_log, /var/log/access_log - nothing happens, and the folder /var/log/zoneminder is empty. I don't know what other logs to try

[neuronetv]

I feel such a fool. I was getting "Forbidden" because I was using http and not https (red faced). Hopefully this may help someone else who finds themselves locked out of the web gui.

[knight-of-ni]

I feel such a fool. I was getting "Forbidden" because I was using http and not https (red faced). Hopefully this may help someone else who finds themselves locked out of the web gui.

The zoneminder rpm for el6 in zmrepo, ships out of the box with an Apache HTTP->HTTPS redirect to avoid precisely this problem:
https://github.com/ZoneMinder/ZoneMinde ... conf.in#L7

Did you disable this on your system?

UPDATE: Now that I think about it, I don't remember exactly when I added the redirect. Since you stated you are running 1.29.0, that might predate the change I referenced. You can always add those lines of code manually to your apache config to avoid this issue again in the future.