Port 443 Binding

Armodon

Hello,

after some struggle with the registration I now be able to add camera feeds and try to connect my cameras to my Echo Show.

There I am again in some struggles.

The .deb files avaiaible are very good, no question but I would like to request an feature that I can choose which interface or IP is binded on my Gateway-Device.

What I can see, the gateway tried to bind *:443 on my Raspberry and is unable to do this due that I have running an Webservice (Apache) on the same RaspberryPi (Model 4) on this Port.
I can understand that Amazon forced that Port but the Interface to be used for that should be choosable, that’s also possible on the most other services around.
So may create and simple .conf file on the already existing /etc/monocle Folder so it is possible to choos that Port 443 should be binded to an specifice IP (On Linux it is easy to add multiple IP’s to one Interface).

May that is an discusable Feature Request.

Now I am going to setup another Pi (old 3B) where the Gateway Service is running on.

Just as an sugestion, no realy issue.

SchmuFoo

@Armodon just for the records, this is possible in the meantime via:

https://monoclecam.com/monocle-gateway/custom-configuration

Monocle

@Armodon ,

@SchmuFoo is right, you can define which IP address the Monocle Gateway uses by overriding the setting via the monocle.properties file. By default Monocle Gateway just auto chooses the first interface it finds.

You would change #rtsp.host=0.0.0.0 to rtsp.host=YOUR_IP_ADDRESS

#--------------------------------------
# RTSP SERVICE PROPERTIES
#--------------------------------------
#rtsp.host=0.0.0.0
#rtsp.port=8555
#rtsp.ssl.port=443

You can technically override the port as well if you were fronting/proxying with some TCP proxy server (… Stunnel, HA Proxy). But in the end the Alexa devices will only connect on port 443.

Thanks, Robert