Troubleshooting
The script didn't answer
When you create a prototype, Commmenty loads its address and waits up to 12 seconds for the script. The script didn't answer on this URL usually means one of these:
- The change with the script isn't deployed to that address yet. Deploy it, or check that you pasted the address of the deployment that has it.
- The prototype sends a
Content-Security-Policywithoutframe-ancestors https://app.commmenty.com, or it sendsX-Frame-Options. See Allow Commmenty to frame it. - The script's
data-pf-origindoesn't point tohttps://app.commmenty.com. The prototype's browser console says so. - In Next.js, the tag is a plain
<script>instead ofnext/script.
You can choose Create anyway and fix it later.
The snippet has the wrong key
| Message | What to do |
|---|---|
| The snippet on this URL has no key. | Deploy the snippet from this prototype, which includes data-pf-key. |
| The snippet on this URL has a key that was rotated. | Deploy the new snippet from the prototype's page. |
| The snippet on this URL carries the key of a prototype on another site. | Use this prototype's snippet. |
| The snippet on this URL has a key that matches no account. | Copy the snippet from Commmenty again and deploy it. |
| This URL belongs to another Commmenty account. | The site is set up under someone else's account. Ask them, or choose Request access. |
The prototype doesn't open in the viewer
- This prototype must be served over HTTPS. Deploy it to an https address. Plain http works only on
localhost. - This prototype needs the updated snippet. The deployed script is missing its key or has an old one. Copy the snippet and deploy it. Prototypes created before 15 November 2026 open without a key until 15 December 2026.
- This prototype isn't linked to a Commmenty account. The script's key belongs to no prototype. Use the snippet from the prototype's page.
- Nothing heard from embed.js. The viewer got no answer from the script after a few seconds. The script isn't running in the prototype, or its
data-pf-originpoints somewhere else. - This prototype didn't open. Choose Retry. If it keeps happening, check the prototype loads on its own.
If you shared the prototype and your client says commenting is off, it's usually one of the above: they see This prototype isn't answering, so commenting is off for now.
The Comment button is greyed out
The tooltip Waiting for embed.js inside the prototype means the script hasn't answered yet. If it stays that way, see the section above. This version is read only means you're on an earlier version; switch to the current one.
Comments show up on the wrong screen
The prototype changes screens without changing its URL, so Commmenty sees them as one screen. Give each screen its own URL, as in One URL per screen. Comments left before the change stay on the URL they were left on.
A link doesn't open
- This prototype has expired or Access to this prototype is off: whoever shared it closed it. Ask them to open it again.
- Log in to open this prototype: the prototype is private. Open the link in the invitation email, or log in with the account it was shared with.
- This invite doesn't open anything now: ask whoever shared it to send it again.
I was signed out
Accounts are signed out after 2 hours without activity, or 30 days with Keep me signed in on this browser. Guests stay signed in for 7 days after their last visit, or what the prototype's owner set under Guests stay signed in; then they open the link they were sent again.
Commmenty asks me to switch to a computer
There's no phone version yet. Open the link on a computer.
Still stuck
Use Give us feedback in the app, or write to hello@commmenty.com.