menu
up-caret
down-caret

ZEIT

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

# General

General Chatter

Trending conversations
503 on deployment
@codelayer · 22d
ENV variables
@remotealex · 4h
BRU1 instances are timing out
@helguita · 31d
Could someone point me toward strategies for decreasing my PHP lambda size?
@unitof · 5h
Images not showing on CRA deployment
@passingmagic · 5h

503 on deployment

February 14, 2019 at 10:52am

Hi guys, getting a 503 on a healthy deployment: http://app-viuxsgrtpx.now.sh/ - any idea why this is occurring.


February 14, 2019 at 10:53am

Any hints on the logs?

  • reply
  • like
TypeError: argument str must be a string 02/14 11:53 AM (3m) at Object.parse (/home/nowuser/src/node_modules/cookie/index.js:51:11) 02/14 11:53 AM (3m) at Function._callee$ (/home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:3548:58) 02/14 11:53 AM (3m) at tryCatch (/home/nowuser/src/node_modules/regenerator-runtime/runtime.js:62:40) 02/14 11:53 AM (3m) at Generator.invoke [as _invoke] (/home/nowuser/src/node_modules/regenerator-runtime/runtime.js:288:22) 02/14 11:53 AM (3m) at Generator.prototype.(anonymous function) [as next] (/home/nowuser/src/node_modules/regenerator-runtime/runtime.js:114:21) 02/14 11:53 AM (3m) at asyncGeneratorStep (/home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:2055:24) 02/14 11:53 AM (3m) at _next (/home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:2077:9) 02/14 11:53 AM (3m) at /home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:2084:7 02/14 11:53 AM (3m) at new Promise (<anonymous>) 02/14 11:53 AM (3m) at new F (/home/nowuser/src/node_modules/core-js/library/modules/_export.js:36:28) 02/14 11:53 AM (3m) TypeError: argument str must be a string 02/14 11:54 AM (2m) react-i18next:: You will need pass in an i18next instance either by props, using I18nextProvider or by using i18nextReactModule. Learn more https://react.i18next.com/components/overview#getting-the-i-18-n-function-into-the-flow
  • reply
  • like

Same is happening to me without any errors on the logs. BRU1 instances are timing out when I try to do a new deployment

  • reply
  • like
TypeError: argument str must be a string 02/14 11:53 AM (3m) at Object.parse (/home/nowuser/src/node_modules/cookie/index.js:51:11) 02/14 11:53 AM (3m) at Function._callee$ (/home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:3548:58) 02/14 11:53 AM (3m) at tryCatch (/home/nowuser/src/node_modules/regenerator-runtime/runtime.js:62:40) 02/14 11:53 AM (3m) at Generator.invoke [as _invoke] (/home/nowuser/src/node_modules/regenerator-runtime/runtime.js:288:22) 02/14 11:53 AM (3m) at Generator.prototype.(anonymous function) [as next] (/home/nowuser/src/node_modules/regenerator-runtime/runtime.js:114:21) 02/14 11:53 AM (3m) at asyncGeneratorStep (/home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:2055:24) 02/14 11:53 AM (3m) at _next (/home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:2077:9) 02/14 11:53 AM (3m) at /home/nowuser/src/.next/server/static/HasqLxb3c44RNbEVhjNJQ/pages/index.js:2084:7 02/14 11:53 AM (3m) at new Promise (<anonymous>) 02/14 11:53 AM (3m) at new F (/home/nowuser/src/node_modules/core-js/library/modules/_export.js:36:28) 02/14 11:53 AM (3m) TypeError: argument str must be a string 02/14 11:54 AM (2m) react-i18next:: You will need pass in an i18next instance either by props, using I18nextProvider or by using i18nextReactModule. Learn more https://react.i18next.com/components/overview#getting-the-i-18-n-function-into-the-flow

This is not a problem with the platform. Please, give me more context so I can assist you...

  • reply
  • like

Im experiencing the exact same both in terms of argument str must be a string + the BRU1 instances

  • reply
  • like

Same is happening to me without any errors on the logs. BRU1 instances are timing out when I try to do a new deployment

Create a new thread with details about this.

  • reply
  • like

Can anyone give me a reproducible example?

  • reply
  • like

well next.js isn't throwing me any errors in the console on local env. So it's very difficult to determine where the issue lies and make it reproducible

Edited
  • reply
  • like

This is not a problem with the platform. Please, give me more context so I can assist you...

What is the best way to give you context? Your input is highly appreciated.

  • reply
  • like

well next.js isn't throwing me any errors in the console on local env. So it's very difficult to determine where the issue lies and make it reproducible

Give me the content of now.json

  • reply
  • like

What is the best way to give you context? Your input is highly appreciated.

Are you trying to use a custom server + Next.js with Now 2.0?

  • reply
  • like
{
"alias": ["app.layerise.com", "www.app.layerise.com"],
"name": "App",
"version": 1,
"regions": ["bru1"]
}
Edited
  • reply
  • like
{
"alias": ["app.layerise.com", "www.app.layerise.com"],
"name": "App",
"version": 1,
"regions": ["bru1"]
}

Do this. Remove your node_modules then the .next folder and try to build it again. Now 1.0 is an environment really close to your own local machine (if MAC or Linux ofc.) It is very unlikely to be an error with the platform...

  • reply
  • like

But if you think it is, put together a small reproducible example so I can check it out...

  • reply
  • like

removing universal-cookie did the trick. However i don't understand why now logs issues i don't encounter on local.

  • reply
  • like

@codelayer Can you give me your now.json? Also, is your code public?

  • reply
  • like

March 1, 2019 at 2:31pm

Completely out of the blue.

  • reply
  • like

Also getting 503

  • reply
  • like

Haven't deployed.

  • reply
  • like

Site just gone down

  • reply
  • like

Was down until I scaled a new instance.

  • reply
  • like

What does a 503 mean?

  • reply
  • like