quasarframework/quasar · error

ERROR_NETWORK_PORT_NOT_AVAIL

ERROR_NETWORK_PORT_NOT_AVAIL

Error message

Could not find an open port. Please configure a lower one to start searching with.

What it means

When no server address is configured, Quasar auto-detects a network address and then searches upward from the configured port for a free one. If the port-finding routine fails with ERROR_NETWORK_PORT_NOT_AVAIL, this warning is emitted because no open port could be found within the search range.

Source

Thrown at app-vite/lib/quasar-config-file.js:267

      host = await getExternalIP()
      cachedExternalHost = host
    }
  }

  try {
    const openPort = await findClosestOpenPort(port, host)
    if (port !== openPort) {
      warn()
      warn(`️️Setting port to closest one available: ${openPort}`)
      warn()

      port = openPort
    }
  } catch (err) {
    warn()

    if (err.message === 'ERROR_NETWORK_PORT_NOT_AVAIL') {
      warn(
        'Could not find an open port. Please configure a lower one to start searching with.'
      )
    } else if (err.message === 'ERROR_NETWORK_ADDRESS_NOT_AVAIL') {
      warn(
        'Invalid host specified. No network address matches. Please specify another one.'
      )
    } else {
      warn('Unknown network error occurred')
      console.error(err)
    }

    warn()

    if (!addressRunning) process.exit(1)
    return null
  }

  addressRunning = true

View on GitHub (pinned to 4841521b5f)

Solutions

1. Lower devServer.port in quasar.config.js to a normal value (e.g. 9000 or 8080) so the upward search succeeds
2. Check the configured devServer.host is valid (see the related address warning otherwise)
3. Ensure no firewall/SELinux policy blocks binding ports in that range
4. Pick a different starting port if your environment reserves certain ranges

Example fix

// before (quasar.config.js)
devServer: { port: 65535 }
// after
devServer: { port: 9000 }

// validate configured port before running dev
const port = require('./quasar.config.js').devServer.port
if (port > 65500) {
  console.error('devServer.port too high; use a value like 9000 so a free port can be found')
}

// if you bind ports yourself before starting quasar dev
try {
  server.listen(preferredPort)
} catch (err) {
  if (err.code === 'EACCES' || err.code === 'EADDRINUSE') {
    console.warn(`Port ${preferredPort} unavailable, falling back to 0 (auto-assign)`)
    server.listen(0)
  }
}

When it happens

Trigger: devServer.port in quasar.config.js is set to a very high value (e.g. 65535 or above the max) so no port can be found by incrementing; the port scanner can't bind any candidate port on the chosen host.

Common situations: Port set to 65535 or a value near the upper bound; firewall/permission restrictions blocking binding; misconfigured host combined with an unrealistic starting port; container environments with restricted port ranges.

Related errors

• ERROR_NETWORK_PORT_NOT_AVAIL
• Unknown network error occurred
• ️️Setting port to closest one available: ${openPort}
• Network error encountered while following the quasar.config
• Registry responded with ${response.status}

AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30). Data as JSON: /api/errors/82634848e73af277. Report an issue: GitHub.