Pauline P. Narvas Can you share a chat link with us?

Genevieve 4276 Hi Pauline, the chat link is as follows: v0.app/chat/fork-of-palanquin-advisors-redesign-pVxVGYS43XK?ref=PO39A4

sergeyhayrapetyan-9496 did you ever get this sorted? curious what fixed the blank preview for you

prestockss Update: this is now resolved on our side. The production Daemon is now running the intended optimized image, and its deployment binding matches the current production deployment. A subsequent deployment containing a small frontend-only change also completed successfully, with the Daemon following that production deployment. We kept the same one-instance, 1 GiB configuration. Read-only runtime checks confirmed that the optimized query path is active and the old full-payload queries stopped increasing during our observation window. Authenticated UI checks also confirmed live holdings updates, qu

simon-7386 I also have this problem. I've uninstalled and installed the app again. When it choose scope it just goes to the github summary.

hilaltalaskurtoglu-2539 Additional information: My latest Production deployment status is Ready. The domain hilalogretmen.vercel.app shows Valid Configuration, and Production is selected. The HTTPS connection still fails on both Wi-Fi and mobile data with ERR_CONNECTION_RESET. This appears to be a TLS handshake or Vercel Edge routing issue rather than a build or DNS configuration issue. Could a Vercel engineer please investigate the Edge TLS response for this hostname?

hilaltalaskurtoglu-2539 I also deleted and recreated the domain with the same name, but the issue persists. Both the main project URL and the deployment-specific URL remain inaccessible. The deployment status is Ready, and the domain configuration is Valid Configuration. I have tested on both Wi-Fi and mobile data. The TLS handshake is reset in both cases. Please investigate this as a possible platform-level connectivity or Edge TLS issue.

TraderMigs Update, November 11, 2026: Vercel's daemon controller resumed reconciliation at 09:04:20 UTC without further operator action. The worker was replaced with an instance matching the current production deployment, and the previous worker stopped cleanly. The new worker is heartbeating, its database listener is connected, and there are no active jobs. The controller had stopped advancing its checks for approximately 5 hours 33 minutes. The current deployment's worker began approximately 2 hours 41 minutes after promotion. We have not identified the cause, and we do not know whether a subsequent pr

Swarnava Sengupta Hey, this will require Pro plan.

Swarnava Sengupta Hey This is correct. You will need Paid Pro plan for hosting such project.