404 logs

[pullmann4rent]

Hello,

every 2 seconds my express logs this:

PUT /api/inngest 200 12.690 ms - 54
PUT /api/inngest 200 13.458 ms - 54
GET /api/inngest 200 3.461 ms - 165
GET /x/inngest 404 0.919 ms - 148
GET /.netlify/functions/inngest 404 5.876 ms - 165
GET /.redwood/functions/inngest 404 1.831 ms - 165

Is this a error because of my implementation or is this normal ?

BTW: I use express

[linear]

INN-2970 404 logs

[jbranchaud]

@pullmann4rent I just ran into the same issue -- it turns out that this is by design.

Inngest scans for common ports and common paths where the API might be served and it does this every 2 seconds. You can see the relevant code here:

inngest/pkg/devserver/discovery.go

Lines 15 to 46 in ea67219

	// Ports indicate the default ports that we attempt to scan on localhost
	// when discovering SDK-based endpoints
	Ports = []int{
	// le derp
	80, 443,
	// Rails, Express & N*xt routes
	3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010,
	// Django
	5000,
	// Other common ports
	8000, 8080, 8081, 8888,
	// Redwood
	8910, 8911,
	}
	// Paths indicate the paths we attempt to hit when a web server is available.
	// These are the default, recommended paths for hosting Inngest routes.
	Paths = []string{
	// Defaults
	"/api/inngest",
	"/x/inngest",
	// Netlify
	"/.netlify/functions/inngest",
	// Redwood
	"/.redwood/functions/inngest",
	}
	timeout = 2 * time.Second
	hc = http.Client{
	Timeout: timeout,
	}

I added --no-discovery and -u http://localhost:3000/api/inngest to the inngest dev server command to get it to quiet down a bit and stop pinging my other unrelated dev servers running on, for example, port 5000.

$ pnpx inngest-cli@latest dev --no-discovery -u http://localhost:3000/api/inngest