Update MediaMTX #1224
Update MediaMTX #1224
Conversation
Co-authored-by: mrlt8 <mrlt8@users.noreply.github.com>
|
volumes:
Changed '/record/' to '/Record/' and now it is recording ;) [On the 'latest' branche and 'previous build', this won't record at all] HLS Stream is working fine, but WebRTC stream is not working So:
volumes:
..............................................................................................................
volumes:
.............................................................................................................. |
|
@JA16122000 default settings will record to |
|
Unfortunately, the WebRTC stream is not working. HLS is working, though. |
|
@JA16122000 WebRTC should be fixed with the latest changes. Please let me know if your run into any other issues. |
Still not playing with WebRTC docker-compose.yml looks like: services: LOG: 🚀 DOCKER-WYZE-BRIDGE v2.9.9 ARMV7L DEV BUILD [2024-06-24t14:25:28.918z] 357857c
|
|
Noticed that MTX auth: 🚀 DOCKER-WYZE-BRIDGE v2.9.9 ARMV7L DEV BUILD [2024-06-24t14:25:28.918z] 357857c I noticed that 'MTX auth' is not case-sensitive for passwords. (I have capital letters, but in the log they are NOT capital) |
The WebRTC issue with the VPN enabled is indeed only on the 'dev' branch. I suspect it has to do with the newer MTX variant, as it worked with older 'dev' branches with older MTX versions |
|
Could you post some more details about your vpn config so I can replicate the issue? Are you connecting to the bridge over a VPN or is the VPN unrelated to the bridge? |
On my laptop (locally, not on the entire network), I use PIA (Private Internet Access) as a VPN. Addition: On my phone, I use a VPN tunnel so that I can use my home network (no matter where I am). For clarity, my own network is VPN-free. |
|
hmm, so I can kind of replicate the issue by connecting to a commercial VPN service...
|
WebRTC doesn't work with VPNs. No matter which VPN you use. It seems that WebRTC is simply not discoverable from outside the network? |
|
So are you trying to VPN back to your LAN to view the WebRTC or are you routing your traffic via a VPN while on your local network? Chrome seems to be resilient to VPN changes for me on DEV/Latest. |
On my LAN-network, i don't have an VPN (NO VPN Network-wide, only my laptop is localy routing traffic by VPN) PHONE: LAPTOP |
|
Working without VPN. 🚀 DOCKER-WYZE-BRIDGE v2.9.10 ARMV7L DEV BUILD [2024-06-29t13:56:12.963z] 71df0c2
|
|
No changes have been made re: webrtc, so there shouldn't be any difference. potential work around: ports:
- 8189:8189
- 8189:8189/udp
...
environment:
- MTX_WEBRTCLOCALTCPADDRESS=:8189
... |
So: ports: |
|
no, should be: |
Also tried, but doesn't work either |
|
then you should probably open an issue with mediamtx as you seem to be having a different issue. |
|
Where and how do I do that? |
|
This one? |
|
The same as: bluenviron/mediamtx#3522 ?? |
|
No, you already confirmed you have a different issue. |
Update MediaMTX which offers an updated authentication system for streams and recording.
NEW:
STREAM_AUTHoption to specify multiple users and paths:::can be used to specify the allowed IP address for the user.@to specify paths accessible to the user.|as a separatorEXAMPLES:
user:passhas access tocam-1andother-camsecond-user:passwordhas access tojust-one-camuser3:passhas access to all paths/camerasuser:passhas access to all paths/cameras when streaming from 192.168.0.7just-one-camwhen streaming from 192.168.0.15 or from 192.168.0.20user:passhas access to all paths/cameraspublic-camRecording via MediaMTX:
RECORD_PATHAvailable variables are%pathor{cam_name},%Y%m%d%H%M%S%f%s(time in strftime format).RECORD_LENGTHLength of each clip. Usesfor seconds ,hfor hours. Defaults to60sRECORD_KEEPDelete older clips. Usesfor seconds ,hfor hours. Set to 0s to disable automatic deletion. Defaults to0s