ax77

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.

Can you elaborate? I don't see that build on community apps

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.

I'm still looking for a solution to this

6.11.0 has been released. Won't have time to test it for a couple of days

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

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 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.

did you check your proxy conf?

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.

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?

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.

@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

@jackiewu yes that's what I did