-
Notifications
You must be signed in to change notification settings - Fork 44
Patches
| Patch | Release Date | Template Application |
|---|---|---|
| Node.js v14.x (0.8.0 Compatibility Patch) | March 23rd, 2021 | v1-1 to v1-6 |
| Certificate Renewal | January 15th, 2021 | v1-1 to v1-5 |
Deployments created prior to March 23rd, 2021 using templates v1-6 and earlier use node v12.x. Foundry VTT 0.8.6 release requires version 14.x of Node.js. Regardless of whether or not you are running 0.8.x, you can apply this patch. Make sure you create a backup of your world(s) before proceeding.
Hello! 0.8.6 STABLE has finally been released! That being said audio/video integration IS NOT WORKING at this time. This is a known bug from Foundry. If you'd like more information, you can find it in their release notes.
Official Release Notes: Foundry VTT Version 0.8.0
Reddit Thread: TLDR Reddit Thread
-
SSH into the EC2 server. If you require instructions on how to do so, follow the SSH Access Instructions.
-
When you have successfully opened a terminal to your server, type the commands after the $ sign below.
Hit return/enter after each line.$ sudo su $ wget https://raw.githubusercontent.com/cat-box/aws-foundry-ssl/master/patches/node_v14.sh $ chmod a+x node_v14.sh $ ./node_v14.sh $ rm node_v14.sh $ node -v
-
The last command from the previous step will output the current version of Node.js. If it reads
v14.x.x(x being their current stable release number), then you have successfully applied the update.
I have noticed that Foundry VTT will frequently disconnect you from the server unless worlds are updated to the latest version. This will be especially apparent if you are using the integrated audio/video function. If you are experiencing this issue, consider restarting your server after ensuring all updates have been applied.
If you find that you are experiencing an unacceptable level of bugs, you can revert to Node.js v12.x. Please remember that v12.x is not supported in the 0.8.0 Foundry VTT release. Reverting to v12.x is only a temporary solution.
-
SSH into the EC2 server.
-
When you have successfully opened a terminal to your server, type the commands after the $ sign below.
$ sudo su $ wget https://raw.githubusercontent.com/cat-box/aws-foundry-ssl/master/patches/node_v12.sh $ chmod a+x node_v12.sh $ ./node_v12.sh $ rm node_v12.sh $ node -v
-
The last command from the previous step will output the current version of Node.js. If it reads
v12.x.x(x being their current stable release number), then you have successfully reverted to v12.x
Deployments created prior to Jan 15th, 2021 using templates v1-5 and earlier do not auto-renew SSL certificates due to a bug. This has been resolved in a patch which needs to be manually applied.
-
SSH into the EC2 server. If you require instructions on how to do so, follow the SSH Access Instructions.
-
When you have successfully opened a terminal to your server, type the commands after the $ sign below.
Hit return/enter after each line.$ sudo su $ wget https://raw.githubusercontent.com/cat-box/aws-foundry-ssl/master/patches/certbot_cronjob.sh $ chmod a+x certbot_cronjob.sh $ ./certbot_cronjob.sh $ rm certbot_cronjob.sh
-
Reboot your server or wait until 12PM UTC the next day for certificate auto-renewal.
There are two methods to check the status of your certificate, via crt.sh or terminal.
- Type in your domain (e.g. example.com).
- On auto-renewal success, the top entry's "Logged At" column will be dated close to the date of your patch application.
-
SSH into the EC2 server.
-
When you have successfully opened a terminal to your server, type the commands after the $ sign below.
Hit return/enter after each line.$ sudo su $ certbot certificates
-
Check the "Expiry Date" line. An example output has been provided below.
Found the following certs: Certificate Name: example.com Serial Number: [serial number here] Key Type: RSA Domains: foundry.example.com Expiry Date: 2021-04-16 12:00:00+00:00 (VALID: 89 days) Certificate Path: /etc/letsencrypt/live/foundry.example.com/fullchain.pem Private Key Path: /etc/letsencrypt/live/foundry.example.com/privkey.pem