Skip to content

Conversation

itzMiney
Copy link
Contributor

I rewrote the first step in advanced troubleshooting steps to use sudo wings diagnostics to stop people from overreading the Stop Wings part and creating duplicate instances of Wings. Most useful errors for debugging get logged on a normal run anyways so the diagnostics command makes more sense in my opinion.

@@ -73,7 +73,7 @@ https://domain.com:8080` on the Panel server and ensure that it can successfully
* 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,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe amend to keep the top line, but with a caveat of if wings are NOT running as a system service? I like the second line though so can keep this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants