Category: Uncategorized

Forgot password to LTS or HikVision NVR (Network Video Recorder), cannot remember template pattern to login to NVR as admin.

In order to recover the NVR password you would need to have physical access to the recorder and have it connected it to a network.

In order to access NVR via network, download SADP Tool from https://www.hikvision.com/en/support/tools/hitools/
Copy/paste the link

Once installed, scan the network and you’d see your NVR on the list. You will find the NVR’s IP address. If the IP is dynamic, you can try connecting to it using SADP Tool. Click on the list to have is highlighted/selected and on the bottom right click Recover password.

Important: make sure you can leave the laptop running till the very end (keep reading) without disconnecting.

Should you encounter an error, change configuration of your laptop/computer to match IP network, but in your computer’s network settings make Gateway be your NVR’s IP address. For example: if you NVR network settings are:
IP: 192.168.0.170, Mask: 255.255.255.0, Gateway: 192.168.0.1

Change your computer’s network configuration to:
IP: 192.168.0.180, Mask: 255.255.255.0, Gateway: 192.168.0.170

DNS servers are not important in this case.

Once you are connected to the NVR, the main point is to export an XML file and have it sent to LTS’s technical/customer support. They’d send you another XML file back to you and you would have to import it into the NVR in order to reset the admin password.

When importing the file you might encounter different errors:

After many trials and errors the main solution seems to be:

Leave the computer/laptop and NVR running for the entire duration of the endeavor! Do not disconnect/power cycle the devices, do not turn off SADP Tool, do not disconnect network switches. WAIT until the customer service sends you the final password reset file. The turnaround is normally from an hour to a business day, depending when you catch the support rep.

PHP 5+

(condition) ? /* value to return if condition is true */ 
            : /* value to return if condition is false */ ;

syntax is not a “shorthand if” operator (the ? is called the conditional operator) because you cannot execute code in the same manner as if you did:

if (condition) {
    /* condition is true, do something like echo */
}
else {
    /* condition is false, do something else */
}

PHP 7+

As of PHP 7, this task can be performed simply by using the Null coalescing operator like this :

 <?php
// Fetches the value of $_GET['user'] and returns 'nobody'
// if it does not exist.
$username = $_GET['user'] ?? 'nobody';
// This is equivalent to:
$username = isset($_GET['user']) ? $_GET['user'] : 'nobody';

// Coalescing can be chained: this will return the first
// defined value out of $_GET['user'], $_POST['user'], and
// 'nobody'.
$username = $_GET['user'] ?? $_POST['user'] ?? 'nobody';
?> 

Midnight Commander has ability to connect to ftp in a pane, so it’s possible to use it to connect to a remote FTP server.

Go to Shell, execute mc and press F9 to call the menu. Select Left/Right window, select FTP Link

Enter FTP server details in one of the following formats:

username:password@host           #for non-anonymous login;
host                             #for anonymous login;
!username:password@host          #for servers behind the firewall, through proxy servers;
username:password@host:port      #for servers using non std port;
username:password@host/directory #to go to specific directory. 

Once you’ve connected to your remote FTP server, you can copy any files or folders between the panes in your Midnight Commander and any directory on your remote FTP server.

First check the status of your queue:

# /var/qmail/bin/qmail-qstat
messages in queue: 6751
messages in queue but not yet preprocessed: 56

After you find and stop the spammer, you now have a bunch of email on your QMail queue. Here’s how to remove it

take a “user@domain.com” that happens in emails from the spammer (usually the sender) and run this command:

grep -R user@domain.com /var/qmail/queue/mess/* | awk -F”:” ‘{print “rm -f ” $1}’ | sh

make sure the quotes and single quotes are straight, not round upon copy/paste

That will delete the emails that contain that user@domain.com

but it would leave behind various indexes and later on your users would start receiving bouncebacks for emails they’ve never sent!

BETTER USE:
qmHandle/qmhandle-1.3.2/qmHandle -Fuser@domain.com

this removes not only messages, but all the mentioning of those messages from everywhere. (sasa4uk)

Mysql:
======
Socket file: /var/lib/mysql/mysql.sock
Database file: /var/lib/mysql
mysql password file: /var/lib/mysql/.my.cnf
Error log: /var/log/mysql/error.log

Ftp:
=====

Proftpd is default with hsphere.

Configuration file: /hsphere/shared/config/ftpd/proftpd.conf
Log file: /hsphere/local/var/proftpd/xferlog

Php:
=====

Recently there was a spike in Authorize.net customers that reported their sites credit card processing errors which, according to log files resulted in the following error produced:

CURL ERROR: SSL certificate problem: self signed certificate in certificate chain

Fix:

• Download and unarchive SDK
  https://codeload.github.com/AuthorizeNet/sdk-php/tar.gz/2.0.0
• Find ./lib/ssl/cert.pem file in it and upload it to the server
• Find cert.pem file in their account and make a backup of it. Replace it with the cert.pem file from the previous step.

Testing (oneliner):

echo | openssl s_client -connect apitest.authorize.net:443 -showcerts -verify 10 -CAfile /home/path/to/cert.pem

Make sure to replace “/home/path/to/cert.pem” with the real path. If all is good you’ll get something like this at the end:

Verify return code: 0 (ok)

Otherwise you’ll see:

Verify return code: 19 (self signed certificate in certificate chain)