[Support] spaceinvaderone - Shinobi Pro

[Derek_]

On 3/22/2022 at 11:08 AM, b0m541 said:

The folks on the Shinobi Discord server told me to try dashboard-v3 to solve my problem with recordings (just a copy of input stream) freezing several times for some seconds. Is there a version of this container with dashboard-v3? Or is there a chance it can be in the near future?

 

I had the freezing/lost frames in my recordings on my camera with a microphone. I set the audio codec to `aac` and it fixed it For memory, `no audio` also fixed it.

It took me a while to figure it out because i kept trying different audio settings in the "Stream" section. I forgot entirely about the "Recorder" section of the settings

Edited July 12, 2022 by Derek_

[damnshaneisthatu]

18 hours ago, Derek_ said:

@damnshaneisthatu I don't think it shows until/unless you select "Watch Only" in the Identity section.

Still the same after changing it.

[Derek_]

19 hours ago, damnshaneisthatu said:

Still the same after changing it.

 

Did you change the settings from 'simple' to 'advanced'? (near the save button).

[Arbadacarba]

Had a problem and found a solution, and thought it would be useful to post here:

 

I have Shinobi running in Spaceinvaderone's docker and it works great. I have 4 cameras with one acting as a driveway camera and one as a baby cam. My wife and I occasionally want to bring up one of those in a hurry.

 

I really like the "Pop" out view that opens a browser window and just displays that single stream.

 

I tried creating a shortcut in Heimdall with the address from the "Pop" out windows, but discovered quickly that one of the components of the shortcut changes periodically.

 

http://192.168.0.10:8080/md0vACTM78E2ZCIDhWsFX5XZVW2ZzD/embed/Xvjuafz1pM/xYaDpX8fAP/fullscreen%7Cjquery%7Crelative%7Cgui (Numbers Scrambled)

 

Tried Searching and found practically nothing other than one person saying they had figured it out... (but no details)

And of course the Shinobi manual: https://shinobi.video/docs/api

 

But after I figured it out I thought I would share it...

 

First Step is to create an API Key:

 

Down Arrow top left corner - API </>

 

Flip all the switches to NO except View Streams - Enter 0.0.0.0 in allowed IP's field. (I would prefer to restrict the IP's to machines inside my ip range, and I seem to have luck with that by putting my router's address here... But to be honest I don't understand why that should work)

 

Click Add

 

Copy the Key that is created and insert it into the address:

http://192.168.0.10:8080/[HERE]/embed/Xvjuafz1pM/xYaDpX8fAP/fullscreen%7Cjquery%7Crelative%7Cgui

 

And now you have a working URL for the camera...

 

I do find I have to flip the switch in the bottom left corner occasionally (again no idea why)

 

Hope someone finds this useful

[ecahbra]

I just installed on unraid and used a second ethernet port as my camera connection. It is network 192.168.5.0 and my unraid is on the first ethernet on the 192.168.0.0 network. When I try to open the shinobi webgui I am not able to. I get 192.168.0.10 took too long to respond. What am I missing?

[snowmirage]

I'm attempting to setup this container and I am getting the error when logging in to the /super page about the database not being setup, as mentioned in the first page of this thread.

However I can't execute the commands to setup the database it lists

when I am in the console of the container

/opt/shinobi # mysql
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
/opt/shinobi # 

Anyone find a way around this?

From what I've read the DB is setup by default to not allow password less root login.  Do we know what database user / password this container is configured with?

[Blairwin]

On 8/8/2022 at 8:47 PM, snowmirage said:

I'm attempting to setup this container and I am getting the error when logging in to the /super page about the database not being setup, as mentioned in the first page of this thread.

However I can't execute the commands to setup the database it lists

when I am in the console of the container

/opt/shinobi # mysql
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
/opt/shinobi # 

Anyone find a way around this?

From what I've read the DB is setup by default to not allow password less root login.  Do we know what database user / password this container is configured with?

 

If you go to your container settings you'll see that the variable MYSQL_ROOT_PASSWORD is blank.  Add a password to this variable and you should be able to execute the commands.

[eaglephantom]

I was previously able to access my ShinobiPro instance via swag but now I'm getting 502 bad gateway errors. I'm still able to access other containers (such as Nextcloud) via swag. I didn't make any changes other than reinstalling Shinobi with the same settings as before, same VLAN and all of that. I also have the "custom networks" setting turned on in the Docker settings. I looked over the config for it in swag and everything looks good. Is anyone else having this issue recently?

[ax77]

On 8/21/2022 at 4:54 PM, eaglephantom said:

I was previously able to access my ShinobiPro instance via swag but now I'm getting 502 bad gateway errors. I'm still able to access other containers (such as Nextcloud) via swag. I didn't make any changes other than reinstalling Shinobi with the same settings as before, same VLAN and all of that. I also have the "custom networks" setting turned on in the Docker settings. I looked over the config for it in swag and everything looks good. Is anyone else having this issue recently?

 

I've had that problem before.  Go into Docker settings and disable "custom networks" restart docker then shut it down and re-enable custom networks.  That brings it back for me every time.  Not sure why it happens but seems to happen sometimes after a server reboot.

 

On another note I'm still dealing with shinobi not purging old recordings and filling up my drive.  I'm getting tired of manually deleting them.  No one else seeing this?  

[Fefepaille]

(Solved)

 

Hello,

 

First of all, thank you for your work, containers, and videos. You are pimping my Unraid Server!

 

I just installed shinobipro, successfully connected my camera, and it records when shinobi detects motion.

I am trying to get notifications on email / discord, but something's wrong.

 

I can receive the "no-motion" emails, so the config seems to be ok, but when something is detected, shinobi records this, without sending me an email. 

 

Is there a trick ?

 

Thanks again.

 

EDIT : I did it ! Reinstalling the whole container solved my issue. 

Maybe the region were too small for the detection. 

Edited August 26, 2022 by Fefepaille
Solved

[eaglephantom]

On 8/23/2022 at 12:25 PM, ax77 said:

 

I've had that problem before.  Go into Docker settings and disable "custom networks" restart docker then shut it down and re-enable custom networks.  That brings it back for me every time.  Not sure why it happens but seems to happen sometimes after a server reboot.

 

On another note I'm still dealing with shinobi not purging old recordings and filling up my drive.  I'm getting tired of manually deleting them.  No one else seeing this?  

Thanks for your response. I tried that out and it didn't work, unfortunately. After doing what you said I also restarted both swag and shinobipro and it's still not working. I'm getting a bunch of this in the error.log within /mnt/user/appdata/swag/log/nginx:

 

2022/08/27 18:37:15 [error] 305#305: *183 connect() failed (110: Operation timed out) while connecting to upstream, client: 192.168.1.1,

 

I cut off the rest but that 192.168.1.1 is my router, so I'm wondering if the issue is there but I have the vlan set up properly... I'm not sure what would've changed. I looked in syslog for my router and didn't see anything that stands out.

[kulezero]

8 hours ago, eaglephantom said:

Thanks for your response. I tried that out and it didn't work, unfortunately. After doing what you said I also restarted both swag and shinobipro and it's still not working. I'm getting a bunch of this in the error.log within /mnt/user/appdata/swag/log/nginx:

 

2022/08/27 18:37:15 [error] 305#305: *183 connect() failed (110: Operation timed out) while connecting to upstream, client: 192.168.1.1,

 

I cut off the rest but that 192.168.1.1 is my router, so I'm wondering if the issue is there but I have the vlan set up properly... I'm not sure what would've changed. I looked in syslog for my router and didn't see anything that stands out.

I am having the exact same problem with my shinobi install.  Everything is working perfect except for the reverse proxy part.  I checked the error log in nginx and its the same error you are getting.  Hopefully someone with some knowledge on this will see it.

[eaglephantom]

On 8/28/2022 at 7:32 PM, kulezero said:

I am having the exact same problem with my shinobi install.  Everything is working perfect except for the reverse proxy part.  I checked the error log in nginx and its the same error you are getting.  Hopefully someone with some knowledge on this will see it.

And I'm assuming you tried ax77's solution and it didn't work? I had a glimmer of hope when I saw his post

[ax77]

On 8/28/2022 at 7:43 AM, eaglephantom said:

Thanks for your response. I tried that out and it didn't work, unfortunately. After doing what you said I also restarted both swag and shinobipro and it's still not working. I'm getting a bunch of this in the error.log within /mnt/user/appdata/swag/log/nginx:

 

2022/08/27 18:37:15 [error] 305#305: *183 connect() failed (110: Operation timed out) while connecting to upstream, client: 192.168.1.1,

 

I cut off the rest but that 192.168.1.1 is my router, so I'm wondering if the issue is there but I have the vlan set up properly... I'm not sure what would've changed. I looked in syslog for my router and didn't see anything that stands out.

 

did your IP address change? do you have swag pointed to a dynamic dns provider for shinobi? 502 bad gateway means theres no connection made.

[kulezero]

On 8/29/2022 at 9:51 PM, eaglephantom said:

And I'm assuming you tried ax77's solution and it didn't work? I had a glimmer of hope when I saw his post

Nope didn't work either.

[eaglephantom]

11 hours ago, ax77 said:

 

did your IP address change? do you have swag pointed to a dynamic dns provider for shinobi? 502 bad gateway means theres no connection made.

It didn't change, but I have the cname setup in cloudflare to point to my duckdns domain. I went and checked just now and duckdns has my current address.

[jcarmi04]

I am having issues in which the (unassigned devices) drive that my camera's write to borks. It reads as 0 available across the board and is not available as a share. I can Unmount it, cycle Shinobi, then after a few minutes remount and it works - or can reboot the server.

 

To test, I have left Shinobi off and the drive on and have not had any issues.

 

Thoughts? I can't quite tell if this is a MariaDB issue, Shinobi, or ?

 

 

log.txt

[ax77]

On 8/31/2022 at 7:58 PM, eaglephantom said:

It didn't change, but I have the cname setup in cloudflare to point to my duckdns domain. I went and checked just now and duckdns has my current address.

did you check your proxy conf?

[eaglephantom]

19 hours ago, ax77 said:

did you check your proxy conf?

Sorry but, check for what?

[ax77]

On 9/16/2022 at 12:28 PM, eaglephantom said:

Sorry but, check for what?

@eaglephantom What unraid version are you running?

 

I just upgraded from 6.9.2 to 6.10.3 and now my shinobi reverse proxy doesn't work.  All other reverse proxies work.  I restored version 6.9.2 and the shinobi reverse proxy works again.  Try restoring your previous OS.  I'm not sure what about the new version is causing this but at least we're getting somewhere.  Let me know.

[eaglephantom]

On 9/18/2022 at 10:59 AM, ax77 said:

@eaglephantom What unraid version are you running?

 

I just upgraded from 6.9.2 to 6.10.3 and now my shinobi reverse proxy doesn't work.  All other reverse proxies work.  I restored version 6.9.2 and the shinobi reverse proxy works again.  Try restoring your previous OS.  I'm not sure what about the new version is causing this but at least we're getting somewhere.  Let me know.

Ah dang... I really don't want to have to revert back to 6.9.2 (is that even easy to do?)

I wonder if Ed has already identified the issue.

[ax77]

24 minutes ago, eaglephantom said:

Ah dang... I really don't want to have to revert back to 6.9.2 (is that even easy to do?)

I wonder if Ed has already identified the issue.

yeah there's a restore option in Update OS.  What version are you on?  I haven't been able to find anyone reporting this issue

[eaglephantom]

1 hour ago, ax77 said:

yeah there's a restore option in Update OS.  What version are you on?  I haven't been able to find anyone reporting this issue

I'm on 6.10.3

[ax77]

15 hours ago, eaglephantom said:

I'm on 6.10.3

 

do you remember if it stopped working around the time you upgraded?

[eaglephantom]

5 hours ago, ax77 said:

 

do you remember if it stopped working around the time you upgraded?

I'm not sure. I can only revert back to 6.10.2, but I want to say the problem happened either with that upgrade or prior. I can try reverting to 6.10.2 and see if it works.