Skip to content
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

Errors while connecting through reverse proxy #192

Open
tclayson opened this issue Jan 6, 2025 · 2 comments
Open

Errors while connecting through reverse proxy #192

tclayson opened this issue Jan 6, 2025 · 2 comments

Comments

@tclayson
Copy link

tclayson commented Jan 6, 2025

I am using hass_ingress to show Blue Iris within Home Assistant. Although I don't know exactly how this works, I understand it's a form of reverse proxy.

It works some of the time, and then it stops working. When it stops working the UI3 interface still loads, but it gives the errors:

The video stream was lost. Attempting to reconnect.
Protocol Error: Stream did not start with "blue"

I have no idea how to even start diagnosing the issue with this. Do you know why these errors might be happening? Or how can I diagnose this?

Thanks for any help you can give me.

@bp2008
Copy link
Owner

bp2008 commented Jan 6, 2025

Hi. Try opening the browser's developer tools (ctrl + shift + i), go to the Network tab, and then reload the page. The network tab will show every HTML request that is made. When it stops working, see if you can identify the last request for the video stream (it tends to appear starting with the text "2.0" and the full path of the request is /video/Index/2.0?session=...). Inspect the response body for that request. It is supposed to be a bunch of binary data starting with the word "blue":

Example:

image

But most likely your proxy server is delivering an HTML page instead of whatever Blue Iris actually sent. This is a common issue with proxy servers that make too many assumptions about the content they are proxying. Anyway whatever the response body actually is, it possibly could contain an error message that should shed some light on whatever is going wrong.

@tclayson
Copy link
Author

Hey, I just wanted to say, thanks for getting back to me.

I was hoping I'd see the issue again and be able to come back with an update, but it hasn't happened again since you replied to me! (It will do eventually!)

I assume it's an issue with the way the proxy is set up, but this is helpful for helping to track down the issue, when it next happens!

I appreciate you spending the time to get back to me! Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants