quasarframework/quasar · error

Unknown network error occurred

Error message

Unknown network error occurred

What it means

This is the catch-all branch of the network-error handler in QuasarConfigFile#onAddress. The address/port detection helper rejected with something other than the two recognized codes (ERROR_NETWORK_PORT_NOT_AVAIL / ERROR_NETWORK_ADDRESS_NOT_AVAIL), so the cause is unknown; the original error is printed via console.error and the process exits if no address resolution is running.

Source

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

      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
  return { host, port }
}

let wsToken = null
function createWsToken() {
  if (wsToken === null) {
    const list =
      'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789'

View on GitHub (pinned to 4841521b5f)

Solutions

1. Read the stack trace printed below the warning — it names the actual underlying error
2. Check devServer.host in quasar.config and try a concrete value like '127.0.0.1' or '0.0.0.0' instead of a hostname
3. Verify the machine has a usable non-loopback network interface (`ip addr` / `ifconfig`); fix or restore it
4. Try running with a simplified network environment (disable VPN/proxy) or a newer/patched Node LTS version
5. If it reproduces on a clean project, report it to the Quasar team with the full stack

Example fix

// before (quasar.config.js)
devServer: { server: { host: 'my-laptop.local' } }
// after
devServer: { server: { host: '127.0.0.1' } }

const os = require('node:os')
const nets = os.networkInterfaces()
const hasUsableAddress = Object.values(nets)
  .flat()
  .some(n => n && !n.internal && n.family === 'IPv4')
if (!hasUsableAddress) {
  console.warn('No usable network interface; pin devServer.server.host to 127.0.0.1')
}

When it happens

Trigger: Any rejection from the underlying get-network-addresses/port detection utilities that is not one of the two known error codes — e.g. an unexpected OS-level network API failure, an EPERM/EACCES from a socket call, or an internal bug in the detection helper surfaced while resolving devServer.host during `quasar dev`.

Common situations: Running inside restricted sandboxes/containers where socket or interface enumeration is blocked; broken or missing network interfaces in CI; VPN/proxy software interfering with address detection; Node version changes altering API behavior of network detection.

Related errors

• ERROR_NETWORK_PORT_NOT_AVAIL
• The queued task for "${task.diffName}" failed
• ERROR_NETWORK_PORT_NOT_AVAIL
• ️️Setting port to closest one available: ${openPort}
• Registry responded with ${response.status}

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