Unknowed brand IPcam
-
okay i have done here the result
root@FhemServer:~# monocle-gateway --restart ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** <<RESTARTING>> THE [MONOCLE-GATEWAY] SERVICE ● monocle-gateway.service - Monocle Gateway Service Loaded: loaded (/etc/systemd/system/monocle-gateway.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2019-08-03 13:51:05 CEST; 53ms ago Main PID: 7948 (monocle-gateway) CGroup: /system.slice/monocle-gateway.service └─7948 /usr/local/bin/monocle-gateway Aug 03 13:51:05 FhemServer systemd[1]: Started Monocle Gateway Service. root@FhemServer:~# monocle-gateway --tail ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** <<TAIL>> LOG FOR THE [MONOCLE-GATEWAY] SERVICE -- Logs begin at Thu 2016-11-03 18:16:43 CET. -- Aug 03 13:46:42 FhemServer monocle-gateway[7849]: - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00) Aug 03 13:46:42 FhemServer monocle-gateway[7849]: - TAGS : @hangup,@proxy-tcp Aug 03 13:46:42 FhemServer monocle-gateway[7849]: ------------------------------------------------- Aug 03 13:46:42 FhemServer monocle-gateway[7849]: 2019-08-03T11:46:42.943Z [INFO] [RTSP PROXY] REGISTERING STREAM [Garten/PRIMARY]; (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) Aug 03 13:46:42 FhemServer monocle-gateway[7849]: 2019-08-03T11:46:42.961Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [REGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp Aug 03 13:46:42 FhemServer monocle-gateway[7849]: 2019-08-03T11:46:42.961Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] { Aug 03 13:46:42 FhemServer monocle-gateway[7849]: "cseq": "1", Aug 03 13:46:42 FhemServer monocle-gateway[7849]: "transport": "reuse_connection=0;preferred_delivery_protocol=interleaved;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63" Aug 03 13:46:42 FhemServer monocle-gateway[7849]: } Aug 03 13:46:42 FhemServer monocle-gateway[7849]: 2019-08-03T11:46:42.965Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined) Aug 03 13:46:42 FhemServer monocle-gateway[7849]: 2019-08-03T11:46:42.966Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] { Aug 03 13:46:42 FhemServer monocle-gateway[7849]: "cseq": "1", Aug 03 13:46:42 FhemServer monocle-gateway[7849]: "date": "Sat, Aug 03 2019 11:46:42 GMT" Aug 03 13:46:42 FhemServer monocle-gateway[7849]: } Aug 03 13:46:44 FhemServer monocle-gateway[7849]: ------------------------------------------------- Aug 03 13:46:44 FhemServer monocle-gateway[7849]: INITIALIZE RTSP STREAM: Garten Aug 03 13:46:44 FhemServer monocle-gateway[7849]: ------------------------------------------------- Aug 03 13:46:44 FhemServer monocle-gateway[7849]: - NAME : Garten Aug 03 13:46:44 FhemServer monocle-gateway[7849]: - LABEL : PRIMARY Aug 03 13:46:44 FhemServer monocle-gateway[7849]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp Aug 03 13:46:44 FhemServer monocle-gateway[7849]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Aug 03 13:46:44 FhemServer monocle-gateway[7849]: - SESS : 1b855079-672f-4e8b-9bf0-4cbe62ca6538 Aug 03 13:46:44 FhemServer monocle-gateway[7849]: - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00) Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - TAGS : @hangup,@proxy-tcp Aug 03 13:46:45 FhemServer monocle-gateway[7849]: ------------------------------------------------- Aug 03 13:46:45 FhemServer monocle-gateway[7849]: ------------------------------------------------- Aug 03 13:46:45 FhemServer monocle-gateway[7849]: INITIALIZE RTSP STREAM: Garten Aug 03 13:46:45 FhemServer monocle-gateway[7849]: ------------------------------------------------- Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - NAME : Garten Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - LABEL : PRIMARY Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxx&channel=1&stream=1.sdp Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - SESS : cd171ddb-2a0c-44f7-931e-c1b45c341f4e Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00) Aug 03 13:46:45 FhemServer monocle-gateway[7849]: - TAGS : @hangup,@proxy-tcp Aug 03 13:46:45 FhemServer monocle-gateway[7849]: ------------------------------------------------- Aug 03 13:47:13 FhemServer monocle-gateway[7849]: 2019-08-03T11:47:13.744Z [INFO] [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 4 MINUTES Aug 03 13:48:13 FhemServer monocle-gateway[7849]: 2019-08-03T11:48:13.802Z [INFO] [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 3 MINUTES Aug 03 13:49:13 FhemServer monocle-gateway[7849]: 2019-08-03T11:49:13.861Z [INFO] [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 2 MINUTES Aug 03 13:50:13 FhemServer monocle-gateway[7849]: 2019-08-03T11:50:13.921Z [INFO] [RTSP PROXY] STREAM [Garten/PRIMARY] WILL BE DE-REGISTERED IN 1 MINUTES Aug 03 13:51:05 FhemServer monocle-gateway[7849]: [RTSP Server Stopping] Aug 03 13:51:05 FhemServer systemd[1]: Stopping Monocle Gateway Service... Aug 03 13:51:05 FhemServer monocle-gateway[7849]: [RTSP Server Stopped] Aug 03 13:51:05 FhemServer monocle-gateway[7849]: [Monocle Stopping] Aug 03 13:51:05 FhemServer monocle-gateway[7849]: [Monocle Stopped] Aug 03 13:51:05 FhemServer monocle-gateway[7849]: [RTSP Proxy Stopped] CODE=0; SIGNAL=SIGTERM Aug 03 13:51:05 FhemServer systemd[1]: Stopped Monocle Gateway Service. Aug 03 13:51:05 FhemServer systemd[1]: Started Monocle Gateway Service. Aug 03 13:51:06 FhemServer monocle-gateway[7948]: ****************************************************************** Aug 03 13:51:06 FhemServer monocle-gateway[7948]: * __ __ ___ _ _ ___ ___ _ ___ * Aug 03 13:51:06 FhemServer monocle-gateway[7948]: * | \/ |/ _ \| \| |/ _ \ / __| | | __| * Aug 03 13:51:06 FhemServer monocle-gateway[7948]: * | |\/| | (_) | .` | (_) | (__| |__| _| * Aug 03 13:51:06 FhemServer monocle-gateway[7948]: * |_| |_|\___/|_|\_|\___/ \___|____|___| * Aug 03 13:51:06 FhemServer monocle-gateway[7948]: * * Aug 03 13:51:06 FhemServer monocle-gateway[7948]: ****************************************************************** Aug 03 13:51:06 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:06 FhemServer monocle-gateway[7948]: MONOCLE RUNTIME ENVIRONMENT Aug 03 13:51:06 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:06 FhemServer monocle-gateway[7948]: VERSION = 0.0.4-1 Aug 03 13:51:06 FhemServer monocle-gateway[7948]: OS/ARCH = linux/arm Aug 03 13:51:06 FhemServer monocle-gateway[7948]: PROCESS = monocle-gateway (PID=7948) Aug 03 13:51:06 FhemServer monocle-gateway[7948]: TIMESTAMP = 2019-08-03T11:51:06.973Z Aug 03 13:51:06 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:06 FhemServer monocle-gateway[7948]: MONOCLE GATEWAY SERVICE (Version: 0.0.4-1) Aug 03 13:51:06 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:06 FhemServer monocle-gateway[7948]: [Monocle Starting] Aug 03 13:51:06 FhemServer monocle-gateway[7948]: [Monocle Connecting] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [Monocle Started] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [RTSP Server Starting] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [RTSP Server Listening] 0.0.0.0:8555 (RTSP) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [RTSP Proxy Started] (PID=7959) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [RTSP Server Listening] 0.0.0.0:8554 (PROXY) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [RTSP Server Started] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:07.090Z [ERROR] [PROXY SERVER ERROR] Error: listen EACCES 0.0.0.0:443 Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [ '[PROXY SERVER ERROR]', Aug 03 13:51:07 FhemServer monocle-gateway[7948]: { Error: listen EACCES 0.0.0.0:443 Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at Server.setupListenHandle [as _listen2] (net.js:1310:19) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at listenInCluster (net.js:1375:12) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at doListen (net.js:1501:7) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at process._tickCallback (internal/process/next_tick.js:63:19) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at Function.Module.runMain (pkg/prelude/bootstrap.js:1315:13) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at startup (internal/bootstrap/node.js:274:19) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at bootstrapNodeJSCore (internal/bootstrap/node.js:608:3) Aug 03 13:51:07 FhemServer monocle-gateway[7948]: errno: 'EACCES', Aug 03 13:51:07 FhemServer monocle-gateway[7948]: code: 'EACCES', Aug 03 13:51:07 FhemServer monocle-gateway[7948]: syscall: 'listen', Aug 03 13:51:07 FhemServer monocle-gateway[7948]: address: '0.0.0.0', Aug 03 13:51:07 FhemServer monocle-gateway[7948]: port: 443 } ] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:07.104Z [ERROR] [RTSP Server Error] listen EACCES 0.0.0.0:443 Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [ '[RTSP Server Error]', 'listen EACCES 0.0.0.0:443' ] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [Monocle Connected] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [RTSP Server Registered] Aug 03 13:51:07 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:07 FhemServer monocle-gateway[7948]: MONOCLE RTSP SERVICE - INITIALIZED Aug 03 13:51:07 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:07 FhemServer monocle-gateway[7948]: FQDN = 9dd28fe1-40f2-4459-805d-daa62fdc6ff5.mproxy.io Aug 03 13:51:07 FhemServer monocle-gateway[7948]: HOST = 192.168.2.172 Aug 03 13:51:07 FhemServer monocle-gateway[7948]: PORT = 443 Aug 03 13:51:07 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:20 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:20 FhemServer monocle-gateway[7948]: INITIALIZE RTSP STREAM: Garten Aug 03 13:51:20 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:20 FhemServer monocle-gateway[7948]: - NAME : Garten Aug 03 13:51:20 FhemServer monocle-gateway[7948]: - LABEL : PRIMARY Aug 03 13:51:20 FhemServer monocle-gateway[7948]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxxxxx&channel=1&stream=1.sdp Aug 03 13:51:20 FhemServer monocle-gateway[7948]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Aug 03 13:51:20 FhemServer monocle-gateway[7948]: - SESS : 6d95feeb-81fc-45c6-8dfa-59a8e864bdc3 Aug 03 13:51:20 FhemServer monocle-gateway[7948]: - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00) Aug 03 13:51:20 FhemServer monocle-gateway[7948]: - TAGS : @hangup,@proxy-tcp Aug 03 13:51:20 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:20 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:20.832Z [INFO] [RTSP PROXY] REGISTERING STREAM [Garten/PRIMARY]; (STREAM:df443cff-97a9-45ac-a21d-9768d4674f63) Aug 03 13:51:20 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:20.849Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [REGISTER] rtsp://192.168.2.102:554/user=admin&password=xxxxxxxxx&channel=1&stream=1.sdp Aug 03 13:51:20 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:20.849Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] { Aug 03 13:51:20 FhemServer monocle-gateway[7948]: "cseq": "1", Aug 03 13:51:20 FhemServer monocle-gateway[7948]: "transport": "reuse_connection=0;preferred_delivery_protocol=interleaved;proxy_url_suffix=STREAM:df443cff-97a9-45ac-a21d-9768d4674f63" Aug 03 13:51:20 FhemServer monocle-gateway[7948]: } Aug 03 13:51:20 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:20.853Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined) Aug 03 13:51:20 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:20.854Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] { Aug 03 13:51:20 FhemServer monocle-gateway[7948]: "cseq": "1", Aug 03 13:51:20 FhemServer monocle-gateway[7948]: "date": "Sat, Aug 03 2019 11:51:20 GMT" Aug 03 13:51:20 FhemServer monocle-gateway[7948]: } Aug 03 13:51:23 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:23 FhemServer monocle-gateway[7948]: INITIALIZE RTSP STREAM: Garten Aug 03 13:51:23 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:23 FhemServer monocle-gateway[7948]: - NAME : Garten Aug 03 13:51:23 FhemServer monocle-gateway[7948]: - LABEL : PRIMARY Aug 03 13:51:23 FhemServer monocle-gateway[7948]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxxxxxx&channel=1&stream=1.sdp Aug 03 13:51:23 FhemServer monocle-gateway[7948]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Aug 03 13:51:23 FhemServer monocle-gateway[7948]: - SESS : c0e72f49-5c9f-4577-9869-6532a3c07ba8 Aug 03 13:51:23 FhemServer monocle-gateway[7948]: - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00) Aug 03 13:51:23 FhemServer monocle-gateway[7948]: - TAGS : @hangup,@proxy-tcp Aug 03 13:51:23 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:24 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:24 FhemServer monocle-gateway[7948]: INITIALIZE RTSP STREAM: Garten Aug 03 13:51:24 FhemServer monocle-gateway[7948]: ------------------------------------------------- Aug 03 13:51:24 FhemServer monocle-gateway[7948]: - NAME : Garten Aug 03 13:51:24 FhemServer monocle-gateway[7948]: - LABEL : PRIMARY Aug 03 13:51:24 FhemServer monocle-gateway[7948]: - URL : rtsp://192.168.2.102:554/user=admin&password=xxxxxxx&channel=1&stream=1.sdp Aug 03 13:51:24 FhemServer monocle-gateway[7948]: - UUID : STREAM:df443cff-97a9-45ac-a21d-9768d4674f63 Aug 03 13:51:24 FhemServer monocle-gateway[7948]: - SESS : b1aa4b49-3d2d-498a-8ae9-0654a4281369 Aug 03 13:51:24 FhemServer monocle-gateway[7948]: - MODIF : Fri Aug 02 2019 15:46:47 GMT+0200 (GMT+02:00) Aug 03 13:51:24 FhemServer monocle-gateway[7948]: - TAGS : @hangup,@proxy-tcp Aug 03 13:51:24 FhemServer monocle-gateway[7948]: ------------------------------------------------- ^C -
OK, if you start at the bottom of that log and scroll up until you find where the service is started, you will see this error:
Aug 03 13:51:07 FhemServer monocle-gateway[7948]: 2019-08-03T11:51:07.090Z [ERROR] [PROXY SERVER ERROR] Error: listen EACCES 0.0.0.0:443 Aug 03 13:51:07 FhemServer monocle-gateway[7948]: [ '[PROXY SERVER ERROR]', Aug 03 13:51:07 FhemServer monocle-gateway[7948]: { Error: listen EACCES 0.0.0.0:443 Aug 03 13:51:07 FhemServer monocle-gateway[7948]: at Server.setupListenHandle [as _listen2] (net.js:1310:19)That is the primary issue. The Monocle Gateway is unable to listen on port 443. This could be a permissions issue or could be that something else is using port 443. Since the gateway seems to work fine running in stand-alone mode, its probably a permissions issue. However, lets rule out the port already in use first with a simple check.
First make sure to stop the service using this command:
monocle-gateway --stopThen check for anything else LISTENING on port 443.
You can check to see what processes are already using port 443 using the following command:
(ref: https://www.cyberciti.biz/faq/unix-linux-check-if-port-is-in-use-command/)$ sudo lsof -i -P -n | grep LISTEN uv4l 334 root 4u IPv4 13349 0t0 TCP *:8080 (LISTEN) sshd 463 root 3u IPv4 11156 0t0 TCP *:22 (LISTEN) sshd 463 root 4u IPv6 11158 0t0 TCP *:22 (LISTEN) monocle-g 759 monocle 13u IPv4 489943 0t0 TCP *:8555 (LISTEN) monocle-g 759 monocle 15u IPv4 489944 0t0 TCP *:443 (LISTEN) monocle-p 774 monocle 3u IPv4 495953 0t0 TCP *:8554 (LISTEN)I’m expecting that there will be no other processes listening on port 443. If that is the case, we can start looking into a permissions related issue.
Thanks, Robert
-
So there is nothing listing on Port 443
I thing it is a permission probleme because if I start it with monocle-gateway without any options it works.
root@FhemServer:~# sudo lsof -i -P -n | grep LISTEN java 397 root 18u IPv6 15321 0t0 TCP *:8080 (LISTEN) vncserver 440 root 11u IPv6 13164 0t0 TCP *:5900 (LISTEN) vncserver 440 root 12u IPv4 13165 0t0 TCP *:5900 (LISTEN) sshd 458 root 3u IPv4 14437 0t0 TCP *:22 (LISTEN)sshd 458 root 4u IPv6 12894 0t0 TCP *:22 (LISTEN)pilight-d 519 root 10u IPv4 13152 0t0 TCP *:5000 (LISTEN) pilight-d 519 root 14u IPv4 12091 0t0 TCP *:5002 (LISTEN) pilight-d 519 root 15u IPv4 12092 0t0 TCP *:5001 (LISTEN) perl 544 fhem 5u IPv4 12111 0t0 TCP *:7072 (LISTEN) perl 544 fhem 6u IPv4 14749 0t0 TCP *:8083 (LISTEN) perl 544 fhem 7u IPv4 13723 0t0 TCP *:8084 (LISTEN) perl 544 fhem 8u IPv4 13724 0t0 TCP *:8085 (LISTEN) perl 544 fhem 10u IPv4 14752 0t0 TCP *:8091 (LISTEN) perl 544 fhem 15u IPv4 15213 0t0 TCP *:9999 (LISTEN) perl 544 fhem 16u IPv4 14227 0t0 TCP *:8090 (LISTEN) perl 544 fhem 17u IPv4 17086 0t0 TCP *:8081 (LISTEN) perl 544 fhem 18u IPv4 14249 0t0 TCP *:1883 (LISTEN) perl 544 fhem 33u IPv4 17363 0t0 TCP *:8383 (LISTEN) smbd 708 root 33u IPv6 15565 0t0 TCP *:445 (LISTEN) smbd 708 root 34u IPv6 15566 0t0 TCP *:139 (LISTEN) smbd 708 root 35u IPv4 15567 0t0 TCP *:445 (LISTEN) smbd 708 root 36u IPv4 15568 0t0 TCP *:139 (LISTEN) node 878 fhem 18u IPv6 18698 0t0 TCP *:8086 (LISTEN) node\x20/ 1297 fhem 18u IPv4 19473 0t0 TCP 127.0.0.1:34729 (LISTEN) cupsd 5343 root 9u IPv6 443540 0t0 TCP [::1]:631 (LISTEN) cupsd 5343 root 10u IPv4 443541 0t0 TCP 127.0.0.1:631 (LISTEN) -
When the daemon/service is installed, this script is run to create a new “monocle” system user and grant them access to the monocle configuration directory:
# Create Monocle service user account to run under echo "Creating 'monocle' system user account" useradd --system -m monocle # Create required config directory echo "Creating configuration directory at '/etc/monocle/'" mkdir -p /etc/monocle/ # Set group ownership and permissions of config directory chgrp -f -R monocle /etc/monocle chmod -f -R g+rw /etc/monocleThe following commands are also run after the executables are copied to the system:
# Configure system to allow Monocle-Gateway access to port 443 echo "Configuring bind access to system reserved port 443" setcap 'cap_net_bind_service=+ep' /usr/local/bin/monocle-gateway # Reload systemd services echo "Reloading systemd daemon" systemctl daemon-reload # Install Monocle Gateway as a system service echo "Starting Monocle Gateway service daemon" systemctl start monocle-gateway echo "Enabling Monocle Gateway service deamon to start automatically" systemctl enable monocle-gateway # Check the status of the Monocle service instance #sudo systemctl status monocle-gatewayTake a look at this command:
sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/monocle-gatewayI wonder if that is the problem on your system. If that failed for any reason, that would explain why your daemon/service instance is not able to access port 443.
Try running that single command (usingsudo) and see what happens.Thanks, Robert
-
Ther coms nothing see
pi@FhemServer:~ $ sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/monocle-gateway pi@FhemServer:~ $ -
If you restart the monocle gateway, does it still have the port 443 error?
I can also use this command to verify the attribute exits on the file:
> sudo getcap /usr/local/bin/monocle-gateway /usr/local/bin/monocle-gateway = cap_net_bind_service+epMonocle: https://monoclecam.com
Getting Started | Troubleshooting Guide | FAQ | Contact Support -
Another thing you can try is editing this file:
/etc/systemd/system/monocle-gateway.serviceAdd the line
AmbientCapabilities=CAP_NET_BIND_SERVICEunder the[Service]section so that the file looks like this:# ********************************************************************* # __ __ ___ _ _ ___ ___ _ ___ # | \/ |/ _ \| \| |/ _ \ / __| | | __| # | |\/| | (_) | .` | (_) | (__| |__| _| # |_| |_|\___/|_|\_|\___/ \___|____|___| # # ------------------------------------------------------------------- # MONOCLE GATEWAY SYSTEMD INIT SCRIPT # COPYRIGHT SHADEBLUE, LLC @ 2018, ALL RIGHTS RESERVED # ------------------------------------------------------------------- # # ********************************************************************* [Unit] Description=Monocle Gateway Service After=network.target ConditionPathExists=/usr/local/bin/monocle-gateway ConditionPathExists=/usr/local/bin/monocle-proxy ConditionFileIsExecutable=/usr/local/bin/monocle-gateway ConditionFileIsExecutable=/usr/local/bin/monocle-proxy ConditionPathExists=/etc/monocle/monocle.token ConditionFileNotEmpty=/etc/monocle/monocle.token [Service] AmbientCapabilities=CAP_NET_BIND_SERVICE ExecStart=/usr/local/bin/monocle-gateway WorkingDirectory=/home/monocle/ StandardOutput=inherit StandardError=inherit Restart=always RestartSec=120 StartLimitInterval=5 StartLimitBurst=10 User=monocle [Install] WantedBy=multi-user.targetNext, run this command to RELAOD the service config:
sudo systemctl daemon-reloadNow restart the monocle gateway and check to log to see if that helped.
Thanks, Robert
-
Hi newbie here, I’ve just started using monocle on a Victure IP camera from Amazon. I had very similar problems to you (although I’ve not read all your threads). My problem was solved when I switched to a new Pi install. I think the problem was Apache running on my main Pi which I use for Domoticz. It was using port 443. I have the stream running on a show 5, Fire & Fire HD. Now all I have to solve is the buffering!
-
Now after this command
> sudo getcap /usr/local/bin/monocle-gatewayIt looks like good. I have made a restart from Raspberry Pi and Alexa can show me the Cam.
And there is no brake I test it some times and give them again feedback. -
Success?
-
Yes it works now, the stream runns with audio. And it did not stop from self. Is there also a way to use IP cams without RTSP viedeo streams? I have one more IP Cam but they did not have a RTSP it is a URL in this format http://ipaddress/videostream.cgi
-
I have one more IP Cam but they did not have a RTSP it is a URL in this format http://ipaddress/videostream.cgi
At this time no. At least not with Monocle and Alexa. Alexa only supports RTSP (and WebRTC) streams. You would have to setup some external media server that can accept the camera stream and convert it into a H.264 RTSP stream.
-
So
I will say thank you for your support and the time you have spend.
I have ordered one more cam like this for 23€ with shipping is it very good.Thanks a lot
-
You are welcome. Enjoy!
-
Here have the same camera board as the first post and using an Alexa Show 5. (new).
I am hoping to update my very old Optex security cameras with these camera boards.
I can see two channels using VLC and the command:
1 - rtsp://192.168.244.151/user=admin_password=xxx_channel=0_stream=1.sdp
Which provides me with a 352X240 video resolution.2 - rtsp://192.168.244.151/user=admin_password=xxx_channel=0_stream=0.sdp
which provides me with a 1920X1080 resolution.I am using a PFSense firewall here. I have disabled sound on the camera.
I also have a Ring Doorbell which works fine with the Amazon Alexa Show. Looked to change over to the HikVision OEM doorbell in the next few weeks.
Also installed the Monocle Gateway here, made above modifications and have tried all of the tags.
See this:
monocle-g 27697 monocle 12u IPv4 109131 0t0 TCP *:8555 (LISTEN)
monocle-g 27697 monocle 14u IPv4 109132 0t0 TCP *:443 (LISTEN)
monocle-p 27725 monocle 3u IPv4 109748 0t0 TCP *:8554 (LISTEN)OK so adjusted my PFSense DNS Resolver adding custom options.
server:
private-domain: “xxx.mproxy.io”Tested it by pinging xxx.mproxy.io and get a response.
Now when I ask Alexa to show test cam it appears to try for about a minute then quits. Beforehand it would quit right away…so I am getting close.
Got it working fine now changing @tunnel to @proxy.
Great stuff.
Auto mator
-
Glad you found a way to get it working for your cameras!
Monocle: https://monoclecam.com
Getting Started | Troubleshooting Guide | FAQ | Contact Support -
@Monocle
Great application.Today purchased my Echo Show #2.
This is actually an IP HD camera board. Way long time ago had gone to using Grandstream cameras and boards for modded cameras. These boards came with an SDK for development. Looking to retrofit my Optex combo camera/PIRs with these camera boards.Auto mator
-
Sounds like an interesting project … I’ve modded lots of hardware in the past, but never an IP cam :-)
-
Hallo i have trubbel.
My cam was working with the monocle gateway for long time but now, I thing since one week Alexa tells my “the Camera is not responding” the gateway service is running and the cam is working with other tools and with VLC Player.Was there any Changes or anything else?
-
No, no changes on our side. Feel free to post your log info from Monocle Gateway while you are requesting the camera feed that is no longer working.
Its possible that Amazon has updated the system firmware and broken something. That happened with the Wansview cameras with the release of Echo Show 5.
