At times is may be necessary to change the exacqVision Web Server Logging Level. By far the most common usage is changing from the default Error logging level to Debug and then back again.
Product
exacqVision Web Server
Solution
In order to assist with troubleshooting exacqVision Web Server issues it is sometimes useful to increase the verbosity of the log files by changing the log level. Once the necessary information has been gathered it is good practice to change the log level back to the default, Error Logging Level.
Change to Debug Logging Level
From Web Service Configuration
Navigate to Configuration, then Logging
Click the dropdown and change the Logging Level to Debug
Apply the change and restart Web Service
Return to the Landing Page
Force or wait for the issue to recur.
Change to normal (Error Logging Level)
From Web Service Configuration
Navigate to Configuration, then Logging
Click the dropdown and change the Logging level to Error
This is not an exhausted list. Soft Triggers are not available in the Web Browser/Thin Client. Customers should use the Exacq Mobile 3 Client from a Web Browser instead.
The physical triggers are located in the menu of the mobile browser instead of on the live view.
For Example: If you are using a trigger for audio and the associations have been created. Connect to the Exacq Mobile 3 Client in a browser, navigate to the menu options, go to the Audio Devices, select Audio Input, and select Listen in Live. In the lower right corner you will see the option for activating that soft trigger.
How to diagnose if the Fast Reverse Proxy Client (FRPC) is the source of issues with the ExacqVision Web Server relay service.
Product
ExacqVision Web Server
Troubleshooting FRPC
FRPC provides a proxy service for Relay Connections used by ExacqVision Web Server. This eliminates the need for firewall configuration and prevents exposing the NVR directly to inbound internet traffic via port forwarding by creating a unique public relay URL.
Some antivirus software may identify this client as a threat and will block, remove, or prevent the installation of FRPC.
This usually manifests itself with issues either in initial setup of the relay service or when existing relay services stop working.
To confirm, check the ExacqVision Web Server logs for entries similar to the following:<br><br>
2021-06-15T10:02:51.215-0400 error failed to launch relay proxy client: file: frpc.exe not found
<br><br>Next confirm that FRPC is present in the appropriate install folder.
The default install locations are:
Windows C:\Program Files\exacqVision\WebService\bin\frpc.exe
Linux /usr/local/exacq/webservice/bin/frpc
Note: In some cases users may need to add relay.exacq.net to the allow list in their firewall.
By default, exacqVision Web Service restricts configuration to the browser on the local machine. Through the configuration, a user can disable this restriction to enable remote configuration. However, there could be a need to manually remove this restriction (such as when installing the Web Service in a virtual environment, such as exacqVision Virtual).
<br>
To manually enable remote configuration, complete the following steps:
<br>
NOTE: These instructions assume that the file to edit does not contain any text. If it has previously been changed, merge the changes specified here into the existing file.
With administrator credentials, open the file .evws-login for editing. By default, this file is found in Windows at C:\Program Files (x86)\exacqVision\WebService\bin\.evws-login, or in Linux at /etc/.evws-login.
Add the following into the file:
[Settings] restricttolocalhost = 0
Save the file.
Restart the Web Service.
<br>
After restarting, the Web Service will have remote administration enabled.
<br>
You can also use the Web Service Configuration page to deselect the Enable Localhost Restriction option.
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
Open a web browser on the server and type http://127.0.0.1 as the URL to access the Web Service. Click on the Web Service Configuration link in the bottom-right corner. <br><br>
Enter the Web Service administrator username and password to log in.<br><br>
Edit the port number to match the custom port number configured for your server.
For Web Service version 7.8 and above: Open the Server Connections page, click Add Server to add a new server, or highlight an existing entry and click Edit. <br><br>
For Web Service version 7.6 and earlier: Open the Servers page and type the new port over the existing port. Click on Update Configuration and then confirm to restart the Web Service.
<br><br>
<br><br>