-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Systems without IPv6 support crash netlify dev #5166
Comments
A temporary fix for this is [dev]
targetPort = "8080 I had a similar issue with SvelteKit when it switched to Vite's |
Adding targetPort didn't work for me. |
Oh, that's odd. I think what happened and why it started working when you changed to static is that it stopped detecting the framework with eleventy.json. I'm not familiar with Eleventy, do you notice anything wrong with the json file? |
Well that's the thing - it did detect Eleventy. I saw that in the output, but it didn't fire it up like it used to. |
Can you please test with version 12.0.10? This new version should show the underlying error in this case, because if it instantly throws that means something went wrong before it even started to wait for the port. |
Big paste coming in.
I really think the 'localhost cant be found thing' is a misfire, and this is the important bit:
Previously, the CLI would use my |
I was able to reproduce this on Ubuntu with IPv6 completely disabled. I will start creating a fix for this. Can you confirm that IPv6 is disabled on your machine? For example doing |
This should be solved with 12.0.11. If the problem persists please reopen. |
I used the techniques here, https://www.golinuxcloud.com/linux-check-ipv6-enabled/, and from what I can tell, IPv6 is not disabled, but, I updated, and everything works now, so the problem is fixed. :) Thank you. Oh, as an aside,
Should I be concerned? |
Describe the bug
For a very long time, I used the following to start my Eleventy site:
A week or so ago, it began throwing an error:
What's interesting is that the error would throw right away. It didn't wait for Eleventy to start. I confirmed localhost worked via ping, and I could still run eleventy in my directory just fine.
You can see my forum post here: https://answers.netlify.com/t/ntl-dev-no-longer-working-with-eleventy/76968
This morning, I noticed how it said "with Eleventy", and I realized the CLI recognized Eleventy and was maybe assuming it was running already? On a whim, I tried this in my toml:
And voila, it worked. It correctly ran the command to start Eleventy.
So my question is - what changed here?
Steps to reproduce
With an Eleventy site, try running it as described above (with
-c
), and see if the CLI doesn't launch Eleventy.Configuration
No response
Environment
The text was updated successfully, but these errors were encountered: