Gymratz found this JSON URL which returns over 90% of plates' data on year, make, model, engine, VIN, single-owner, ever been in repairs, etc.
(Just substitute 'PLATE' for a real plate, and of course 'CA' for a valid state.)
I thought I got a 500 response if it was working properly. Maybe I am not remembering correctly though.
I'm sorry I can't be of more help @tech101 but I'm using the Docker version on Linux and not Windows . It could very well be a Windows firewall issue preventing it. If you are getting a successful webhook test then at least you know that is working properly. Maybe disable Windows firewall totally and try again? I hate Windows which is why I run Linux for just about everything.
you'll get a 500 error from the openalpr webhook page, because it's sending it an invalid payload
you'll get a 405 trying to get to localhost:5000/webhook because it's expecting a POST, not a GET request.
Gymratz found this JSON URL which returns over 90% of plates' data on year, make, model, engine, VIN, single-owner, ever been in repairs, etc.
(Just substitute 'PLATE' for a real plate, and of course 'CA' for a valid state.)
Interesting, could do a comparison between what openalpr thinks the car is and what that site thinks the car is, and if they don't match up by a certain percentage put a big STOLEN CAR FAKE PLATE alert ?
I guess you saw my log earlier that the missing parameters are still causing everything to "bomb out" as you say. I guess it wasn't as easy to fix as thought.
i need to see the actual payload to be certain, i assumed the array of vehicles would be empty, i think the array is not even present when there are no vehicles.
I have added a debug option to the configuration file to dump the webhook payloads to the logs. When you get a failure copy the JSON from the log so I can take a look.
oh, duh, since you are running on windows you have to tell it to not just listen to localhost. in your appsettings add "urls": "http://0.0.0.0:5000" to get it to listen on all interfaces. you only need to do this if you are running the windows build. docker handles this for you.
oh, duh, since you are running on windows you have to tell it to not just listen to localhost. in your appsettings add "urls": "http://0.0.0.0:5000" to get it to listen on all interfaces. you only need to do this if you are running the windows build. docker handles this for you.
I'm viewing a locally hosted website (using grunt serve, if that matters). I can view it via http://localhost:9000/ or http://127.0.0.1:9000/, but not via http://10.0.0.16:9000/. 10.0.0.16 is my l...
Just pulled the new container image and running it now with logging "true". I won't get the errors till tonight more than likely but I'll post them when I do.
Ok, I'm attaching the log file since it s real big. For some reason I'm not getting overlays any longer and I'm not sure why since nothing changed on my end. I'm getting car make/model/color stuff in the OpenALPR dashboard now that its light enough so I know everything is still working there but nothing is being overlayed on the cam.
Ok, I'm attaching the log file since it s real big. For some reason I'm not getting overlays any longer and I'm not sure why since nothing changed on my end. I'm getting car make/model/color stuff in the OpenALPR dashboard now that its light enough so I know everything is still working there but nothing is being overlayed on the cam.