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
Chat
view-forward
# All channels
view-forward
# General
view-forward
# Announcements
view-forward
# Feature Requests
view-forward
# Hyper
view-forward
# Jobs
view-forward
# Micro
view-forward
# Now
view-forward
# PKG
view-forward
# Serve
view-forward
Team
Paulo De Mitri
@paulogdm
Guillermo Rauch
@rauchg
William Li
@williamli
Joe Cohen
@joecohens
Nathan Rajlich
@tootallnate
Tim
@timneutkens
Leo Lamprecht
@leo
Arunoda Susiripala
@arunoda
Timothy
@timothyis
Matheus Fernandes
@matheus
Matthew Sweeney
@msweeneydev
Allen Hai
@coetry
Steven
@styfle
Max Rovensky
@rdev
Luis
@lfades
Igor Klopov
@igorklopov
Naoyuki Kanezawa
@nkzawa
Javi Velasco
@javivelasco
Connor Davis
@davis
Evil Rabbit
@evilrabbit
Shu Ding
@shu
Andy Bitz
@andybitz
Joe Haddad
@timer
Paco
@paco
Juan Campa
@juancampa
Ana Trajkovska
@ana-trajkovska
Christopher Skillicorn
@skllcrn
Posts
Chat
Members
Info
Show previous messages

January 9, 2020 at 9:10pm
Hello, I need help with my domain, I added it to zeit and everything is verified and looks good, even the A dns points correctly as a subdomain but my deployments don't show on the main domain, it keeps loading and nothing shows up, where should I look?
  • reply
  • like

January 12, 2020 at 5:21am
Hi, one question : le there a way to invalidate cache on a single url - or trigger a recache ? If I ping a resource with the no_cache header, I will bypass the cache, but will it cache the new render ? Is there any other way to do that ? Purpose is to be as lean as possible in the use of actual computing and rely on cdn as much as possible.
  • reply
  • like

January 12, 2020 at 2:47pm
  • reply
  • like
how do i fix this?
  • reply
  • like
i purchased the domain of zeit
  • reply
  • like

January 12, 2020 at 11:23pm
Hello , I'm really sorry about that - please email support@zeit.co with the domain for further assistance.
  • reply
  • like
Wow, I just got this message: "You have been creating deployments at a very fast pace. Please retry in 19 hours"
19 hours? I need to work, also I Knew nothing about a limit like that one.
Apart from all that, I'm being forced to deploy to test my code because "now dev" doesn't work on Windows (with Go) . . .
Edited
  • reply
  • like

January 13, 2020 at 2:56pm
Anyone experiencing with stuck deployments? It says "done" but the status is still building
like-fill
1
  • reply
  • like
  • reply
  • like
these has been done but still in the building status
  • reply
  • like
Anyone experiencing with stuck deployments? It says "done" but the status is still building
I have the exact same issue
  • reply
  • like
the deployments seem to be okay now
  • reply
  • like
I'm currently experiencing a rate limit error on zeit now
  • reply
  • like
Have you guys ever experienced something simillar?
  • reply
  • like
429: RATE_LIMITED Code: INTERNAL_FUNCTION_RATE_LIMIT
  • reply
  • like
My functions are all out of service currently because of this
  • reply
  • like

January 14, 2020 at 6:20am
My app is serverful – Next v8 and Now v1. What do I need to do to go serverless. I think I need to put v2 in my now.json and get rid of express and move my REST endpoints to lambdas in the /api directory. Do I need to upgrade Next v8 to v9? Anything else?
  • reply
  • like

January 14, 2020 at 5:53pm
Hi Guys! Anyone here who could help solve domain and issues with zeit? I am willing to pay for the help!
  • reply
  • like

January 17, 2020 at 6:09pm
Hi Guys, the zeit.co dont can modify a json file?
  • reply
  • like
ERROR Unhandled Promise Rejection {"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"Error: EROFS: read-only file system, open '/var/task/bot/content.json'","reason":{"errorType":"Error","errorMessage":"EROFS: read-only file system, open
  • reply
  • like

January 18, 2020 at 10:30pm
i think You can try using /tmp/ dir to write and read files
  • reply
  • like

January 22, 2020 at 8:48pm
Hello there guys! Excuse the possibly dumb question but I'm fairly new to next.js and I'm trying to deploy a website to now.sh and I can't seem to find anything online to help me troubleshoot this issue I have. Whenever I first load the website it never delivers the index.jsx page. If I try to directly access other routes though everything works fine. On my localhost everything is working just fine, the problem only shows up when I deploy it to now.sh.
  • reply
  • like
Hello there guys! Excuse the possibly dumb question but I'm fairly new to next.js and I'm trying to deploy a website to now.sh and I can't seem to find anything online to help me troubleshoot this issue I have. Whenever I first load the website it never delivers the index.jsx page. If I try to directly access other routes though everything works fine. On my localhost everything is working just fine, the problem only shows up when I deploy it to now.sh.
Leaving it here, maybe someone can find a cleaner solution or patch the same behaviour. For some reason I'm still trying to get, now is generating all the html files without an extension, this leaves me with two files: index.html and index and for some reason on the first load it goes with the extensioned index which is blank and only has the "root" node in it.
  • reply
  • like

January 23, 2020 at 2:55pm
Suddenly getting error Couldn't find any versions for "workbox-build" that matches "^5.0.0-rc.3" error when deploying with now
  • reply
  • like