December 11, 20223 yr Was somebody successfull installing the latest version 22.12.5 of Xeoma?? I'm still on version 22.3.16....
December 13, 20223 yr 12 hours ago, Alex24 said: Ja, läuft bei mir ohne Probleme. @Alex24 welchen Docker Container verwendest du, hattest du mit Version 22.8.16 auch die Probleme wie hier im Thread beschrieben? Which docker container are you using? Did you have similar problems with version 22.8.16 as discribed in this thread?
December 13, 20223 yr Docker Version 20.10.21. Ich hatte probleme mit der Xeoma Version 22.8.16 in dem dass mein RAM innerhalb kürzester Zeit überlief und das ganze zum absturz gebracht hat. Mit der 22.12.15 läuft es wieder normal.
December 14, 20223 yr Hello , I have a problem, I'm installed Xeoma on default settings, but I cannot start application. Just press start, a few second later its still stopped any idea , how to fix this ?
December 18, 20223 yr Hallo @Alex24, ich meinte welchen Docker Container du von hub.docker.com installiert hast. Ich verwende https://hub.docker.com/r/coppit/xeoma/ und hatte die von mir hier im beschriebenen Probleme: Hello @Alex24, I ment wich container you are using from hub.docker.com. I installed https://hub.docker.com/r/coppit/xeoma/ and had following problems: On 9/29/2022 at 10:42 PM, vakilando said: Same here... I tried updating to the latest version 22.8.16: manually downloaded the latest version 22.8.16 (xeoma_linux64.tgz) from felenasoft renamed xeoma_linux64.tgz to xeoma_22.8.16.tgz put it in the xeoma download directory (/mnt/cache/appdata/Xeoma/downloads) changed the config file xeoma.conf by adding: VERSION='22.8.16' When starting the container it stucks at: Sep 29 20:09:44 5b7e2d0c1c9d syslog-ng[13]: syslog-ng starting up; version='3.13.2' Configuration: PASSWORD=<hidden> VERSION=22.8.16 [Sep 29 08:09:47 PM] Setting the password Reverting to version 22.3.16 and everything is fine.... Did somebody find a way to get it up and running, perhaps by manually setting the password? Ich werde die Tage mal Version 22.12.15 testen.
December 18, 20223 yr @Maniek2as2 can you show us your logs and your configuration? If you use this container, did you follow the instructions from here https://github.com/coppit/docker-xeoma-server: "When run for the first time, a file named xeoma.conf will be created in the config dir, and the container will exit. Edit this file, setting the client password." Edited December 19, 20223 yr by vakilando more information for help
December 19, 20223 yr @Alex24 version 22.12.5 is working for me - partially... The docker starts up, I can connect to the xeoma server with the linux client software an I see the cameras with pictures. The xeoma web server also starts successfully but I can't login with my admin account. It says wrong password although it isn't wrong! I can login with my second account, but the camera prictures are just black....
December 19, 20223 yr 18 hours ago, vakilando said: Hallo @Alex24, ich meinte welchen Docker Container du von hub.docker.com installiert hast. Ich verwende https://hub.docker.com/r/coppit/xeoma/ und hatte die von mir hier im beschriebenen Probleme: Hello @Alex24, I ment wich container you are using from hub.docker.com. I installed https://hub.docker.com/r/coppit/xeoma/ and had following problems: Ich werde die Tage mal Version 22.12.15 testen. I was do this now, but after run docker still i have a problem , i was check log : *** /etc/my_init.d/30_parse_config_file.sh failed with status 3 *** Killing all processes... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/10_syslog-ng.init... *** Running /etc/my_init.d/30_parse_config_file.sh... *** /etc/my_init.d/30_parse_config_file.sh failed with status 3 *** Killing all processes... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/10_syslog-ng.init... *** Running /etc/my_init.d/30_parse_config_file.sh... *** Running /etc/my_init.d/40_install_xeoma.py... 2022-12-19 18:04:49 Determining version of Xeoma to use 2022-12-19 18:04:49 Config version is "latest" 2022-12-19 18:04:49 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version3.xml 2022-12-19 18:04:53 Using Xeoma version 22.12.5 (the latest stable version) 2022-12-19 18:04:53 Deleting files in /config/downloads to reclaim space... 2022-12-19 18:04:53 Downloading from http://felenasoft.com/xeoma/downloads/latest/linux/xeoma_linux64.tgz into /config/downloads 2022-12-19 18:04:53 Downloading from http://felenasoft.com/xeoma/downloads/latest/linux/xeoma_linux64.tgz 2022-12-19 18:04:54 Downloaded to /config/downloads/xeoma_22.12.5.tgz 2022-12-19 18:04:54 Installing Xeoma from /config/downloads/xeoma_22.12.5.tgz 2022-12-19 18:04:55 Installation complete *** Running /etc/my_init.d/50_configure_xeoma.sh... *** Booting runit daemon... *** Runit started as PID 68 /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found *** Shutting down runit daemon (PID 68)... *** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown... *** Init system aborted. *** Killing all processes... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/10_syslog-ng.init... *** Running /etc/my_init.d/30_parse_config_file.sh... *** Running /etc/my_init.d/40_install_xeoma.py... 2022-12-19 18:06:41 Determining version of Xeoma to use 2022-12-19 18:06:41 Config version is "latest" 2022-12-19 18:06:41 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version3.xml 2022-12-19 18:06:41 Using Xeoma version 22.12.5 (the latest stable version) 2022-12-19 18:06:41 Downloaded file /config/downloads/xeoma_22.12.5.tgz already exists. Skipping download 2022-12-19 18:06:41 Skipping installation because the currently installed version is the correct one *** Running /etc/my_init.d/50_configure_xeoma.sh... *** Booting runit daemon... *** Runit started as PID 66 /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found /bin/sh: 1: ip: not found Dec 19 18:03:27 28e3380dd2c6 syslog-ng[14]: syslog-ng shutting down; version='3.13.2' Dec 19 18:03:39 28e3380dd2c6 syslog-ng[13]: syslog-ng starting up; version='3.13.2' Please edit the config file to specify your settings Dec 19 18:03:39 28e3380dd2c6 syslog-ng[13]: syslog-ng shutting down; version='3.13.2' Dec 19 18:04:48 28e3380dd2c6 syslog-ng[13]: syslog-ng starting up; version='3.13.2' Configuration: PASSWORD=<hidden> VERSION=latest [Dec 19 06:04:55 PM] Setting the password Password set successfull [Dec 19 06:04:55 PM] Starting the server in 5 seconds. See the log directory in your config directory for server logs. [Dec 19 06:04:55 PM] Not using archive cache Dec 19 18:04:55 28e3380dd2c6 cron[72]: (CRON) INFO (pidfile fd = 3) Dec 19 18:04:55 28e3380dd2c6 cron[72]: (CRON) INFO (Running @reboot jobs) Dec 19 18:06:14 28e3380dd2c6 syslog-ng[13]: syslog-ng shutting down; version='3.13.2' Core: Starting ... Core: Starting services ... Core: Started. Core: Stopping ... Core: Save settings ... Core: Stopping services ... Core: Stopped. Dec 19 18:06:40 28e3380dd2c6 syslog-ng[13]: syslog-ng starting up; version='3.13.2' Configuration: PASSWORD=<hidden> VERSION=latest [Dec 19 06:06:41 PM] Setting the password Password set successfull Dec 19 18:06:42 28e3380dd2c6 cron[71]: (CRON) INFO (pidfile fd = 3) Dec 19 18:06:42 28e3380dd2c6 cron[71]: (CRON) INFO (Skipping @reboot jobs -- not system startup) [Dec 19 06:06:42 PM] Starting the server in 5 seconds. See the log directory in your config directory for server logs. [Dec 19 06:06:42 PM] Not using archive cache And when I click Webui i have "HTTP error: 404" Edited December 19, 20223 yr by Maniek2as2
December 19, 20223 yr Edited conf file, set password. Got it to start, at least. 404 errors on all attempts to access gui, whether host, bridge, br0, etc. cannot connect.
December 24, 20223 yr On 12/19/2022 at 7:46 PM, tucansam said: 404 errors on all attempts to access gui You are using the administrotor account, right? I have a similar problem with the administrotor account, I don't get a 404 error but a "wrong login/password" message. I can only login with my second non administrative account, but the I have black pictures. Try creating a second non administrative account with the Xeoma client (Linux/Win) and with that try to login to the webinterface.
December 24, 20223 yr On 12/19/2022 at 1:26 AM, vakilando said: @Alex24 version 22.12.5 is working for me - partially... The docker starts up, I can connect to the xeoma server with the linux client software an I see the cameras with pictures. The xeoma web server also starts successfully but I can't login with my admin account. It says wrong password although it isn't wrong! I can login with my second account, but the camera prictures are just black.... I got it working! Solution was quite simple.... (no login) => remove characters from password like: §, $, %, & (black pictures) => I don't know why, but the account for the web server module had a wrong password set
November 1, 20232 yr What is the current state of this container? It appears that @coppit is no longer maintaining it, so has anyone forked it and make any updates? I noticed that Archive Search is no longer functioning, and my Motion Detector is now complaining about not having the a new enough library. My guess is this is a dependency that just needs to be updated in the dockerfile, but I'm not sure.
November 1, 20232 yr I sadly must agree @NewDisplayName.... I had Xeoma up and running for quite a long time. It worked very well and was rock solid too, but the container is no longer maintained by @coppit I have more cameras than my licence admits costs are too high to upgrade I still have the xeoma container installed because I like the drag an drop configuration very much dispite of a quite ugly interface but I'll move on to frigate.
August 31, 2025Aug 31 Author Hi everyone,After many years, I've updated the container. Changes:Fix download URL so that "latest" and "latest_beta" works againUpdate to latest Phusion base image (Ubuntu lite)Change how the config file sets passwords to allow for special charactersAdd the -core option to suppress an X11 warningAllow the user to set the MAC_ADDRESS to a consistent valuePeriodically fix permissions in the config directoryLet me know if there are any other burning feature requests and I'll try to address them.Thanks to the folks who provided pull requests. Edited August 31, 2025Aug 31 by coppit
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.