Troubleshooting

by Game Master· published November 8, 2026 at 10:20 PM

Setup Wizard messages

  • GitHub rejected the token: the token was copied incompletely or has expired. Create a new one (Setup Wizard step 2) and paste it again.

  • Couldn't find owner/repo: check the spelling of your GitHub username and the repository name. If both are right, the token wasn't given access to this repository: edit the token on GitHub and add the repository under Only select repositories.

  • Doesn't have the "Contents" permission: edit the token on GitHub and set Contents to Read and write.

  • No branch named "main": if your hosting provider only just created the repository, wait a minute and try again.

My site doesn't show my posts

  1. Check that the Publish to Web button is green. If it's orange, click it.

  2. Check that the journal has Publish this journal to the web checked, and the page shows a checkmark.

  3. Wait a few minutes, then reload the site. Your host has to rebuild it after each publish.

  4. Open your hosting provider's dashboard and look at the latest deploy. If it failed, its log says why.

My first deploy failed with "ENOENT" or "Could not read package.json"

GitHub sometimes hasn't finished copying a brand-new repository when the host first builds it. It fixes itself on your first Publish to Web.

Publishing stopped working after a while

Your token probably expired. Create a new one with the Setup Wizard. Step 1 warns that it will create a new site; to keep your existing site instead, create a new token on GitHub and paste it into GitHub Personal Access Token in Configure Settings.

I updated World2Web but my site looks the same

Your site updates on your next Publish to Web after the module update, not when you install it. Publish once, and look for the notification that your site is being updated. If there's no such notification, check that Keep Site Up to Date is on in the module settings.

Still stuck?

Report a problem at github.com/gludington/world2web/issues.