Vercel's infinite loop of assigning deployment urls: Frontend & Backend
Unanswered
Amey posted this in #help-forum
AmeyOP
Hello guys,
I have 2 different repos. Frontend and Backend. I am providing both of them each others url via environment variables.
Theres a loop hole though
When i provide an unique link of frontend through environment vairable to my backend. The backend must be redeployed which generates a new unique link of backend. No this newly generated unique link of my backend, I provide it do frontend via environment variable so then frontend again must redeployed.
This goes on continuously. How do I fix this?
The bottom most is the unique link.
Another catch is. I am using jwt auth. If I using the main domain link which doesn't change on every deployment. The cookies corrects in browser.
When this exact same link of new main domain to friend / others, their browser doesn't receive cookie.
This link only works when it is being clicked on vercel's official accounnt > projects page...
I have 2 different repos. Frontend and Backend. I am providing both of them each others url via environment variables.
Theres a loop hole though
When i provide an unique link of frontend through environment vairable to my backend. The backend must be redeployed which generates a new unique link of backend. No this newly generated unique link of my backend, I provide it do frontend via environment variable so then frontend again must redeployed.
This goes on continuously. How do I fix this?
The bottom most is the unique link.
Another catch is. I am using jwt auth. If I using the main domain link which doesn't change on every deployment. The cookies corrects in browser.
When this exact same link of new main domain to friend / others, their browser doesn't receive cookie.
This link only works when it is being clicked on vercel's official accounnt > projects page...