What are you trying to do? (please be as specific as possible and include relevant screenshots, code snippets)
Im trying to publish site to custom domain we’ve just set up.
What are the reproduction steps?
Relevant links:
Hi! @verifi_me-website
Usually it takes some time for the changes to take effect when you buy a new domain name, have you configured it right before attempting to deploy?
Can you also try to delete the plasmic.run subdomain before pushing to the custom domain?
yeah but ive waited a couple of hours to try again. Still not working.
Ive removed all domains and set up custom domain again just now but still not working at all.
Not sure what im doing wrong here?
I’ve built my personal portfolio using plasmic and im not a newbie. This has never happened before.
@verifi_me-website sorry for the late reply - if you’re still having trouble, you can try:
1. Remove plasmic hosting from publish modal
2. Add plasmic hosting again, making sure not to set a plasmic.run subdomain
3. Publish with only your custom domain
Hi Samuel,
Ive tried that but it’s still failing
I am at a loss, not sure what else to do here.
Please help….
Hi, sorry for the delay - can you try again? I manually fixed the deploy settings for your site.
Hi Samuel,
It’s still not working.
The config still says it’s configured correctly and yet when I redeploy, it’s still failing.
Is there anything else we can try?
Hi @verifi_me-website, I see that Vercel is returning a "forbidden” error when we try to set up the domain. Have you added this domain to another Vercel account?
As a quick workaround, can you try adding the following TXT record to
Name: _vercel
Value: vc-domain-verify=newsite.verifime.com,20ea600463ad8a1a8a58
I’m not sure this will fix the problem immediately, it may not be possible to use a domain that is currently associated with a Vercel account.
This is a bug in the UI though, it should have shown you an error when you added the domain in the first place.
Ok so according to our tech support, we have portal.verifime.com deployed to vercel.
We have added the TXT record to newsite.verifime.com but it did not work.
This is what our tech support has sent me to attach.
dig _vercel.newsite.verifime.com TXT
; <<>> DiG 9.10.6 <<>> _vercel.newsite.verifime.com TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2064
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_vercel.newsite.verifime.com. IN TXT
;; ANSWER SECTION:
_vercel.newsite.verifime.com. 60 IN TXT "vc-domain-verify=newsite.verifime.com,20ea600463ad8a1a8a58"
;; Query time: 43 msec
;; SERVER: 192.168.4.1#53(192.168.4.1)
;; WHEN: Thu Nov 27 14:06:17 NZDT 2025
;; MSG SIZE rcvd: 156
Does this mean we cannot use plasmic hosting with this domain at all? Ideally, we would like to be able to use standard plasmic hosting. Please help.
Thank you
@verifi_me-website I believe it should be possible to deploy to Plasmic hosting, but the TXT record needs to be on the domain root, sorry for being unclear previously:
_vercel.verifime.com. 60 IN TXT "vc-domain-verify=newsite.verifime.com,20ea600463ad8a1a8a58"
You will also have to be careful to avoid removing the domain from the Plasmic site, it may reset Vercel’s verification. If this doesn’t work I’ll see if there’s any alternative.
Hi Samuel,
Thanks for quick reply. I’ve sent this new information to our tech team but they said we should not add any TXT record to our root domain for security reasons.
Is there any other workaround we can try?
Unfortunately this is a requirement from Vercel for their domain verification process. There’s nothing else we can do on our end, but maybe you can reach out to their support?
Otherwise I recommend setting up a loader project and deploying to Vercel under the same account as portal.verifime.com.