From ac370e2edaab6a07f7dc2b0ebcb6b62da4775c29 Mon Sep 17 00:00:00 2001 From: Tuomas Suutari Date: Thu, 1 Aug 2024 17:36:32 +0300 Subject: [PATCH] panel/1.0/troubleshooting: Add note about cert expiration Expired certificate can create an error that looks like a general communication error, since websocket or XHR requests just fail in very similar way like the service was not responding at all. This could be a quite common case, especially if the certificate renewal (e.g. for Let's Encrypt) is not properly set up. --- panel/1.0/troubleshooting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/panel/1.0/troubleshooting.md b/panel/1.0/troubleshooting.md index 55eddbc03..e31301641 100644 --- a/panel/1.0/troubleshooting.md +++ b/panel/1.0/troubleshooting.md @@ -70,6 +70,7 @@ and `2022` for SFTP traffic. https://domain.com:8080` on the Panel server and ensure that it can successfully connect to Wings. * Ensure that you are using the correct HTTP scheme for your Panel and Wings. If the Panel is running over HTTPS Wings will also need to be running on HTTPS. +* If using HTTPS for Wings, make sure that the certificates have not expired. ### More Advanced Debugging Steps * Stop Wings and run `wings --debug` to see if there are any errors being output. If so, try resolving them manually,