Skip to main content Skip to footer

Best practices for updating Wyn and installation troubleshooting

In this article, we will focus on two topics around the Wyn Updating/Installation process.

First is the best practices when updating/ installing Wyn on a server, then second what is needed to troubleshoot the issues that may come up.

 

Best Practices:

For Updating:

First off, you always want to back up your Wyn.conf, and the WynDatabase which Wyn runs on top of. This will give you a place to roll back to if that is needed due to some complication or need to do so in the future.

This effectively gives a snapshot of all the items on the server at that time, so you will lose some data if you do need to roll back.

Secondly, for Windows server users, you should make note of make sure that you make a note of where you are installing from the .exe. As the installation logs will be present in the folder that you run it from rather than a central area.

 

For Installing:

If on Windows, make note of where you run the .exe from for the installation logs.

If on Docker, make sure you are using the correct image type from Docker. arm64 is for Mac, while the standard image is for Linux and Windows servers that host Docker.

Make sure you have all prerequisites to install Wyn, System Requirements

If using external databases to host the WynDatabase, please make sure the account you are using to access them has read and write permissions to that database server so that it can create the needed data structure. If using internal/ default installation this will all be done for you automatically

When you are working with the install always include a business email as this is needed to verify/ contact you if you are working with the 30 day trial, which is the standard state of the install unless you have a license key you can add on the admin portal.

 

When issues come up:

If you run into an issue in the installation or update process, please screenshot any errors, make note of the steps you took, and gather logs to share with the support team.

Then if you were updating please roll back your system, as to not have an outage.

From there we will reach out and share next steps.