When using the exacqVision Mobile app with the release of exacqVision Server 24.09 or higher, the exacqVision Mobile app will connect directly to the exacqVision Server service rather than require the intermediary exacqVision Web Service.
By default the service will listen for incoming mobile app connections on port 8443. This may be manually changed by the system administrator to accommodate network needs when needed.
<br>
Product
exacqVision Server, version 24.09 and above
exacqVision Mobile, version 24.09 and above
<br>
Steps
Log into the system running the exacqVision Server instance with administrative privileges.<br><br>
The method used for connecting to an exacqVision system from outside the LAN it resides on will depend on your network configuration and use case. Examples are provided below based on each method.
Remote Connections
Remote Connections are supported by exacqVision Server/Client 24.09 and above to facilitate connections from the exacqVision Mobile app. When considering the network configurations Remote Connections eliminate the need to open ports or enable port forwarding rules on your router by using Exacq’s Remote Connectivity service. Users of the mobile app enter an access code generated by the system admin and the Remote Connectivity agent handles the connecting of the mobile app user and the Server.
NOTE: Remote Connectivity does not accept connections for the Desktop Client software or the earlier Exacq Mobile 3 app. Only exacqVision Mobile 24.09 and higher are supported.
<br>
Traditional
In a traditional setup, the site’s router is configured to port forward incoming external connections on each port. The ports configured for forwarding incoming traffic vary depending on whether users will connect via exacqVision Desktop Client software, the web browser client, or a mobile app.
<br>
Web Relay Service
Sites using exacqVision Web Service 19.06 and higher may wish to take advantage of the web service Relay, which provides a web-based proxy to connect to, avoiding the need to configure the router for port forwarding. When enabled, the exacqVision Web Service Status page will display the Relay Service IP. Remote users will then be able to connect their Exacq Mobile 3 app or web browser client directly to this proxy IP address.
NOTE: The Relay Service does not accept connections for the Desktop Client software, only web browser and Exacq Mobile 3 connections.
Using the Serial Ports page allows you to configure your ExacqVision system to receive serial data from Point of Sale (POS) devices, ATMs, access control devices, and more over UART or serial over IP connections.
Learn more about the address, ports, and protocols used for these tasks.
Edge cameras cannot run the exacqVision Web Service. If you want to connect to an Edge camera using the Web Client or the Exacq Mobile 3 app you will need to install the exacqVision Web Service on another machine.
The web service can be run on other machines but you will need to enter the Web Service Configuration to change the default server address from the loop back of 127.0.0.1 to the address of your Edge device(s).
Unlike an NVR installation of the exacqVision Server, the Edge Server application does not permit changing the default listening port for incoming client connections. Therefore, if you need to use the web service with Edge cameras you will need to configure the proper port forwarding for these connections. The addresses and port forwarding used depend on where you are placing the web service, and whether you are using multiple Edge devices behind the same router.
<br>
Web Service Inside LAN
If the web service is inside the same Local Area Network as the Edge cameras, you may use the Server Connections page in the Web Service Configuration to connect the web service to each Edge camera. This requires minimal port forwarding in the router.
<br>
Web Service Across WAN
If the web service is placed outside of the Local Area Network the Edge cameras are on, you will need to configure port forwarding as well as port translation. Port translation is used because the listening port of the Edge servers cannot be changed from their default port numbers.
NOTE: Some home or small business routers may not be capable of port translation.
Best practice for servers with more than one NIC includes isolating camera traffic to a separate scheme. This practice not only isolates camera bandwidth consumption from other network traffic, but also adds an additional layer of security to prevent workstation users from accessing cameras and video streams directly.
Whether using separate network switches or creating a VLAN on shared switches, the concept is the same.
<br>
IMPORTANT: DO NOT place both NICs within the same subnet. This is a poor network practice that WILL cause communication problems. Administrators that wish to attempt utilizing more than one NIC within a single subnet for redundancy or transfer speeds must configure NIC bonding/teaming. This is only recommended for systems with more than two NICs so that cameras may continue to be isolated from other network traffic. See also:
There are two ways to modify the ports used by the Web Service:
Using the Web Service configuration interface
Hand editing the configuration file
It is recommended to use the configuration interface, whenever possible. However, it is possible that you must hand edit the configuration in cases where the Web Service cannot start (for example, if there is a port conflict). This article provides instructions for both methods.
Important: The structure and location of the Web Service config has changed over the life of the web service. Please pay close attention to the section headers in this article, as they indicate the versions to which particular instructions apply.
While various versions are mentioned in this article, it is recommend to keep your Web Service updated to the latest version to help prevent exposure to vulnerabilities and take advantage of the latest performance improvements.
<br>
Using the Web Service configuration UI
Versions 9.6 and above
Log into Web Service Configuration using your Web Service administrator account. Using the provided Web Service configuration interface navigate to Configuration > Ports.
Update the fields to change to your selected port number, then click ‘Apply’ to save your changes. The Web Service will need to restart to reflect your changes.
Versions 7.6 to 9.4
Web Service version 7.2 introduced Web Sockets for video streaming. Version 9.4 was the last version to feature Web Sockets, as it was replaced by other improvements.
When logging into Web Service Configuration, navigate to Configuration > Ports. Update the fields shown to your selected port numbers then click ‘Apply’ to save your changes. The Web Service will need to restart to reflect your changes.
Versions 7.2 to 7.6
Web Service version 7.2 introduced Web Sockets for video streaming. Version 9.4 was the last version to feature Web Sockets, as it was replaced by other improvements.
When logging into Web Service Configuration, navigate to Basic Service Configuration. You have the ability to update the Web Service Port and WebSocket Ports through the configuration page.
To change the HTTPS (SSL) or Secure WebSocket (SSL) ports requires manually editing the configuration file. See the section in this article titled ‘Manual Configuration‘ for more on these steps.
The Web Service will need to restart to reflect your changes.
Versions 7.0 and earlier
These versions are quite dated and as mentioned earlier, we recommend keeping your Web Services updated to help avoid vulnerabilities and take advantage of new features and performance enhancements.
<br>
Additional SSL Information
Note: Changing the SSL ports (https/wss) DOES NOT enable SSL. This merely allows you to easily modify those ports, but you still need to manually configure SSL support for both Apache and WebSockets. See the following article on configuring a certificate for HTTPS.
Firewall/Router Configuration
Note: Be sure to forward the new port in your router. Exacq Technical Support does not provide assistance with port forwarding, but see the following links if necessary:
Manual Configuration (hand editing the configuration)
The steps here will change depending on the type of port (HTTP vs. WebSockets) you wish to edit.
HTTP / HTTPS (Web Service verions 7.2 and above)
The first step to manual editing is to find the location of the config file where the port numbers are held. This depends on both the platform (operating system) and version of the Web Service you have installed.
Windows:
9.0.x+ (both HTTP and HTTPS are in the same file): C:\ProgramData\Webservice\conf\wfe.json
9.0.x+ (both HTTP and HTTPS are in the same file): /etc/webservice/wfe.json
7.2.x – 8.8.x:
HTTP: /etc/evapache/httpd.conf
HTTPS: /etc/evapache/extra/httpd-ssl.conf
Determine where this file is for your install before continuing.
Once you have found the file, open it using your editor of choice (be sure to do so with administrative privileges) and perform either of the following depending on its name:
For httpd.conf (HTTP port) and httpd-ssl.conf (HTTPS port):
Find the Listen directive in the file
For example, if the current port is 80, the line should read Listen 80
Modify the port number as desired
Save the file and restart Apache and the Web Service
For wfe.json:
Find the webserver section
For the HTTP port:
Find the listen key, nested one level within the webserver section
Modify the port number as desired
For the HTTPS port:
Find the tls key, nested one level within the webserver section
Under the tls section, find the listen key one level below
Modify the port number as desired
Save the file and restart the web service
<br>
Web Sockets (7.2.x – 9.4.x)
Both the standard and SSL WebSocket ports are changed from the Web Service ini/conf file. The location and name of this file depends on the platform (operating system) and web service version:
Determine where this file is for your install before continuing.
Once you have found the file, open it using your editor of choice (be sure to do so with administrative privileges) and perform the following:
Find the [Broker] section. This will only appear if it was entered manually before, or you configured it previously using the UI. So if you do not see it, and are configuring it for the first time, you may need to enter it by hand.
The standard websocket port configuration is websocket_port = 8082, while the secure websocket port (wss) is ssl_port = 8083. Modify the port numbers as desired.
As mentioned above, if these configuration settings are not already present, or the [Broker] section is missing, the defaults are being used. You may manually add the section/settings with desired values should this be the case. The resulting section of the file should appear similar to the below example, with your custom port numbers. [Broker] websocket_port = 8082 ssl_port = 8083
When experiencing network connection or discovery issues, one possibility is that you have more than one service attempting to use the same port number.
To further investigate and attempt to resolve exacqVision port conflicts, complete the following steps:
Begin by opening the server logs. If you are unable to start the exacqVision Server service or are unable to connect to it from your client you will need to open the logs manually using a text editor, such as ‘Notepad’, on Windows.
On Windows systems, the server log files are located in: C:\Program Files\exacqVision\Server\logs\
The files located in this directory are named by date, so you will likely want to open the latest one. When opened, it should look similar to this:
In this example, you can see an error message that includes “ONVIF camera detection is not available. Could not bind receiving socket. Address already in use [239.255.255.250:3702].”
The important part of the message is the port number following the IP address (in this case, 3702).
Open a command prompt with elevated status. To do this, right-click Command Prompt and select ‘Run as Administrator’.
Run the command netstat -a -n -o. This displays the ports in use and their Process ID (PID). It should look similar to this:
Note that the ‘Local Address’ column displays information in IP Address:Port format.
Look for the port that matches the port shown in the error message in the exacqVision log file (3702 in the example). Scroll down if necessary to reveal all ports:
When you find the port, look at the ‘PID’ in the far-right column (in this case, the PID for 3702 is 3428).
Right-click on the Windows taskbar and select ‘Task Manager’. Click on the ‘Services’ tab and sort the ‘PID’ column by clicking the ‘PID’ column header. It should look similar to this:
Find the service that has the matching PID from the previous step. In this example, we see that the service associated with the PID is ‘FDResPub (Function Discovery Resource Publication)’. If more than one service appears with a matching PID, take note of this for use in a later step.
Open the ‘Services’ window from the ‘Control Panel’ or by searching for ‘Services’ within the Windows (Start) menu. It should look similar to this:
Find the service identified in the previous step. In this example, the status of the ‘Function Discovery Resource Publication’ service is “Started”; this is why ONVIF cameras cannot be found by the network scan.
Right-click the service and select ‘Stop’. The service’s entry should no longer list a status, as shown here:
Change the ‘Startup Type’ to ‘Manual’ or ‘Disabled’ within the ‘Properties’ dialog if necessary.
Determine whether there is still a port conflict. For example, in the case of the undetected ONVIF cameras, you should run the network scan in exacqVision Client.
If the port conflict still exists, and more than one running service matched the PID, restart the service that you stopped and then stop the next service with the same PID. Check for the port conflict again.
If the port conflict is not resolved even after disabling each of the services with the same PID, there are most likely other issues outside of Windows and exacqVision.
NOTES
When you identify the conflicting service, be sure you know how important the service is before you disable it permanently. If the service is important enough to keep enabled, you can simply stop it temporarily to accomplish what you need to do, and then restart it when finished.<br><br>
This article was based on a Windows 7 platform, but the process should also work on other Windows platforms. The specific services shown here might vary by platform.
By default, the exacqVision Client communicates with exacqVision Servers on port 22609. If your network does not allow port 22609, or if you need to forward the port on multiple exacqVision systems, you can change the exacqVision Server’s listening port number. To do this, complete steps detailed on this page.
NOTE: The exacqVision Default Ports article states that 22610 is reserved for interprocess communication. This is true when using the default client to server port set to 22609. If this is changed to a port other than 22609, the reserved port becomes your chosen port number plus one. Example: If you change 22609 to 2350, the reserved port becomes 2351.<br><br>
Windows 11, 10, 8, 7, Vista, XP
Log into the system hosting the exacqVision Server application.<br><br>
Exit all exacqVision software.<br><br>
Highlight the exacqVision Server service listed, and Stop the ExacqVision Server service, in one of three ways:
Press the ‘Stop’ icon from the toolbar.
Click the ‘Stop’ link from the left-hand side.
Right-click the service name and select ‘Stop’. Note: Leave the Services window open, as you will need to restart the service later.<br><br>
Open the Notepad application. Search for the application from the Windows Start menu, right-click and choose to ‘Run as Administrator’. <br><br>
Use Notepad to Open the following file: C:\Program Files\exacqVision\Server\streampi.xml<br> If you are using a 32-bit installation, select Program Files (x86) instead of Program Files.<br> NOTE: In the Open file dialogue, you will likely need to change the file type field from ‘Text Documents (*.txt)’ to All Files (*.*)’ to see file types of other extensions. <br><br>
In the streampi.xml file, scroll down until you find the line which states: <Port value="22609" />. Change the number to the port you want to use between the quotation marks (” “). Do NOT use port 22610 since this is reserved. The following example changes the port number to ‘11111’. <br><br>
After changing the port number, open the File menu, select Save, and close the editor window.<br><br>
Restart the exacqVision Server Service by clicking ‘Start’ button, link or from the right-click menu, in the Services window that you opened earlier. You should now be able to connect using the new port number.<br><br>
In the exacqVision Client, make sure the port number on the ‘Add Systems’ page matches the new port number. NOTE: The exacqVision Web Service is also a client of the exacqVision Server. Therefore, if using the exacqVision Web Service you may also be required to change the connecting port in the exacqVision Web Service Configuration.<br><br>
Ubuntu 20.04, 18.04, 16.04, 14.04, 12.04, 10.04
Log into the system hosting the exacqVision Server application.<br><br>
Exit all exacqVision software.<br><br>
Open a Terminal command prompt by pressing CTRL+ALT+T
NOTE: Depending on system settings, your Terminal window may appear with different colors than pictured.<br><br>
Stop the exacqVision Server by entering one of the following commands:
sudo service edvrserver stop
sudo /etc/init.d/edvrserver stop
NOTE: The sudo command elevates your system privileges in order to edit this file. Your system may prompt you for an administrator password. Enter this password if prompted. Linux systems do not display any characters when entering passwords in the CLI.
NOTE: On some systems you may see output that reads: sudo: unable to resolve host <hostname> Ignore this message if seen.<br><br>
You may use your preferred Linux editing tool, but in our example we will be using ‘gedit’.
Use gedit to open the streampi.xml file containing the settings for the exacqVision Server by entering: sudo gedit /usr/local/exacq/server/streampi.xml<br><br>
Locate the line which states: <Port value:"22609" /> Change the number to the port you want to use between the quotation marks (” “). Do NOT use port 22610 since this is reserved. The following example changes the port number to ‘11111’. <br><br>
Click ‘Save’ to commit your changes and close the editor window. <br><br>
Returning to the Terminal prompt, enter one of the following commands to restart the exacqVision Server:
sudo service edvrserver start
sudo /etc/init.d/edvrserver start<br><br>
In the exacqVision Client, make sure the port number on the ‘Add Systems’ page matches the new port number. NOTE: The exacqVision Web Service is also a client of the exacqVision Server. Therefore, if using the exacqVision Web Service you may also be required to change the connecting port in the exacqVision Web Service Configuration.
<br><br>
<br><br>
<br><br>
<br><br>