Well.. I've tried rpaf (did nothing) remoteip (did nothing) and changing the log format string for apache (works for apache but not web_php.log)
Still all I can get in the web_php.log is the proxy IP. I don't have huge amounts of time to put in to this so I'll have to shelve it for a while.
Search found 55 matches
- Tue Aug 09, 2022 5:53 pm
- Forum: ZoneMinder 1.36.x
- Topic: web_php.log + Fail2Ban + reverse proxy
- Replies: 10
- Views: 6175
- Tue Aug 09, 2022 12:56 pm
- Forum: ZoneMinder 1.36.x
- Topic: web_php.log + Fail2Ban + reverse proxy
- Replies: 10
- Views: 6175
- Mon Aug 08, 2022 10:11 pm
- Forum: ZoneMinder 1.36.x
- Topic: web_php.log + Fail2Ban + reverse proxy
- Replies: 10
- Views: 6175
Re: web_php.log + Fail2Ban + reverse proxy
Interesting, the option names are not quite the same in my version, plus there is this:
This module should be considered as deprecated after Jessie.
This module should be considered as deprecated after Jessie.
- Mon Aug 08, 2022 7:13 pm
- Forum: ZoneMinder 1.36.x
- Topic: web_php.log + Fail2Ban + reverse proxy
- Replies: 10
- Views: 6175
Re: web_php.log + Fail2Ban + reverse proxy
I use mod_rpaf on a few PHP-based sites hosted behind reverse proxies and they all see the correct remote address. Could you tell me how you set this up? I have this module installed and set RPAF_ProxyIPs with the IP address of the proxy, but still only the proxy is being logged and not the X ...
- Wed Apr 13, 2022 4:04 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
- Wed Apr 13, 2022 3:45 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
- Wed Apr 13, 2022 3:41 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Must be something in the web server group that conflicts. Works better with a minimal install. How does one restore the database? # mysql zm < /home/zmuser/zm.sql ERROR 1005 (HY000) at line 232: Can't create table `zm`.`Events` (errno: 150 "Foreign key constraint is incorrectly formed")
- Mon Apr 11, 2022 6:46 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Built another VM and followed https://wiki.zoneminder.com/Debian_11_Bullseye_with_Zoneminder_1.36.x Error right out of the box. Job for zoneminder.service failed because the control process exited with error code. See "systemctl status zoneminder.service" and "journalctl -xe" for details ...
- Mon Apr 11, 2022 5:40 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Debian 11.3 on Xen. Everything was installed from zmrepo.
I may try the rebuild approach.
I may try the rebuild approach.
- Thu Apr 07, 2022 6:33 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Checked RTSP stream with ffplay & VLC, works fine. Tried ffmpeg source type as noted in changelog, made no difference ZM still shows a black window with "unable to stream" or occasionally a garbled video frame. Still getting "[Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc ...
- Wed Apr 06, 2022 6:31 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Tried the upgrade again, doing one step at a time with snapshots. After running zmupdate (successfully!) I have buckets of errors and no picture 04/06/2022 14:28:57.376506 zmtrigger[1516].ERR [ZoneMinder::Memory::Mapped:90] [Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc ...
- Fri Apr 01, 2022 7:31 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
Re: Upgrade from 1.34 to 1.36 on Debian broke ZM
Well I'm restoring this machine from backup. ZoneMinder updates are a cluster****
- Fri Mar 25, 2022 5:39 pm
- Forum: ZoneMinder 1.36.x
- Topic: Upgrade from 1.34 to 1.36 on Debian broke ZM
- Replies: 17
- Views: 3041
Upgrade from 1.34 to 1.36 on Debian broke ZM
Not really sure where to start. Upgraded from 1.34 to 1.36 using apt. Database upgrade went fine. Have no picture after the upgrade. zmwatch is continually restarting zmc. I have errors like: Memory map file '/dev/shm/zm.mmap.1' does not exist in zmMemAttach. zmc might not be running. No RTSP ...
- Fri Mar 25, 2022 5:35 pm
- Forum: ZoneMinder 1.34.x
- Topic: [SOLVED] "Unable to connect to ZM db"
- Replies: 3
- Views: 6349
Re: [SOLVED] "Unable to connect to ZM db"
apt remove php7.0-cli php7.0-common php7.0-gd php7.0-json php7.0-opcache php7.0-readline php7.0-xml php7.0 libapache2-mod-php7.0
- Wed Jul 29, 2020 1:54 pm
- Forum: ZoneMinder 1.34.x
- Topic: [SOLVED] "Unable to connect to ZM db"
- Replies: 3
- Views: 6349
[SOLVED] Re: "Unable to connect to ZM db"
Found the problem. libapache2-mod-php7.3 was missing. Somehow pieces of php7.0 were hanging around even tho it wasn't installed, zoneminder was trying to use those instead.