Troubleshoot Connectivity - Revision history

Regify: /* Error 59 */

2026-02-19T09:35:08Z

Error 59

2025-05-27T10:11:47Z

Error 58

2025-05-27T10:11:19Z

Error 58

2025-05-27T10:09:27Z

General connectivity information

2021-02-24T14:12:40Z

I still have problems

2020-02-14T15:18:43Z

Error 52

2018-05-23T15:59:33Z

General connectivity issues

2018-05-23T15:59:03Z

What proxy types are supported?

2018-05-23T15:58:08Z

What domains do I need to white-list for regify usage?

2018-05-23T15:55:22Z

Error 52

@@ Line 71: / Line 71: @@
 ** Make sure it does not block the regify software from the Internet!
 ** If it does, please allow Internet access to the regify software! We don't know all software, so we can't help you on this topic.
 * '''Mobile:'''
 ** Is mobile data plan activated? WLAN turned on?

@@ Line 55: / Line 55: @@
 ==== Error 58 ====
 No Internet connection. It is a generic connectivity issue. Check if you are connected to the Internet and if your operating system is up to date.
 In many cases, the same help applies as for error 59 (below).

@@ Line 55: / Line 55: @@
 ==== Error 58 ====
 No Internet connection. It is a generic connectivity issue. Check if you are connected to the Internet and if your operating system is up to date.
 In many cases, the same help applies as for error 59 (below).

@@ Line 20: / Line 20: @@
 === What ports is regify using? ===
 In order to allow regify to work, you need to allow regify to access the Internet on TCP/IP ports 443 and 80.
 === What domains do I need to white-list for regify usage? ===
-Try this tool to get all domains that need to be white-listed for regify usage:<br>[http://www.regify.com/checkWhitelist.php regify tool to determine domains for regify usage]
+Obviously the domain of your regify provider. As regify software also checks certificate revocation lists and looks for updates, try this tool to get all domains that need to be white-listed for complete regify usage with your regify provider:<br>[http://www.regify.com/checkWhitelist.php regify tool to determine domains for regify usage]
 This only applies if you are using a proxy-server that blocks Internet access to all sites that are not white-listed. In general, using regify behind such a restricted proxy is not very comfortable. This is because

← Older revision		Revision as of 14:12, 24 February 2021
Line 84:		Line 84:

	We do not suggest to use this option permanently. It is meant for debugging or testing purposes.		We do not suggest to use this option permanently. It is meant for debugging or testing purposes.
−
−	~~This is only available from regify Client V4.2, regibox Manager V1.4 and regify Desktop V2.0 or higher (mid 2016).~~

@@ Line 45: / Line 45: @@
 ===I'm having connection problems===
 ==== Error 52 ====
-Unable to verify SSL certificate revocation lists. Mostly, the proxy server does not allow the machine to access the CRL from the SSL certificates. You may need to whitelist (see above on this page).
+Unable to verify SSL certificate revocation lists or generic SSL related error. Mostly, the proxy server does not allow the machine to access the CRL from the SSL certificates. You may need to whitelist (see above on this page). Also, maybe some content inspection firewall is trying to intercept the SSL connection but the root certificate is not correctly installed for Windows.
 If you are using a '''proxy server on Windows''', please try to enter the proxy settings also to your IE/Edge configuration. regify is using the SSL backend of Windows and it seems that Windows needs a configured proxy to access the certificate revocation lists. As Windows is using IE configuration, you simply may have to enter the proxy to IE/Edge, too.

@@ Line 37: / Line 37: @@
 For authentication, the regify software supports the following authentication schemes: AUTH_BASIC, AUTH_DIGEST and AUTH_NTLM.
-For automated proxy settings, the regify software is also supporting PAC files (Proxy Auto Configuration).
+For automated proxy settings, the regify software is also supporting PAC files (Proxy Auto Configuration). This is only available on Windows and Mac.
 Please always test with the most recent regify client version!

@@ Line 23: / Line 23: @@
 === What domains do I need to white-list for regify usage? ===
-<u>'''Automatically determine needed locations'''</u>
+Try this tool to get all domains that need to be white-listed for regify usage:<br>[http://www.regify.com/checkWhitelist.php regify tool to determine domains for regify usage]
 This only applies if you are using a proxy-server that blocks Internet access to all sites that are not white-listed. In general, using regify behind such a restricted proxy is not very comfortable. This is because
@@ Line 34: / Line 32: @@
 If you are affected by such CRL issue, your debug log (regify client, regibill, regipay) or diagnostics log (regibox) is showing entries like "Unknown error 0x80092013" or similar. In such case, mostly the log shows an error message saying that the certificate revocation list was offline or nor available.
-In this case, you need to whitelist all relevant CRL locations on your proxy server.
+In this case, you need to whitelist all relevant CRL locations on your proxy server. You also may have a look below about error 52.
 === What proxy types are supported? ===