This channel is not moderated by Netlify staff. For staff and peer support, please head to 👉 community.netlify.com
yes
!
i will look now
thanks
i don't see any errors in the log
1:12:44 AM: Site is live
1:12:44 AM: Site is live
1:13:13 AM: Finished processing build request in 3m4.432228476s
I just deployed an
Now I try to access
index.html file directly through dragNdrop. I have my site up and running at name.netlify.com like usual. I then went to my registrar and setup a DNS record CNAME www.example.com to name.netlify.com. I waited a bit and checked through dnschecker.org that DNS is propagated and I can see www.example.com points to name.netlify.com. Neat !Now I try to access
www.example.com and get a Not Found message... Strangely, the Response headers say Server: Netlify which I guess means that Netlify is reached. Do I need another setup ?
I don't really know why by the way... I would be glad to get a technical explication to this. As far as I understand,
CNAME www.example.com to name.netlify.com should be enough to work. No ?
@Jonarod CNAME is enough to work, yes. So you need to tell us what the difference is in the DNS records returned by your DNS servers when you "add www.example.com as a custom domain." "custom domain" is not any kind of standard DNS terminology and I don't know what that means.
But that is what is written in Netlify domains panel
For instance, I login to Netlify then I click my website, then on the
Settings tab I go to Domain management. Here I can see "custom domain". If I don't fill "www.example.com" here, the CNAME rule doesn't work: I get a "Not Found" error
CNAME alone does not work for me, hence my surprise :)
@Jonarod Oh, I see. I wasn't clear that your fix didn't change any DNS settings at all; the "domain settings" you were changing was the list of host names that Netlify recognises. That's nothing to do with DNS at all; that setting lets Netlify recognise the
Host: header sent in the HTTP request and map it to the correct Netlify site.
(I.e., Netlify has no idea what DNS request(s), if any, were made to get the IP address on which it received the request, nor does it care. That same address will be used for many different Netlify sites.)
Hey guys, I have read https://www.netlify.com/pdf/oreilly-modern-web-development-on-the-jamstack.pdf and it's amazing! I really enjoyed the read 👍
The only question I'm having: "What are the downsides of using JAMstack over traditional monolith architecture? And what type of projects are not the best fit for JAMstack?"
I'm getting an error: :1: Incorrectly eaten value: please report this warning on http://git.io/vg5Ft
I've upgraded Jekyll locally to 4.0.0. I'm setting Ruby to v 2.4.3 in .ruby-version but all Netlify builds are failing because "jekyll-4.0.0 requires rubygems version >= 2.7.0, which is incompatible with the current version, 2.6.14" Locally, I have rubygems 3.0.6 Is there anyway to get Netlify to run >=2.7.0?
◈ Netlify Dev ◈
◈ Starting Netlify Dev with gatsby
◈ Function builder netlify-lambda detected: Running npm script build:lambda
› Warning: ◈ This is a beta feature, please give us feedback on how to improve at
› https://github.com/netlify/netlify-dev-plugin/
(node:10400) UnhandledPromiseRejectionWarning: Error: spawn yarn ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:84:9)
(node:10400) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:10400) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
◈ Starting Netlify Dev with gatsby
◈ Function builder netlify-lambda detected: Running npm script build:lambda
› Warning: ◈ This is a beta feature, please give us feedback on how to improve at
› https://github.com/netlify/netlify-dev-plugin/
(node:10400) UnhandledPromiseRejectionWarning: Error: spawn yarn ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:84:9)
(node:10400) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:10400) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
and attempting to use gatsby develop and access the admin panel errors out with "failed to fetch"
@patrickisgreat So sorry you have this issue, the starter only supports netlify-lambda ATM, there's a PR wich removes netlify-lambda and adds netlify-dev to starter, you can check the PR here: netlify-templates/gatsby-starter-netlify-cms#274
@patrickisgreat To also asnwer your concrete question, you have to remove everything from
package.json which is netlify-lambda related, but all the steps you need to make can be found in the PR mentioned above.
I've tried to disable adblock but no luck
Also the deploys are not working