Replies: 3 comments
-
|
Do you have a log showing the messages when you try to open the page? (At the debug level) |
Beta Was this translation helpful? Give feedback.
-
|
I figured out the problem. The older version of motionplus I was running required a full path name for the motion.html file specified in the webcontrol_html entry in the .conf file. The newer version of motion has a new directory in the /usr/local/var/lib/motion called webcontrol. The .conf file now requires only that the file name be specified and that file resides in the webcontrol directory. At least, that is the only way I could get it to work. Also, the configuration documentation on the motion web page still states that full path is required. |
Beta Was this translation helpful? Give feedback.
-
|
Got it. Yea, I put it so that the web control would not provide any page/file outside of the webcontrol subdirectory as a security measure. Only the git version of the documentation mentions it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am running 2 RPi4's with motion installed on Bookworm. Both Pi's were working well until I upgraded the OS. The main problem I am having is that the webcontrol_html setting in motion.conf doesn't work anymore. I use the webcontrol page to display both cameras on the same display when I load the it on my phone or computer
On Pi#1, I did a new complete install from scratch 5 days ago. Everything seemed to work OK except that I could not access the html page on that Pi anymore when it is declared in the motion.conf file. I used the same .conf files with no mods for the new install and the instructions under the V5.0 part of the motion web page.
Since the web page was not a top of the line issue for me I went ahead with upgrading the second Pi. First I upgraded with upgrade/update to see if that made any difference. Not only did the webpage access disappear but motion detection also stopped working. I finally gave up chasing the cause and did a new install the same as above. After the install, I got motion detection back but the webpage access did not work. Again, same configuration with the .conf files.
In my motion.conf file I have
webcontrol_port 8085
webcontrol_localhost off
webcontrol_parms 2
webcontrol_interface user
webcontrol_html /home/pi/Programs/motion.html
The way I have been accessing the webpage for this config is;
http://192.168.1.25:8085
It worked before the upgrades but now I get;
Bad Request
The server did not understand your request.
I'm not sure what to try at this point. Any help is appreciated.
Beta Was this translation helpful? Give feedback.
All reactions