Accessing Foundry
If you got this far, you should have a Foundry server that should be fully integrated with S3 storage with SSL Encryption.
Lets go through a checklist to make sure you're fully set up. If you run into any problems, take a look at the Troubleshooting section below.
- If you chose to host content on your domain, you can access it through the browser e.g. example.com
- You can access your subdomain through the browser e.g. foundry.example.com
- You see a little lock in the address bar. If you click on it, it shows a secure connection.
- You are able to use your webcam and microphone in foundry.
If you checked everything off, you're all set to go! Make sure to check for patches if you run into any bugs down the line. That's it from me, enjoy! 🥳
So... despite all my testing, your server doesn't work. Before you create an issue, take a gander through the troubleshooting section. I've tried to help you narrow down what to look for if a specific component isn't working.
- Deployed Template Parameters
- I can't access my domain or subdomain
- I don't see a lock
- I can't use my camera or microphone
You can review the values you input into the CloudFormation template. You'll likely need to check these once you've narrowed down the suspects from the sections below.
- Login to AWS
- Navigate to the CloudFormation dashboard by searching CloudFormation in the Services dropdown.
- You should see your foundry stack listed, click into the stack name for your deployment.
- Click Parameters. You should now see the values you input during creation.
Browsers sometimes cache information to load previously visited websites faster. After creating the website, your browser may not be aware that you've updated the site.
- Open an incognito/private window and type in the URL
- Include
https://into the address (e.g. https://foundry.example.com) - Access the site from a different device
It is possible that an error was made when inputting parameters into the template. We can narrow down some of the possibilities. Grab the IP address of the server and enter it into the address bar in the following format (without the square brackets): [IP Address]:30000
- [Google/NameCheap]: Double check that you have set up your record set correctly and written the exact same subdomain and domain name (if you created a webserver) values into the template parameters (deployed template parameters)
-
Have you recently changed/deleted your API Key and Secret from the domain registrar? If so, the server uses the API key and secret to update your domain registrar with its new IP. Since it can no longer do so, you have two options to fix the issue.
- Recreate the server. If you did not make snapshots, you will lose all foundry data
- SSH into the server, and as root user, edit the
/foundryssl/variables.shfile. You will need to update the appropriate API key & secret values. Refer to the parameter definitions section for more info.
-
Does your DNS record's IP value match the instance's IP?
If not, you may have incorrectly entered your API Key and Secret values. Keep in mind that API Key and Secrets are matching pairs.
- Review the download link you provided for "FoundryDownloadLink" in the template. If you're using Google Drive, double check that the file settings are approriately applied with the correct permissions.
- 👀 How long did you wait? Initial setup can take longer than you'd expect. There are a good number of scripts the server has to run through and apply. Give the server a little extra time... go grab a snack!
There are really only a few scenarios where certificates would have failed to generate.
-
How many times have you tried creating a server? Letsencrypt imposes a limit on the number of times you can request a certificate for a specific domain set. Letsencrypt provides more information on this.
[Renewals] are subject to a Duplicate Certificate limit of 5 per week... Exceeding the Duplicate Certificate limit is reported with the error message too many certificates already issued for exact set of domains... Revoking certificates does not reset rate limits, because the resources used to issue those certificates have already been consumed.
What now??? Well, you have two options.
- Wait the week out. The Google Transparency Report or crt.sh shows all issued certificates for your domain. The week long timer resets from when you made your first request of the week.
- Settle for a different subdomain name. The limit applies on sets of domain certifications. So if you change your subdomain name, it will count as a unique set.
Note: If you are also creating a webserver, you will likely have also maxed out the domain requests. In this case, you will have to wait a week since this template requests certificates separately for the subdomain and domain.
-
Letsencrypt also will not create a certificate if the server is not properly connected to the domain registrar. If you can't access the domain and/or subdomain, take a look at the section above first.
-
Make sure your connection is secure (you have the little lock next to the address bar). If your connection isn't secure, foundry's audio and visual automatically will not work.
-
The GM may need to manually turn on audio visual settings for each player, including themselves. Double check that has been approriately set.
-
Browsers will often request access to audio and video communication as a safety feature. You will need to accept this before audio and video will work.
[Google Chrome]: On the left side of the address bar, click the lock icon and then "Site settings". Change Camera and Microphone to Allow. Refresh the webpage.
[Firefox]: On the left side of the address bar, click the lock icon and then the
>arrow. Click "More Information." Click the "Permissions" tab and scroll to the bottom of the list. Locate "Use the Camera" and "Use the Microphone" and uncheck "Use Default" for both. Select the "Allow" bubble for both settings. Refresh the webpage.