Nuxt•2mo ago

Vite allowedHosts problem

In my Nuxt 3.16.1 app, i am continually getting blocked request. This host "placeholder.web.app" is not allowed. To allow this host, add "placeholder.web.app" to server.allowedHosts in vite.config.js. Below is the config. vite: { server: { allowedHosts: [ 'placeholder.web.app' ] } }, Setting to 'true' also does not work. What am I missing?

5 Replies

kapa.ai•2mo ago

Hi @Ploggs. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- I can see you're having an issue with Vite's allowedHosts configuration in your Nuxt 3.16.1 application. This is a known issue in Nuxt 3.16.x where setting allowedHosts: true doesn't work as expected. According to the GitHub issue #31318, other users have reported the same problem where setting allowedHosts: true doesn't function as a wildcard to allow all hosts. The issue has been confirmed to be specific to Nuxt's implementation, as it doesn't occur in Vite directly. For your specific case with placeholder.web.app, there are a couple of approaches you can try: 1. Explicitly list all domains you need in the array (as you've already attempted) 2. Try using environment variables for defining allowed hosts, which was added in a recent Vite update If you're still experiencing issues despite having the domain explicitly listed in your configuration, it might be related to another problem that appeared in Nuxt 3.16.0 involving mismatching versions of the ohash package, which can cause various unexpected behaviors. This was reported in this GitHub issue. As a workaround for the ohash issue, you could try adding an override in your package.json:

"overrides": {
  "ohash": "2.0.11"
}

"overrides": {
  "ohash": "2.0.11"
}

And then reinstall your dependencies with:

rm -rf node_modules package-lock.json && npm install

rm -rf node_modules package-lock.json && npm install

(Or the equivalent command for your package manager) If you're still facing issues after these steps, you might want to consider temporarily downgrading to Nuxt 3.15.x until these issues are resolved in a future patch release. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•2mo ago

<@149277091714695168> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

PloggsOP•5w ago

good suggestions, but no luck @kapa.ai any other ideas. Im stuck

kapa.ai•5w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I understand you're still stuck with the Vite allowedHosts issue in your Nuxt application. Let me suggest a few additional approaches that might help: 1. Try using a regex pattern in your allowedHosts configuration:

   vite: {
     server: {
       allowedHosts: [/\.web\.app$/]
     }
   }

   vite: {
     server: {
       allowedHosts: [/\.web\.app$/]
     }
   }

2. Disable host checking completely (only for development):

   vite: {
     server: {
       host: true,
       hmr: {
         clientPort: 24678,
         host: '0.0.0.0'
       }
     }
   }

   vite: {
     server: {
       host: true,
       hmr: {
         clientPort: 24678,
         host: '0.0.0.0'
       }
     }
   }

3. Check for conflicting configurations in your project. Sometimes there might be multiple Vite configurations that override each other. 4. Verify your hosts file to ensure the domain is properly mapped to your local IP. 5. Try using a specific version override for Nitro and h3 as mentioned in this GitHub issue comment:

   "overrides": {
     "nitropack": "2.10.4",
     "h3": "1.15.0"
   }

   "overrides": {
     "nitropack": "2.10.4",
     "h3": "1.15.0"
   }

6. If you're using macOS and have Spotlight indexing enabled, try disabling it for your project folder. Some users reported in this issue that Spotlight indexing can cause unexpected behavior. 7. If you're using Bun, try adding polling options as mentioned in this GitHub issue:

   watchers: {
     chokidar: {
       usePolling: true,
     },
   },
   nitro: {
     watchOptions: {
       usePolling: true,
     },
   }

   watchers: {
     chokidar: {
       usePolling: true,
     },
   },
   nitro: {
     watchOptions: {
       usePolling: true,
     },
   }

If none of these solutions work, you might need to consider a temporary workaround like using a different domain for development or waiting for a fix in a future Nuxt release. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•5w ago

<@149277091714695168> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

Gaming

Programming

Vite allowedHosts problem

Did you find this page helpful?