Sat>IP device not accessible

[Connor]

I guess this might be port related. Which port are you using (554/ 9983)? and how can I set the port to 9983 in general?

Is that the port they're using for RTSP data, or the web admin? They're usually different ports.

At the moment it's hardcoded for 554, but I also haven't come a device using a different port. Does your http://<IP>/rootDescr contain any info that refers to a different port?

These are the ports that are used for RTSP data. The web admin goes to a completely different port.

And for the differing port: That's odd. It might not be a device, but an issue from the Synology implementation, site they are restricting all ports < 1024.

As written in beforehand, in my TVHeadend installation, that log says (while it is not running in a Docker container) "Port 554 restricted for non-root users, using 9983".

[Connor]

I can't see any way to detect the port, but I guess I could make 554 for the default, but let the user override it with SATIP_RTSP_PORT environment variable

If you don't see any other issue from my logs, then I would really appreciate this.

[sub]

Ok, I've added that logic for the next release.

[Connor]

Perfect, thank you. And just as I am curious: for when have you planned the release?

[sub]

FYI, in the meantime, if you're up to trying a bit of sql to force a different port, you could try changing the base_url column in the SATIP_RECORDER table in the npvr.db3 file.

[sub]

Next release will likely be within the next week.

[Connor]

Thank you - I'll be patient until then.

Have a great evening!

[Connor]

First of all: Thank you for publishing the new image and for again sharing your dedication.

Is there anything that I need to specifically do apart from adding the ENV SATIP_RTSP_PORT with the port number?
Unfortunately it is not working, but the scans are still being tried on port 554.

Thank you for your clarification.

[sub]

You would probably have needed to delete the existing device, and restart it with that environment variable set. (the port was set at discovery time)

[Connor]

Thank you for the feedback. I realised my own mistake - which was to reuse the /config/ folder.
Somehow I am not gaining ground on this.

While I was pretty sure that port 9983 for RTSP would solve my issues, it didn't.
Using that port cause log entries showing that port 9983 may not be accessed.
So I switched back to port 554 - but this one is not finding any channels.
Is it already the right moment to break down crying?


Best regards,

Connor