Troubleshooting Provider Appliance - Revision history

Regify: /* Restore backup */

2026-05-05T10:34:54Z

Restore backup

2026-05-05T10:34:19Z

Make backup

2026-05-05T09:58:10Z

Restore backup

2025-08-12T07:49:57Z

Other log entries

2025-01-23T08:47:46Z

Short explanation about the counting

2025-01-07T09:25:06Z

The websock server is stuck, lwsws utilizes all CPU

2025-01-03T12:14:48Z

The websock server is stuck, lwsws utilizes all CPU

2025-01-02T17:17:11Z

Handle known appliance problems

2024-03-12T07:17:27Z

Check bandwidth usage

2024-03-11T16:17:40Z

@@ 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

@@ Line 243: / Line 243: @@
 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 ==

← Older revision		Revision as of 07:49, 12 August 2025
Line 111:		Line 111:

	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.		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.
−
−	~~=== Other log entries ===~~
−
−	~~PHP Warning: htmlentities(): Invalid multibyte sequence...~~
−	~~PHP Warning: htmlspecialchars(): Invalid multibyte sequence...~~
−
−	~~This happens more often since provider V3.4.0. We are investigating the problem.~~

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

@@ Line 62: / Line 62: @@
 *# active ''regimail professional'' members and
 *# above the free 30 days period (regify does not charge for the first 30 days) and
-*# maxtransaction setting is less or equal the provider-default an
+*# ''maxtransaction'' setting is less or equal the provider-default and
 *# ungrouped and
 *# not a regimail mass sender

@@ Line 143: / Line 143: @@
 === The websock server is stuck, lwsws utilizes all CPU ===
-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.
+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:
   svc -k /service/lwsws/
-  ps ax | grep lwsws         // wait and check until /usr/bin/lwsws is gone
+  tports | grep lwsws        // must return nothing. If ports 7681 or 7682 are still listed, lwsws is not stopped yet
   svc -u /service/lwsws/

← Older revision		Revision as of 17:17, 2 January 2025
Line 140:		Line 140:
	In order to fix this, log in as root (or drop to shell and use ''su root''). Now, execute the following:		In order to fix this, log in as root (or drop to shell and use ''su root''). Now, execute the following:

		+	svc -u /service/lwsws/
		+
		+	=== The websock server is stuck, lwsws utilizes all CPU ===
		+	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:
		+	svc -k /service/lwsws/
		+	ps ax \| grep lwsws // wait and check until /usr/bin/lwsws is gone
	svc -u /service/lwsws/		svc -u /service/lwsws/

@@ Line 248: / Line 248: @@
   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
-Run it like this:
+'''NOTE:''' You cannot use a more recent version of ''bandwhich'', because the newer versions require more recent ''glibc'' versions.
   ./bandwhich -n
-You stop it with the q key. Please remove the tool after you finished.
+'''NOTE:''' The '''-n''' parameter stops the tool from querying DNS for every IP address. It is of no use and also causes traffic.

← Older revision		Revision as of 16:17, 11 March 2024
Line 241:		Line 241:

	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 ==
		+	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
		+
		+	Run it like this:
		+	./bandwhich -n
		+
		+	You stop it with the q key. Please remove the tool after you finished.