After launch
The store is already running, and the domain, a payment, mail, an import, or a language does not match what you expect. A store that is not up yet, or is stuck on the first deploy, stays in Troubleshooting. If the case is in neither article, sign in at fatleon.com and open a support ticket.
Each row is the check, then the existing article that already has the steps.
| What you see | Check first | Read |
|---|---|---|
The domain changed. Email links, canonical tags, or the sitemap still use the old address, or still use https://live.fatleon.com. | System → Site Settings, Site URL. An empty value falls back to url in src/config/site.config.ts. Watch the trailing slash, and watch a www host and the root domain both being saved as the public address. | System and global settings and Search and extra hostnames |
| The customer has paid in Stripe or PayPal. The admin still shows Pending Payment. | The webhook has to be the shop domain the customer is using now: https://{shop-domain}/api/webhooks/payments/stripe or https://{shop-domain}/api/webhooks/payments/paypal. After a domain change, an endpoint left on *.amplifyapp.com, a preview branch, or a Lambda Function URL is no longer called. The event types and the signing secret or Webhook ID still have to be saved. | Mail and payments and Payments |
| Checkout on the live store still marks an order paid in one click, or still accepts a test card. | Payment Settings still has Mock turned on, or Stripe is still on pk_test_ / sk_test_. | Payments |
| Opening the store asks the browser for an Amplify username and password. | Hosting → Access control is still on. After you turn it off, start a new build from the repository. The password gate comes off when that build finishes. | Basic auth while you set up the store |
| An import is rejected. | theme in that folder's official-pack.json and officialImportTheme in src/config/site.config.ts differ. | Sample data and Data preparation and import |
| After an import, the store name and logo are the demo values again. | The demo site-settings folder was imported into a store that was already configured. | Import order |
| You replaced a homepage or page-layout image and the storefront still shows the old one. | Those images are banner rows under Content. Save the row for the language you are viewing. A logo or favicon file replaced in the repository waits for the next Amplify build. | Where to change the storefront |
| Product photos are missing. The logo is still there. | Product photos go through import or the admin, into S3 under admin-pictures/. The default logo and favicon live in public/frontend/ until Site Settings replaces them. | Sample data and Backend |
| A language is enabled in the admin, and its public URL comes back in English. | Installed and enabled are two layers. A public URL for an installed locale that is not enabled returns 308 to en. A language missing from the language screen entirely is not in locales in src/config/site.config.ts. The admin cannot add it. | Storefront locales |
The last admin is gone, and /setup does not appear. | /setup stays closed. In the Cognito console, add the user back to Admins. | First admin |
| A test message from the admin arrives. The customer receives no sign-up mail or order mail. | SMTP is saved. Check the sender, and which statuses are enabled under Order emails. Until you change that list, the messages are Processing and Shipped. Claiming the first admin does not send mail. |
A domain that has just moved onto your own hostname shows up in three rows above: Site URL, the webhook address, and Basic auth. Each row links to the article that already has the steps.