ZoneMinder LXC Container API Problem

Forum for questions and support relating to the 1.34.x releases only.
Post Reply
poohbah
Posts: 6
Joined: Sun Nov 15, 2020 10:11 pm

ZoneMinder LXC Container API Problem

Post by poohbah »

I'm running Zoneminder 1.34 in as an LXC container in Proxmox 6.2. I am having trouble getting the API working. At this point I am not even sure it is installed. I've been reading the forums and documentation, but I can't seem to find a situation that matches my own. I followed the instructions here: https://zoneminder.readthedocs.io/en/st ... abling-api to do the basic API setup. All is good until I run the curl -XPOST -d "user=admin&pass=mypassord" http://192.168.97.30/zm/api/host/getVersion.json. I get the following output when I run the command:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body></html>

When I run: http://192.168.97.30/zm/api/host/getVersion.json, I get a 404 error in my browser.

Any help is appreciated
User avatar
Bluemax
Posts: 121
Joined: Wed Jun 12, 2019 5:15 pm

Re: ZoneMinder LXC Container API Problem

Post by Bluemax »

Please post your web server configuration.
poohbah
Posts: 6
Joined: Sun Nov 15, 2020 10:11 pm

Re: ZoneMinder LXC Container API Problem

Post by poohbah »

apache2.conf posted below.

# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
# `-- sites-enabled
# `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections which can be
# customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
# directories contain particular configuration snippets which manage modules,
# global configuration fragments, or virtual host configurations,
# respectively.
#
# They are activated by symlinking available configuration files from their
# respective *-available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
# their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
# work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#

DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
Options FollowSymLinks
AllowOverride None
Require all denied
</Directory>

<Directory /usr/share>
AllowOverride None
Require all granted
</Directory>

<Directory /var/www/>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>

#<Directory /srv/>
# Options Indexes FollowSymLinks
# AllowOverride None
# Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
User avatar
Bluemax
Posts: 121
Joined: Wed Jun 12, 2019 5:15 pm

Re: ZoneMinder LXC Container API Problem

Post by Bluemax »

That's not much of use. I guess it's rather the 'sites-enabled' one.

The rest does work? Liveview? Recording? Playback?
What container os is running in lxc?
poohbah
Posts: 6
Joined: Sun Nov 15, 2020 10:11 pm

Re: ZoneMinder LXC Container API Problem

Post by poohbah »

It's working pretty well. The container system is Proxmox built on top of Debian Buster I've got live view (only works with authentication turned off), storage is working with a bound mount to a dedicated disk within the node. Playback seems to be ok, but I get a "No Data" in the Montage review camera view. Could that be an issue with the time? I don't know. At this point, the only error I see in the log has to do with php timezone settings. I'm still working that one out.

From Sites Enabled
Default.conf
ServerName localhost

<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www/
</VirtualHost>

<VirtualHost *:443>
SSLEngine on
ServerAdmin webmaster@localhost
DocumentRoot /var/www/
</VirtualHost>


<Directory /var/www/>
Options Indexes FollowSymLinks MultiViews
Require all granted
</Directory>

Adminder.conf

#Apache configuration

<VirtualHost *:12322>
SSLEngine on
ServerAdmin webmaster@localhost
DocumentRoot /usr/share/adminer/adminer
Alias /adminer/static /usr/share/adminer/adminer/static
Alias /externals /usr/share/adminer/externals
Alias /editor /usr/share/adminer/editor
</VirtualHost>

<Directory /usr/share/adminer/adminer>
Options FollowSymLinks
DirectoryIndex tkl-index.php

<IfModule mod_php5.c>
AddType application/x-httpd-php .php

php_flag magic_quotes_gpc Off
php_flag track_vars On
php_flag register_globals Off
php_value include_path .
</IfModule>
</Directory>

<Directory /usr/share/adminer/editor>
Options FollowSymLinks
DirectoryIndex index.php

<IfModule mod_php5.c>
AddType application/x-httpd-php .php

php_flag magic_quotes_gpc Off
php_flag track_vars On
php_flag register_globals Off
php_value include_path .
</IfModule>
</Directory>

Zoneminder.conf

ServerName localhost

ScriptAlias /zm/cgi-bin "/usr/lib/zoneminder/cgi-bin"

<Directory "/usr/lib/zoneminder/cgi-bin">
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
AllowOverride All
Require all granted
</Directory>

Alias /zm/cache /var/cache/zoneminder/cache
Alias /zm /usr/share/zoneminder/www

<Directory /usr/share/zoneminder/www>
php_flag register_globals off
Options Indexes FollowSymLinks
<IfModule mod_dir.c>
DirectoryIndex index.php
</IfModule>
</Directory>

<Directory /usr/share/zoneminder/www/api>
AllowOverride All
</Directory>

<Directory /var/cache/zoneminder/cache>
Require all granted
</Directory>
User avatar
Bluemax
Posts: 121
Joined: Wed Jun 12, 2019 5:15 pm

Re: ZoneMinder LXC Container API Problem

Post by Bluemax »

poohbah wrote: Wed Nov 25, 2020 11:43 am The container system is Proxmox built on top of Debian Buster.
What OS did you choose "inside" Proxmox/LXC?
LXC is a container. It needs an OS that in the end provides the Zoneminder package. You might have catched an old or buggy version. Official Ubuntu should be fine.
poohbah
Posts: 6
Joined: Sun Nov 15, 2020 10:11 pm

Re: ZoneMinder LXC Container API Problem

Post by poohbah »

I downloaded the container from Turnkey Linux.
User avatar
Bluemax
Posts: 121
Joined: Wed Jun 12, 2019 5:15 pm

Re: ZoneMinder LXC Container API Problem

Post by Bluemax »

i think your webroot filestructure might be identical to the official one. Try this as Zoneminder.conf:
https://github.com/ZoneMinder/zoneminde ... inder.conf
poohbah
Posts: 6
Joined: Sun Nov 15, 2020 10:11 pm

Re: ZoneMinder LXC Container API Problem

Post by poohbah »

Thanks Bluemax. That was the problem. I replaced the contents of the Zoneminder config file Everything is working well and the wife is happy!
Post Reply