Troubleshooting Provider Appliance - Revision history

Regify: /* Check bandwidth usage */

2026-09-17T09:25:24Z

Check bandwidth usage

Regify: /* Some IP address was blocked by accident */

2026-09-17T09:24:35Z

Some IP address was blocked by accident

Regify: /* Clearing Related */

2026-09-17T09:23:28Z

Clearing Related

Regify: /* Security Related */

2026-09-17T09:20:04Z

Security Related

Regify: /* Appliance diagnostics */

2026-09-17T09:19:24Z

Appliance diagnostics

Regify: /* The websock server is stuck, lwsws utilizes all CPU */

2026-07-30T13:45:53Z

The websock server is stuck, lwsws utilizes all CPU

Regify: /* Handle known appliance problems */

2026-07-30T13:35:59Z

Handle known appliance problems

Regify: /* Restore backup */

2026-05-05T10:34:54Z

Restore backup

Regify: /* Make backup */

2026-05-05T10:34:19Z

Make backup

Regify: /* Restore backup */

2026-05-05T09:58:10Z

Restore backup

← Older revision		Revision as of 09:25, 17 September 2026
Line 234:		Line 234:

	5) Upon this, you can '''restart the webserver using "Provider..." -> "Start SSL..."'''.		5) Upon this, you can '''restart the webserver using "Provider..." -> "Start SSL..."'''.
−
−	~~== Check bandwidth usage ==~~
−	~~Install the '''bandwhich''' tool in home folder (temporary use only, please):~~
−
−	~~cd ~~~
−	~~wget https://github.com/imsnif/bandwhich/releases/download/0.20.0/bandwhich-v0.20.0-x86_64-unknown-linux-musl.tar.gz -O - \| tar -xz~~
−
−	~~'''NOTE:''' You cannot use a more recent version of ''bandwhich'', because the newer versions require more recent ''glibc'' versions.~~
−
−	~~Now, run it like this:~~
−	~~./bandwhich -n~~
−
−	~~'''NOTE:''' The '''-n''' parameter stops the tool from querying DNS for every IP address. It is of no use and also causes traffic.~~
−
−	~~You stop it with the '''Q''' key.~~
−
−	~~Please remove the tool after you finished.~~

← Older revision		Revision as of 09:24, 17 September 2026
Line 132:		Line 132:

	'''Notes:''' svc -k kills the process, svc -u restarts it		'''Notes:''' svc -k kills the process, svc -u restarts it
−
−	~~=== Some IP address was blocked by accident ===~~
−	The regify provider 6.0 and higher is automatically creating a blocking firewall entry, if some IP is trying to scan or attack the system. The IP is blocked for about one hour and is then automatically removed. If you really need to unblock before, you can execute this on the provider command shell:
−
−	~~nft delete element inet main blocked_ips { <IP> }~~
−
−	~~Replace <IP> with the IP address you want to unblock.~~

	== How to fix broken cross-master replication ==		== How to fix broken cross-master replication ==

@@ Line 73: / Line 73: @@
 == Common messages in appliance error log ==
-  CRIT: Failed URL: https://dc1.regify....  [Error executing curl call (0)....]
+  CRIT: Failed URL: https://dc1.clear-center.eu/...
-  CRIT: Locked connection-id 1. Check /opt/provider/REGIFY_INCLUDE/../ClearingLock.dat [....]
+  CRIT: Locked connection-id 1. Check /var/lib/regify-provider/ClearingLock.dat ...
   CRIT: clearing connection 1 still not available [....]

← Older revision		Revision as of 09:20, 17 September 2026
Line 100:		Line 100:

	This means that <u>all</u> defined clearing connections are found as working (mostly after one or more connections have been locked before).		This means that <u>all</u> defined clearing connections are found as working (mostly after one or more connections have been locked before).
−
−	~~=== Security Related ===~~
−
−	~~CRIT: Wrong session-host for url /downloads.php?lg=EN / /downloads.php called by xxx~~
−
−	We currently do not know the origin of this problem. It looks like someone with an old cookie (maybe wrong system time) is trying to connect to your provider with this old cookie. As the session is already finished on the provider, this entry is created. You can ignore this. But if you know the origin of this, please contact us. We are interested in investigating this issue.
−
−	~~PHP Warning: session_start(): The session id is too long or contains illegal characters, valid characters are a-z, A-Z, 0-9...~~
−	~~PHP Warning: Unknown: The session id is too long or contains illegal characters, valid characters are a-z, A-Z, 0-9...~~
−	~~PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct~~
−	~~PHP Warning: Unknown: Input variables exceeded 1000.~~
−
−	All these entries are coming from intrusion attempts by hackers. Mostly some hacker-tools are testing if systems are vulnerable on such attacks. Currently, the regify provider is not affected but it triggers such kind of entries. You can ignore and delete such entries.

	== Handle known appliance problems ==		== Handle known appliance problems ==

@@ Line 38: / Line 38: @@
 == Appliance diagnostics ==
 If you want the regify support to help you on a specific appliance issue (eg IP addresses, SSL certificates, E-Mail), please go to your SSH appliance menu and visit '''Appliance -> Other Settings -> Support Diagnostics'''. Please enter an e-mail address as destination. This will send the appliance configuration to the given address. Passwords and sensitive information are not part of this report.
 == How are the regify invoices calculated? ==

@@ Line 138: / Line 138: @@
 We've seen this once. The lwsws process used 98% CPU and the provider warned '''Websock server for regibox not running'''. The reason is unknow, memory was available.
-The following methods successfully restarted the websocket server:
+The following methods successfully restarted the websocket server (only provider 5):
   svc -k /service/lwsws/
   tports | grep lwsws        // must return nothing. If ports 7681 or 7682 are still listed, lwsws is not stopped yet

← Older revision		Revision as of 13:35, 30 July 2026
Line 144:		Line 144:

	'''Notes:''' svc -k kills the process, svc -u restarts it		'''Notes:''' svc -k kills the process, svc -u restarts it
		+
		+	=== Some IP address was blocked by accident ===
		+	The regify provider 6.0 and higher is automatically creating a blocking firewall entry, if some IP is trying to scan or attack the system. The IP is blocked for about one hour and is then automatically removed. If you really need to unblock before, you can execute this on the provider command shell:
		+
		+	nft delete element inet main blocked_ips { <IP> }
		+
		+	Replace <IP> with the IP address you want to unblock.

	== How to fix broken cross-master replication ==		== How to fix broken cross-master replication ==

@@ Line 230: / Line 230: @@
 === Restore backup ===
 Copy the backup to the new machine. We prefer rsync or scp. Here is an example scp call:
   scp backup.enc root@<yourProvider>:/tmp
-Now log in to your new appliance and make sure to be ''root''.
+) Now log in to your new appliance and make sure to be '''root'''.
-Restore the backup using this command:
+) Restore the backup using this command:
   /usr/libexec/regify-provider-app/restore -i <PROVIDERID> /tmp/backup.enc
@@ Line 242: / Line 243: @@
 You will be prompted for the CLEARINGPASS password. Upon correct password was entered, the backup is restored and the configuration is updated.
-You now need to enter the SSH appliance menu and re-assign the providers domains to the IP addresses.
+) You now need to enter the SSH appliance menu and re-assign the providers domains to the IP addresses.
-Upon this, you can '''restart the webserver using "Provider..." -> "Start SSL..."'''.
+) Upon this, you can '''restart the webserver using "Provider..." -> "Start SSL..."'''.
 == Check bandwidth usage ==

@@ Line 208: / Line 208: @@
 === Make backup ===
-Login using SSH and make sure to be root. Now run the following:
   /usr/libexec/regify-provider-app/makebackup -o /opt/provider/REGIFY_PUBLIC/backup.enc
-Then download the backup using a webbrowser at https://<yourProvider>/backup.enc
+) Then download the backup using a webbrowser at https://<yourProvider>/backup.enc
 IMPORTANT: Remove the backup after downloading:
@@ Line 218: / Line 219: @@
   rm /opt/provider/REGIFY_PUBLIC/backup.enc
-In order to restore it, you also need your clearing ID and password. If you do not know that any more, run the following:
+) In order to restore it, you also need your clearing ID and password. If you do not know that any more, run the following:
   cat /opt/provider/REGIFY_INCLUDE/menu_config.php