Troubleshooting Provider Appliance - Revision history

Regify: /* Other log entries */

2025-08-12T07:49:57Z

Other log entries

Regify: /* Short explanation about the counting */

2025-01-23T08:47:46Z

Short explanation about the counting

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

2025-01-07T09:25:06Z

The websock server is stuck, lwsws utilizes all CPU

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

2025-01-03T12:14:48Z

The websock server is stuck, lwsws utilizes all CPU

Regify: /* Handle known appliance problems */

2025-01-02T17:17:11Z

Handle known appliance problems

Regify: /* Check bandwidth usage */

2024-03-12T07:17:27Z

Check bandwidth usage

Regify at 16:17, 11 March 2024

2024-03-11T16:17:40Z

Regify: /* Many people complain that they do not receive the portal e-mails */

2024-01-31T09:01:46Z

Many people complain that they do not receive the portal e-mails

Regify: /* Restore backup */

2022-12-08T16:00:16Z

Restore backup

Regify: /* Restore backup */

2022-10-05T10:31:40Z

Restore backup

← 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/

@@ Line 148: / Line 148: @@
   svc -k /service/lwsws/
   ps ax | grep lwsws         // wait and check until /usr/bin/lwsws is gone
   svc -u /service/lwsws/
 == How to fix broken cross-master replication ==

← 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.

← Older revision		Revision as of 09:01, 31 January 2024
Line 11:		Line 11:

	If all looks good, there is nothing more you can do. But please note that some missing e-mails from a few hundred or even thousands is normal. And even the most perfect configured email sending system does not prevent your emails from getting sorted out as spam. Spam filters are mainly based on training . Therefore, if and why regify messages are classified as spam or not is very specific to the recipient.		If all looks good, there is nothing more you can do. But please note that some missing e-mails from a few hundred or even thousands is normal. And even the most perfect configured email sending system does not prevent your emails from getting sorted out as spam. Spam filters are mainly based on training . Therefore, if and why regify messages are classified as spam or not is very specific to the recipient.
		+
		+	==== Reverse DNS ====
		+	Please note that reverse dns records must be managed by the owner of the IP address. Therefore, it is very likely not on you to handle this in your DNS. You need to contact the hoster of your solution or the internet provider of your company in order to get such reverse dns record.
		+
		+	==== DMARC ====
		+	You may want to add a ''_dmarc'' TXT record to your DNS server. To get basic functionality (passing everything) you can start with some TXT record like
		+
		+	v=DMARC1; p=none
		+
		+	for the domain '''_dmarc.[yourdomain]'''. More information is [https://mxtoolbox.com/dmarc/details/what-is-a-dmarc-record here at MX toolbox].

	=== What exactly happens during registration and invitation? ===		=== What exactly happens during registration and invitation? ===

@@ Line 216: / Line 216: @@
 === Restore backup ===
-Provider the backup to the new machine. We prefer rsync or scp. Here is an example scp call:
+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 sue to be root.
+Now log in to your new appliance and make sure to be ''root''.
-Restore the machup using this command:
+Restore the backup using this command:
   /usr/libexec/regify-provider-app/restore -i <PROVIDERID> /tmp/backup.enc

← Older revision		Revision as of 10:31, 5 October 2022
Line 228:		Line 228:
	You will be prompted for the CLEARINGPASS password. Upon correct password was entered, the backup is restored and the configuration is updated.		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. Upon this, you can restart the webserver using "Provider..." -> "Start SSL...".	+	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...".