ax77

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by ax77

  1. Hello, I've updated to 6.12.8 and continue to have this specific issue. Can anyone help or point me in the right direction? I don't want to have to revert to 6.9.2 as I have other issues with it.
  2. Can you elaborate? I don't see that build on community apps
  3. I run a similar setup as @dawhit. Pfsense on vm with Shinobi on vlan. My shinobi.subdomain.conf is correct as his example. Not sure what else is different. I'm currently on 6.9.2 because when I upgraded to 6.10.x my Shinobi reverse proxy stopped working. Reverting got it back up. I haven't tried upgrading to 6.11.5.
  4. 6.11.0 has been released. Won't have time to test it for a couple of days
  5. Hello, I upgraded to 6.10.3 from 6.9.2 and lost reverse proxy access to my shinobi docker. Other reverse proxies (Nextcloud and Emby) work fine. Shinobi uses a custom IP in a vlan. I restored 6.9.2 and it works fine. thanks, tower-diagnostics-20220921-1712.zip
  6. do you remember if it stopped working around the time you upgraded?
  7. 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
  8. @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.
  9. 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.
  10. 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?
  11. I recently migrated from Spaceinvaderone's Shinobi container to selfhosters container. Looks like I traded one set of issues for another. Playing videos before was almost instant to start playing. Now it take over 8 seconds and much longer through reverse proxy. It seems like it's downloading the video before it plays it. I'm not sure if this is the correct place to get support for this.
  12. @RodWorks is setting up that container pretty much the same? On top of the drive issue I just lost access through my reverse proxy and can't figure out why. Other reverse proxies are working fine
  13. @jackiewu yes that's what I did
  14. @JackieWu thanks, but now after inputting ip route add 10.253.0.0/24 via "unraid ip" I'm getting ip: RTNETLINK answers: Network unreachable
  15. @JackieWu when I try and add the static route to my Shinobi container I get the following ip: RTNETLINK answers: Operation not permitted
  16. following these directions will open the port. https://hub.shinobi.video/articles/view/LyCI3yQsUTouSAJ
  17. Could you elaborate on accessing VLANs? I have everything setup for complex networks. I can ping devices on different VLANs but I can't access their web gui's. Not sure what other static route I can add.
  18. awesome. I'll give it a try. Thanks!
  19. I've been running Shinobi for about 2 years without much issues. Today I realized that none of my cameras had any recordings for the past 2 days. Turns out that my dedicated unassigned drive was completely full with recordings back to 2021. The shinobi gui says the drive is only 13% used. Has anyone seen this? any advice on fixing it? It's set to only keep recordings up to 30 days. I had to manually delete recordings. I restarted Shinobi but it's still not purging old recordings.
  20. @jackiewu sorry for the late response. Never got a notice. But to answer your question no I wasn't able to resolve this. Maybe someone else can chime in with ideas. Right now I'm working on a separate unraid/wireguard installation where I want to use the complex network setup but for some reason in this configuration I lose connection to Windows computers on the remote lan. I could reach other devices but not Windows devices. Not sure why. I've disable the Windows firewall with no luck. Setup is the same as my first install, but using PFsense. Correct static route, everything identical. I'm able to reach Windows devices on my first install just fine. When change to Simple network config using NAT on wireguard settings I am able to reach Windows device. Any ideas?
  21. I've set up wireguard for a complex network but I'm unable to access my shinobicctv docker that is on a vlan. The vlan has a subnet of 10.5.20.0/24. I'm able to ping and tracert all ip addresses on the vlan through wireguard but can't access them via webgui. I can access the router at 10.5.20.1 tough. Any ideas?
  22. I've set up wireguard for a complex network but I'm unable to access my shinobicctv docker that is on a vlan. The vlan has a subnet of 10.5.20.0/24. I'm able to ping and tracert all ip addresses on the vlan through wireguard but can't access them via webgui. I can access the router at 10.5.20.1 tough. Any ideas?