Bad port: "6566" is reserved for sane-port
Not sure if it is possible to filter the automatically assigned port during deployments?
5 Replies
Project ID:
497a7953-e85b-4044-b984-112dc9defad9497a7953-e85b-4044-b984-112dc9defad9
This had happened with one of my projects, wait a bit and redeploy. It goes away
I figured a redeploy would work - but since it is a known reserved port for Next.js applications, maybe it could be filtered from the automatically generated port during build/deployment?
correct 👍