-
Notifications
You must be signed in to change notification settings - Fork 323
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
I always get rstp input error #144
Comments
I use proxmox with VM and home assistant, in this case what port range do you have open? I only read about the 8554 and 8555. Thanks |
I've opened only the UDP, in large range... Because I saw that the UDP ports used changes randomly. |
well yes it's a solution but opening all those ports is not healthy .... for rtsp with Webrtc it says to listen to traffic on 8555 but anyway I get the same problems |
That's for TCP, the other user is referring to udp ports. |
sorry then I didn't understand what I should do, now on my Fritz I opened port 8555 in udp. which ones should I open and which range? |
In the future, it is better to attach logs as text, not as pictures. No need to change anything for the already attached logs. |
I hope problem fixed in https://github.com/AlexxIT/go2rtc/releases/tag/v0.1-rc.7 |
thank you very much, the problem seems solved, I have no more errors, I will test until tomorrow. if everything is fine, I close the problem. thanks a lot again |
good morning guys and happy new year, i'm using webrtc and go2 rtc at the latest versions but i'm always getting this error, and i can't get out of it, i'm new but i would like to understand, i'm using three rtsp streams but i keep getting error like in the pictures following and I would like to understand what I'm doing wrong, if I activate the watchdog it continues to work even if the component crashes. thank you all so much for being available
![error_go2rtc](https://user-images.githubusercontent.com/62015384/210344608-29985399-17c9-4189-baf5-dbd224df4f52.png)
The text was updated successfully, but these errors were encountered: