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

Remote end closed connection without response #122

Open
matheusvellone opened this issue Feb 25, 2024 · 5 comments
Open

Remote end closed connection without response #122

matheusvellone opened this issue Feb 25, 2024 · 5 comments

Comments

@matheusvellone
Copy link

I'm using this gist to test ONVIF support for my camera to add it to Frigate.

I've looked inside the request in Wireshark to check if there was something different being sent from the script comparing it to Onvif Device Manager, which is able to successfully control the camera, but I could not spot anything different between them

Here is a successfull request made by Onvif Device Manager. Could not replicate a GetConfigurations request on ODM
image

And here a request made by the script
image

Also, on OnvifCamera constructor there is a GetCapabilities call which responds successully, which makes me think everything is setup correctly, and maybe the problem is on my camera
image

My camera is a cheap and generic bulb camera.

I'm not very used to Python and WSDL, so this might be a dumb thing I'm missing

I also tried the #91 changes too, but it results in the same error anyway, although the CreatePullPointSubscription endpoint also receive no response too.

@PveOnly
Copy link

PveOnly commented May 1, 2024

Hi, were you able to fix this ? I have the same problem :/

@matheusvellone
Copy link
Author

Hi, were you able to fix this ? I have the same problem :/

No 😢

@matheusvellone
Copy link
Author

@FalkTannhaeuser sorry for the ping.
Is there any light you can cast on this to make progress?

@PveOnly
Copy link

PveOnly commented Sep 26, 2024

Hey, so in my case I was able to fix it, it was because I was using the wrong port which was not the ONVIF one. For some reason my ONVIF was not set on port 80 but on 8080.
Maybe you can try to brute force the connection with common HTTP port :
[80, 8000, 8080, 8899, 5000, 443]

@matheusvellone
Copy link
Author

matheusvellone commented Sep 26, 2024

Tried them, but no luck with any 😕

All returned a Connection refused error, only the 5000 one do something different.
Also, I intercepted some network packets from OnvifDeviceManager to the camera. The software is able to correctly PTZ the camera on port 5000.

Being a cheap and generic camera, maybe the manufacturer didn't implement onvif protocol entirely. But since another piece os software could communicate with it, i feel like something is slightly misconfigured on the WSDLs

(nice you could get yours working 🎉)

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