Failed deploy on nextjs app - Unable to call /api/revalidate

Just a normal deploy after creating a new project results into not being able to deploy to custom domain.

Repro steps:

  1. Create new project
  2. Choose template - Professional services
  3. Choose NextJS
  4. Configure custom domain
  5. Publish

Result:
Save a new version:

Successfully saved Vesna’s web page v1.0.2!
Pushed updates to CDN cache!
Publish to Plasmic Hosting
Deployed to vesnamalinova.plasmic.run
Failed deploy to v2.vesnamalinova.com: Unable to call /api/revalidate.

v2.vesnamalinov.com shows
404: NOT_FOUND
Code: DEPLOYMENT_NOT_FOUND

Dev tools:
Request of interest - https://studio.plasmic.app/api/v1/revalidate-hosting

Payload:
projectId: “sZaKH4irD9a3r8VoQ35nJS”

Response:

{
    "successes": [
        {
            "domain": "vesnamalinova.plasmic.run"
        }
    ],
    "failures": [
        {
            "domain": "v2.vesnamalinova.com",
            "error": {
                "type": "Invalid JSON response"
            }
        }
    ]
}

Relevant links

  1. Plasmic project
  2. Similar issues, but no resolution:
    1. Unable to deploy to Plasmic hosting - Plasmic Studio Questions - Plasmic Community
    2. Unable to deploy project to custom domain - Plasmic Studio Questions - Plasmic Community
    3. Deploy failed on non-www domain - Issues - Plasmic Community
    4. Failed to Publish / Deploy to Plasmic Hosting - Issues - Plasmic Community

@jason any help would be greatly appreciated here :folded_hands:

cc @alex_noel @samuel_pullman

Hi @drag_dim, the problem is that the root domain (vesnamalinova.com) appears to be connected to a Vercel account. We also use Vercel for Plasmic hosting, and they don’t allow connecting subdomains to different accounts without manual verification.

We’re looking into ways to solve this and improve documentation about Plasmic hosting, but currently the only solution would be for you to host v2.vesnamalinova.com in the same project as vesnamalinova.com (instead of via Plasmic).

1 Like