-
Notifications
You must be signed in to change notification settings - Fork 152
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
Cannot connect to RTSP via VLC nor Synology Surveillance Station #335
Comments
Have you tried with out the basic auth. So remove the users and the permitted user bit? |
If you want to keep using basic auth please make sure your url is of the form:
|
I have attempted to connect via VLC using
Synology sat at |
I see then we will need more debug information. Could you please and the environment variable |
Something to do with the rtsp server? I installed Gstreamer (outside of docker which I think is the correct/only way to do it) But after going back and looking through, I didn't do anything specific for a server. Is that not included in the following instruction? Windows/Linux On Ubuntu/Debian machines gstreamer can be installed with:
|
This error: |
I doubt 2 instances are running as I only have one in portainer and earlier today I restarted the server for unrelated reasons. That would have terminated everything. I did adjust the port so in docker it's still Lastly, I updated the bind address in the Have I changed the wrong setting accidentally? |
Played with a few more settings with no further success. Currently bound to host IP and docker is on host network. Back to port 8554. Did ffprobe and got the following
The Checked the GST Debug and it says
|
Can I ask about your docker configuration. You say Your ffprobe seems to be successful so at least we have a connection at this point and neolink is working. The question is why is VLC (which I presume is on another machine) not getting any connection? This seems to be a network/firewall/port forward issue. Unless you can show me a neolink log with VLC connection being picked up. |
I'm just reporting what the error message means. It may be that the port wasn't closed by the docker instance.
Only need router port forwarding if your trying to access from outside your home network. In this case you might find it easier to set up a home assistant to handle the streams. You'll also need to change the port that is being exposed in docker and the one in the toml.
Usually best to set the bind in the toml to be bind = "0.0.0.0"
bind_port = 8554
Not sure maybe you could post the whole thing again with your latest test |
VLC is being used on a different device, that is correct. Same network though. Okay so port forwarding is irrelevant as my intention is to put the camera through my NAS which I'll have external access to. If I bind to 0.0.0.0, does that mean it doesn't bind? Or it binds to anything? Currently my toml reads as
My compose yml looks like
Recreating the container gives
And attempting to connect to
I really appreciate you taking the time out to assist with this issue. |
Attempting to view the rtsp stream on VLC on the host machine outputs this.
|
|
Have you tried changing your name in the toml to lower case? |
I adjusted the bind and removed the capital letter (but I have been careful to be case sensitive) and we have some new information!
|
That seems to be a working connection form the logs. Anything being displayed? |
No, VLC still pops up with the error thing saying unable to open MRL check the logs (which for some reason are no longer being created???) |
Oh wait I missed that last line. When reading on mobile it still says missing |
I was case sensitive and entered
|
Seems like something is stripping the case along the way. Can you confirm that ffplay/ffprobe works from the same machine as vlc |
SSH via PuTTy > ffprobe
|
Wait why ssh? I mean on the local machine that vlc is on? If you ssh into another box/virtual box it invalidates the test I wanted to achieve |
Since I made this comment
I've been using VLC on the host machine. So I SSH'd into it to run the probe so i can copy paste easier into this thread. |
Apologies if I misunderstood. Jumping onto the host machine directly shows a few errors before the same output as above. The errors are |
Oh but ffplay works! |
Ok just time stamp issues thats fine, they are usually just coming from dropped packets. |
Yeah this seems to be something not being happy between gstreamer and VLC both of which external parts to neolink |
What would you like me attempt to troubleshoot for this? I've gotten this far from understanding as much as I can about the instructions and googling the issues but I feel more than this will require a bit more patience if I don't get it. I'm obviously not very bright with linux. Alternatively, I don't care about not seeing it in VLC - if I can get it working in Surveillance Station that's what I'm after. |
Also interestingly, I can't get ffplay to work via ssh. |
ffplay over ssh probably won't work without x11 forwarding to send the window it makes back to the client. |
Over ssh just make sure ffprobe works |
Okay that makes sense. |
Can you try this build |
It allows for all lower case path connections |
|
I'm having the same issue with an Argus 2E |
I'm trying to get an Argus2E at the moment to test this actually. Just having trouble finding it in my country. Might have to shop from abroad |
Can I downgrade the firmware on my E1 to a version that has been tested? |
I think you can actually, I don't believe they have any checks on versions or anything for the firmware what is uploaded. What is your current E1 firmware? I've got an E1 camera so I could update mine to match and test it |
Reolink camera model and firmware: Reolink E1 - firmware version v3.0.0.400_21062500 |
I have the same/similar issue to #287
Neolink running in Docker on Linux server internal IP of 192.168.0.xxx. I can access all other software on this IP with the relevant ports, no issue.
Neolink terminal states
So clearly my username/password is correct.
Synology won't authenticate the camera when adding to Surveillance station.
Using VLC to open
rtsp://192.168.0.xxx:8554/Camera_Name
results in the following;To Reproduce
Steps to reproduce the behavior. Example:
CMD
/usr/local/bin/neolink rtsp --config /etc/neolink.toml
3.1. Navigate to add IP camera in Synology Surveilance Station and enter a user defined camera with rtsp address of:
rtsp://192.168.0.xxx:8554/Camera_Name
3.2 Open VLC on Windows computer and open a network stream using the same address as in 3.1.
Versions
NVR software: Synology Surveillance Station
Neolink software: Neolink 0.4.0 (Docker image)
Reolink camera model and firmware: Reolink E1 - firmware version v3.0.0.400_21062500
The text was updated successfully, but these errors were encountered: