menu

ZEIT

Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.

Channels
Team

Cannot create NOW v1 deployments

January 8, 2019 at 4:26pm

Cannot create NOW v1 deployments

January 8, 2019 at 4:26pm

When I run now, I get this output:

> Error! You tried to create a Now 1.0 deployment. Please use Now 2.0 instead: https://zeit.co/upgrade

My now.json file looks like this:

{
"version": 1,
"type": "docker",
"features": {
"cloud": "v2"
}
}

Any ideas as to why this happens and how to fix it?


January 8, 2019 at 4:39pm

Hello! Is your account new @lartech?

  • reply
  • like

I have deployed successfully to Now v1 before.

  • reply
  • like

Oh ok, could you please email support@zeit.co with all the details?

  • reply
  • like

GitHub says I created my account 6 days ago

  • reply
  • like

Yes, I emailed support@zeit.co and linked to this thread

  • reply
  • like

I see. Well, we restricted access to V1 on newly created accounts a few days ago.

https://spectrum.chat/users/paulogdm?thread=5d1def00-3504-4618-9ef4-40d64e69f573

  • reply
  • like

I see.

  • reply
  • like

Would I be included in those new users? It seems strange to allow people to deploy to Now v1 and then remove that permission

  • reply
  • like

If you created the account before 1 January you are unable to deploy on V1. I know it is a little bit of trouble, but keep in mind that V1 will be deprecated eventually and it makes sense for us to now allow new users to deploy.

  • reply
  • like

It does make sense, but not at the moment, given that there are issues with deploying next+custom node on now v2. Besides using docker/now-v1, I don't know of another way to deploy such setups

  • reply
  • like

OK, if I cannot deploy on v1, how can I use Docker images on v2?

  • reply
  • like

You cannot

  • reply
  • like

rip time to find new free hosting

  • reply
  • like

January 10, 2019 at 5:59pm
If you created the account before 1 January you are unable to deploy on V1. I know it is a little bit of trouble, but keep in mind that V1 will be deprecated eventually and it makes sense for us to now allow new users to deploy.

Wait, what? Older users cannot continue using Docker deployments? Does that make any sense? You claim v. 1 won't be deprecated until there's a smooth transition path. Well, for my projects, there is no smooth path so far, I'd love to keep deploying with Docker.

Is that not possible anymore?

  • reply
  • like

February 10, 2019 at 1:11pm

Locking to avoid bumps.

  • reply
  • like
private
This conversation has been locked