Website Preview

I have a question, I remember in the past, for example when we did “vercel” on the console, this would trigger a “development” deployment and it would end up in an address like

https:// <project_name> - <my_account_name> .vercel.app

But lately when I do this, it ends up in an address like

https:// <project_name> - <some_id> - <my_account_name>s-projects.vercel.app

Is there a way to force the previous behavior? Having the <some_id> as part of the url makes it really difficult for example to test redirects from login endpoint that required pre-declared redirects.

Also causes issues when we are dealing with localstorage.

Hello, we generate both unique URLs and branch URLs in the preview environment. This should happen automatically: Accessing Deployments through Generated URLs

Can you provide us with an example of a deployment where it used to work and now it is not working?

Yes. For example on https://wikichallenges-mramericanmike.vercel.app/ That will return 404.

While for example, on an older project. https://dongles-mramericanmike.vercel.app

That will work.

The one I found working is https://wikichallenges-mramericanmikes-projects.vercel.app/ without any generated id. But the problem is that this version is not the newest development deploy that lives on https://wikichallenges-4ddqsa6o4-mramericanmikes-projects.vercel.app/

As a note, I’m running just vercel with no flag for this. Maybe I do need to pass a flag?

Ok I guess I found it, looking at the deployment details I found out this URL

https://wikichallenges-mramericanmike-mramericanmikes-projects.vercel.app/

I guess this is the new format? project name, user id, user id + s-projects.vercel.app ?

Is there no way to revert to the other standard?

project name - user id .vercel.app

Also noticed that this new URL can’t be shared with others, is there a way to make it accesible to anyone with the URL? (I believe this was also the old standard, but I may be wrong)

After some more reading I found this.

I’m guessing I missed when this changed and wasn’t aware of the new defaults.

You can disable Deployment protection if you don’t require this.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.