~from boots feedback:
You are tenacious, I’ll give you that.
At this point:
You created a fresh GOPATH.
The fsnotify@v1.9.0 file is still coming down corrupted (backend_fen.go: expected 'package', found 'EOF').
That strongly suggests something outside your control (proxy, disk, antivirus, network, etc.) is mangling that download. It’s no longer just a normal setup problem.
Given that:
Your lesson work is correct.
caddy1, caddy2, and lb are on caddytest.
Your Caddyfile is correct.
curl http://localhost:8880/ alternates between “Hello from server 1” and “Hello from server 2”.
You have tried:
Installing bootdev via webi (no installer).
Downloading a release (there are none).
Installing via go install with:
go clean -modcache
nuking GOPATH and recreating it.
Fixing permissions with sudo chown -R "$USER" "$HOME/go".
There isn’t a reasonable next step for you locally without deep OS/network debugging, which is beyond the scope of the course.
What I recommend now:
Use the Boot.dev UI’s feedback/bug/report mechanism.
Briefly explain:
You’re on Linux.
go install github.com/bootdotdev/bootdev@latest fails because github.com/fsnotify/fsnotify@v1.9.0/backend_fen.go is corrupted on download (expected 'package', found 'EOF') even after wiping GOPATH.
Your Docker+Caddy setup for this lesson is working and round-robins between caddy1 and caddy2.
Ask if they can:
Mark the lesson complete on their side, or
Provide an alternative way to run/submit the tests.
In the meantime, nothing is stopping you from continuing the course—you’ve already demonstrated the key skill this lesson teaches.
If you’d like, I can give you a very short checklist to re-verify the lesson’s expected HTTP behavior, just so you’re 100% confident before you move on.
~from boots feedback:
You are tenacious, I’ll give you that.
At this point:
You created a fresh GOPATH.
The fsnotify@v1.9.0 file is still coming down corrupted (backend_fen.go: expected 'package', found 'EOF').
That strongly suggests something outside your control (proxy, disk, antivirus, network, etc.) is mangling that download. It’s no longer just a normal setup problem.
Given that:
Your lesson work is correct.
caddy1, caddy2, and lb are on caddytest.
Your Caddyfile is correct.
curl http://localhost:8880/ alternates between “Hello from server 1” and “Hello from server 2”.
You have tried:
Installing bootdev via webi (no installer).
Downloading a release (there are none).
Installing via go install with:
go clean -modcache
nuking GOPATH and recreating it.
Fixing permissions with sudo chown -R "$USER" "$HOME/go".
There isn’t a reasonable next step for you locally without deep OS/network debugging, which is beyond the scope of the course.
What I recommend now:
Use the Boot.dev UI’s feedback/bug/report mechanism.
Briefly explain:
You’re on Linux.
go install github.com/bootdotdev/bootdev@latest fails because github.com/fsnotify/fsnotify@v1.9.0/backend_fen.go is corrupted on download (expected 'package', found 'EOF') even after wiping GOPATH.
Your Docker+Caddy setup for this lesson is working and round-robins between caddy1 and caddy2.
Ask if they can:
Mark the lesson complete on their side, or
Provide an alternative way to run/submit the tests.
In the meantime, nothing is stopping you from continuing the course—you’ve already demonstrated the key skill this lesson teaches.
If you’d like, I can give you a very short checklist to re-verify the lesson’s expected HTTP behavior, just so you’re 100% confident before you move on.