Environment

• Operating System: Darwin
• Node Version: v22.16.0
• Nuxt Version: 4.1.1
• CLI Version: 3.28.0
• Nitro Version: 2.12.5
• Package Manager: pnpm@10.7.0
• Builder: -
• User Config: modules, devtools, css, content, mdc, runtimeConfig, routeRules, sourcemap, experimental, nitro, vite, eslint, i18n, plausible, robots, sanctum, sentry, sitemap
• Runtime Modules: @nuxt/eslint@1.9.0, @nuxt/ui-pro@3.3.3, @nuxtjs/sitemap@7.4.3, @nuxt/content@3.7.0, @vueuse/nuxt@13.9.0, nuxt-auth-sanctum@1.2.0, @nuxtjs/i18n@10.0.6, nuxt-laravel-echo@0.2.7, @nuxtjs/robots@5.2.10, @nuxtjs/plausible@1.2.0, @sentry/nuxt/module@9.46.0, nuxt-seo-utils@7.0.14, @nuxt/image@1.11.0
• Build Modules: -

Version

3.7.0

Reproduction

Description

In dev mode, connection to web sockets is closed:

WebSocket connection to 'wss://localhost:4000/ws' failed: Could not connect to the server.

Additional context

I think it is related to #3500 . I am using Laravel valet proxy (and I need to do that even in production).

Pinning nuxt/content to 3.5.1 resolves this problem.

Logs