NodeJS is not working - Revision history

IVSWikiBlue at 20:50, 11 May 2022

2022-05-11T20:50:12Z

← Older revision		Revision as of 20:50, 11 May 2022
Line 3:		Line 3:
	* When starting or stopping a recording, the buttons do not update.		* When starting or stopping a recording, the buttons do not update.
	* When opening the Observe tab, only the following message is displayed:		* When opening the Observe tab, only the following message is displayed:
	~~[[File~~:nodejs.png \| ~~900px\|link~~=~~https://ipivs.com/wiki/images/4/4c/Nodejs.png]]~~		:::{{img \| file = nodejs.png \| width=800px}}

	=Diagnosis=		=Diagnosis=
Line 10:		Line 10:
	To check the connection to NodeJS from the client computer do the following:		To check the connection to NodeJS from the client computer do the following:
	# Open the VALT application in Google Chrome.		# Open the VALT application in Google Chrome.
	#: ~~[[File:~~nodejs6.png \| ~~900px\|link~~=~~https://ipivs.com/wiki/images/0/09/Nodejs6.png]]~~		#: {{img \| file = nodejs6.png \| width=800px}}
	# Right click on the page and select '''Inspect''' from the menu.		# Right click on the page and select '''Inspect''' from the menu.
	#: ~~[[File:~~nodejs7.png \| ~~900px\|link~~=~~https://ipivs.com/wiki/images/f/f5/Nodejs7.png]]~~		#: {{img \| file = nodejs7.png \| width=800px}}
	# Click on the '''Console''' tab.		# Click on the '''Console''' tab.
	#: ~~[[File:~~nodejs8.png \| ~~900px\|link~~=~~https://ipivs.com/wiki/images/b/bd/Nodejs8.png]]~~		#: {{img \| file = nodejs8.png \| width=800px}}
	#: If the client computer is unable to connect to NodeJS, you will receive an error message like the one above.		#: If the client computer is unable to connect to NodeJS, you will receive an error message like the one above.

Line 22:		Line 22:
	# Connect to the VALT appliance via SSH.		# Connect to the VALT appliance via SSH.
	# Type in the following, and then press Enter: <pre>ps -ax \| grep node</pre>		# Type in the following, and then press Enter: <pre>ps -ax \| grep node</pre>
	{\|		:::{\|
	\|~~[[File:nodejs2.png~~\|~~link~~=~~https://ipivs.com/wiki/images/6/67/Nodejs2~~.png]]		\|{{img \| file = nodejs2.png}}
	\|~~[[File:nodejs3.png~~\|~~link~~=~~https://ipivs.com/wiki/images/e/e6/Nodejs3~~.png]]		\|{{img \| file = nodejs3.png}}
	\|-		\|-
	\|align="center"\|This is a system where NodeJS is not running.		\|align="center"\|This is a system where NodeJS is not running.
Line 37:		Line 37:
	# Connect to the VALT appliance via SSH.		# Connect to the VALT appliance via SSH.
	# Type in the following, and then press Enter: <pre>nc -zv 127.0.0.1 8080</pre>		# Type in the following, and then press Enter: <pre>nc -zv 127.0.0.1 8080</pre>
	{\|		:::{\|
	\|~~[[File:nodejs5.png~~\|~~link~~=~~https://ipivs.com/wiki/images/6/60/Nodejs5~~.png]]		\|{{img \| file = nodejs5.png}}
	\|~~[[File:nodejs4.png~~\|~~link~~=~~https://ipivs.com/wiki/images/c/ca/Nodejs4~~.png]]		\|{{img \| file = nodejs4.png}}
	\|-		\|-
	\|align="center"\|This is a system where NodeJS is not listening.		\|align="center"\|This is a system where NodeJS is not listening.
Line 61:		Line 61:
	# Connect to the VALT appliance via SSH.		# Connect to the VALT appliance via SSH.
	# Type in the following, and press Enter: <pre>sudo nano /var/www/v3/nodejs/server.js</pre>		# Type in the following, and press Enter: <pre>sudo nano /var/www/v3/nodejs/server.js</pre>
	#: ~~[[File:nodejs9.png~~\|~~link~~=~~https://ipivs.com/wiki/images/9/90/Nodejs9~~.png]]		#: {{img \| file = nodejs9.png}}
	#: The file should appear similar to the picture above. Specifically the following section:		#: The file should appear similar to the picture above. Specifically the following section:

Line 126:		Line 126:
	You can test the certificate by doing the following:		You can test the certificate by doing the following:
	:Type in the following, and press Enter: <pre>openssl x509 -in certificate.cer -text -noout</pre>		:Type in the following, and press Enter: <pre>openssl x509 -in certificate.cer -text -noout</pre>
	~~[[File~~:~~nodejs10.png~~\|~~link~~=~~https://ipivs.com/wiki/images/4/46/Nodejs10~~.png]]		:::{{img \| file = nodejs10.png}}
	: An error similar to the picture above indicates the certificate is not PEM encoded.		: An error similar to the picture above indicates the certificate is not PEM encoded.

IVSWikiBlue: /* Certificate Error */

2021-03-17T19:50:43Z

Certificate Error

← Older revision		Revision as of 19:50, 17 March 2021
Line 126:		Line 126:
	You can test the certificate by doing the following:		You can test the certificate by doing the following:
	:Type in the following, and press Enter: <pre>openssl x509 -in certificate.cer -text -noout</pre>		:Type in the following, and press Enter: <pre>openssl x509 -in certificate.cer -text -noout</pre>
	[[File:nodejs10.png]]		[[File:nodejs10.png\|link=https://ipivs.com/wiki/images/4/46/Nodejs10.png]]
	: An error similar to the picture above indicates the certificate is not PEM encoded.		: An error similar to the picture above indicates the certificate is not PEM encoded.

IVSWikiBlue: /* Server.js Config Error */

2021-03-17T19:50:19Z

Server.js Config Error

← Older revision		Revision as of 19:50, 17 March 2021
Line 61:		Line 61:
	# Connect to the VALT appliance via SSH.		# Connect to the VALT appliance via SSH.
	# Type in the following, and press Enter: <pre>sudo nano /var/www/v3/nodejs/server.js</pre>		# Type in the following, and press Enter: <pre>sudo nano /var/www/v3/nodejs/server.js</pre>
	#: [[File:nodejs9.png]]		#: [[File:nodejs9.png\|link=https://ipivs.com/wiki/images/9/90/Nodejs9.png]]
	#: The file should appear similar to the picture above. Specifically the following section:		#: The file should appear similar to the picture above. Specifically the following section:

IVSWikiBlue: /* NodeJS is not listening */

2021-03-17T19:49:43Z

NodeJS is not listening

← Older revision		Revision as of 19:49, 17 March 2021
Line 38:		Line 38:
	# Type in the following, and then press Enter: <pre>nc -zv 127.0.0.1 8080</pre>		# Type in the following, and then press Enter: <pre>nc -zv 127.0.0.1 8080</pre>
	{\|		{\|
	\|[[File:nodejs5.png]]		\|[[File:nodejs5.png\|link=https://ipivs.com/wiki/images/6/60/Nodejs5.png]]
	\|[[File:nodejs4.png]]		\|[[File:nodejs4.png\|link=https://ipivs.com/wiki/images/c/ca/Nodejs4.png]]
	\|-		\|-
	\|align="center"\|This is a system where NodeJS is not listening.		\|align="center"\|This is a system where NodeJS is not listening.

IVSWikiBlue: /* NodeJS stopped */

2021-03-17T19:48:44Z

NodeJS stopped

← Older revision		Revision as of 19:48, 17 March 2021
Line 23:		Line 23:
	# Type in the following, and then press Enter: <pre>ps -ax \| grep node</pre>		# Type in the following, and then press Enter: <pre>ps -ax \| grep node</pre>
	{\|		{\|
	\|[[File:nodejs2.png]]		\|[[File:nodejs2.png\|link=https://ipivs.com/wiki/images/6/67/Nodejs2.png]]
	\|[[File:nodejs3.png]]		\|[[File:nodejs3.png\|link=https://ipivs.com/wiki/images/e/e6/Nodejs3.png]]
	\|-		\|-
	\|align="center"\|This is a system where NodeJS is not running.		\|align="center"\|This is a system where NodeJS is not running.

IVSWikiBlue: /* Check Connection */

2021-03-17T19:47:39Z

Check Connection

← Older revision		Revision as of 19:47, 17 March 2021
Line 10:		Line 10:
	To check the connection to NodeJS from the client computer do the following:		To check the connection to NodeJS from the client computer do the following:
	# Open the VALT application in Google Chrome.		# Open the VALT application in Google Chrome.
	#: [[File:nodejs6.png \| 900px]]		#: [[File:nodejs6.png \| 900px\|link=https://ipivs.com/wiki/images/0/09/Nodejs6.png]]
	# Right click on the page and select '''Inspect''' from the menu.		# Right click on the page and select '''Inspect''' from the menu.
	#: [[File:nodejs7.png \| 900px]]		#: [[File:nodejs7.png \| 900px\|link=https://ipivs.com/wiki/images/f/f5/Nodejs7.png]]
	# Click on the '''Console''' tab.		# Click on the '''Console''' tab.
	#: [[File:nodejs8.png \| 900px]]		#: [[File:nodejs8.png \| 900px\|link=https://ipivs.com/wiki/images/b/bd/Nodejs8.png]]
	#: If the client computer is unable to connect to NodeJS, you will receive an error message like the one above.		#: If the client computer is unable to connect to NodeJS, you will receive an error message like the one above.

IVSWikiBlue: /* Symptoms */

2021-03-17T19:46:14Z

Symptoms

← Older revision		Revision as of 19:46, 17 March 2021
Line 3:		Line 3:
	* When starting or stopping a recording, the buttons do not update.		* When starting or stopping a recording, the buttons do not update.
	* When opening the Observe tab, only the following message is displayed:		* When opening the Observe tab, only the following message is displayed:
	[[File:nodejs.png \| 900px]]		[[File:nodejs.png \| 900px\|link=https://ipivs.com/wiki/images/4/4c/Nodejs.png]]

	=Diagnosis=		=Diagnosis=

IVSWikiBlue: /* Re-issue the certificate with a SAN */

2020-06-02T14:54:45Z

Re-issue the certificate with a SAN

← Older revision		Revision as of 14:54, 2 June 2020
Line 85:		Line 85:

	===Re-issue the certificate with a SAN===		===Re-issue the certificate with a SAN===
	# Connect to the ~~Valt~~ appliance via SSH.		# Connect to the VALT appliance via SSH.
	# Type in the following, and press Enter: <pre>nano csr_details.conf</pre>		# Type in the following, and press Enter: <pre>nano csr_details.conf</pre>
	# Copy and paste the following into nano:		# Copy and paste the following into nano:

IVSWikiBlue: /* Server.js Config Error */

2020-06-02T14:54:21Z

Server.js Config Error

← Older revision		Revision as of 14:54, 2 June 2020
Line 59:		Line 59:
	If the server has been configured to utilize SSL, but an error was made in the configuration of the Server.js file, the NodeJS service may fail to start or may start, but may not listen for connections. This is most likely to occur if the SSL configuration has been performed manually instead of utilizing the provided scripts through the command line menu. This can also occur if a typo is made when entering the key and certificates into the command line menu.		If the server has been configured to utilize SSL, but an error was made in the configuration of the Server.js file, the NodeJS service may fail to start or may start, but may not listen for connections. This is most likely to occur if the SSL configuration has been performed manually instead of utilizing the provided scripts through the command line menu. This can also occur if a typo is made when entering the key and certificates into the command line menu.

	# Connect to the ~~Valt~~ appliance via SSH.		# Connect to the VALT appliance via SSH.
	# Type in the following, and press Enter: <pre>sudo nano /var/www/v3/nodejs/server.js</pre>		# Type in the following, and press Enter: <pre>sudo nano /var/www/v3/nodejs/server.js</pre>
	#: [[File:nodejs9.png]]		#: [[File:nodejs9.png]]

IVSWikiBlue: /* Antivirus */

2020-06-02T14:53:47Z

Antivirus

← Older revision		Revision as of 14:53, 2 June 2020
Line 54:		Line 54:

	==Antivirus==		==Antivirus==
	Issues connecting to NodeJS can be caused by a local antivirus on the client PC. If Port 8080 is not open between the PC and the ~~Valt~~ appliance, the client will be unable to connect to NodeJS. If this is the cause of the issue, you will be unable to connect to NodeJS from the client PC, but NodeJS will be running, and will be listening for inbound connections.		Issues connecting to NodeJS can be caused by a local antivirus on the client PC. If Port 8080 is not open between the PC and the VALT appliance, the client will be unable to connect to NodeJS. If this is the cause of the issue, you will be unable to connect to NodeJS from the client PC, but NodeJS will be running, and will be listening for inbound connections.

	==Server.js Config Error==		==Server.js Config Error==
	If the server has been configured to utilize SSL, but an error was made in the configuration of the Server.js file, the NodeJS service may fail to start or may start, but may not listen for connections. This is most likely to occur if the SSL configuration has been performed manually instead of utilizing the provided scripts through the command line menu. This can also occur if a typo is made when entering the key and certificates into the command line menu.		If the server has been configured to utilize SSL, but an error was made in the configuration of the Server.js file, the NodeJS service may fail to start or may start, but may not listen for connections. This is most likely to occur if the SSL configuration has been performed manually instead of utilizing the provided scripts through the command line menu. This can also occur if a typo is made when entering the key and certificates into the command line menu.