-
-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login Auth Sucess but api failed Issue #552
Comments
|
I'm running zmNinja in the same server that is running ZM, but i tried to use zmNinja in another PC (with the ip adress) and it shows the same issue (api failed) |
Can you please paste a screenshot of the settings (with IP) |
if possible, you might want to log into irc.freenode.net channel #zoneminder - I am there -we can chat real time to debug and resolve. |
i'm there as vini |
@pliablepixels Thanks a lot!! |
No problem, closing. |
What was the solution to this? |
I don't remember. @vinizanini do you recall what we did on IRC? |
Hi guys i think that was a problem in path to cgi-bin i was using http://serverIP/zm/cgi-bin and the correct adress is http://serverIP/cgi-bin, when @pliablepixels changed the adress it works fine, i hope it helped you. |
@Gorfy00 Check it in Zoneminder>Settings |
@vinizanini I can confirm that this worked for me also. |
Hello Guys,
i'm trying to use zmninja but it shows login sucess but api failed, zmNinja is running in the same machine that Zoneminder, and zoneminder works fine, i'm using Debian 9,
when i go to
127.0.0.1/zm/api - Error: The requested address '/zm/api/' was not found on this server
but when i access http://127.0.01/zm/api/monitors.json - It shows {"monitors"{"Monitor":"Id":"1","Name":"Monitor-1","ServerId":"0","Type":"Ffmpeg","Function":"Monitor","Enabled":"1","LinkedMonitors":"","Triggers...
and when i go to - http://localhost/zm/api/host/getVersion.json - {"version":"1.30.4","apiversion":"1.0"}
I think it's an issue of some permission, but I have no idea where it is, someone can help me
Thanks
The text was updated successfully, but these errors were encountered: