Cannot GET / #1373

ghost · 2018-04-10T17:39:20Z

Operating System: Windows 10 x64
Node Version: 7.3.0
NPM Version: 3.10.10
webpack Version: 4.5.0
webpack-dev-server Version: 3.1.3

This is a bug
This is a modification request

Code

https://github.com/MitchTalmadgeUofU/Digital-Story/tree/a73fbbf8c5d0f90d9190232e976407610eb5fb7e

Expected Behavior

When I visit http://localhost:9000/, it should display the index.html page generated by HtmlWebpackPlugin.

Actual Behavior

When I visit http://localhost:9000/, I receive a 404: Cannot GET /. If I compile the index.html using my production webpack config -- so that the files are generated on the hard drive and not in memory -- I can then load webpack dev server and the index.html file is served (but does not update when I make changes to the template).

For Bugs; How can we reproduce the behavior?

Clone the repository

Edit: We discovered that this error only occurs on Windows, and only if you clone into a directory with spaces in the path. No spaces? No error.

Checkout this tree: git checkout a73fbbf8c5d0f90d9190232e976407610eb5fb7e .
Install dependencies: npm i
Start dev-server: npm run dev-web.

Edit: I forgot to remove part of my dev-web script; open package.json and replace the dev-web script contents with:

webpack-dev-server --config webpack/webpack.dev.config.js --progress

Visit http://localhost:9000 and see the error message.
Stop the dev-server.
Compile the production files: npm run build-web.
Start dev-server again: npm run dev-web.
Visit http://localhost:9000 and see "Hello World".

The text was updated successfully, but these errors were encountered:

tresko · 2018-04-10T17:49:06Z

I also have the same problem that only appears on Windows, but on Mac and Ubuntu, it works fine.

Operating System: Windows 10 x64
Node Version: 9.11.1
Yarn Version: 1.3.2
webpack Version: 4.5.0
webpack-dev-server Version: 3.1.3

ghost · 2018-04-10T18:29:00Z

I downgraded back to these versions:

"html-webpack-plugin": "^2.30.1",
"webpack": "^3.8.1",
"webpack-dev-server": "^2.9.3"

And I can confirm that it works again. This seems to be a problem with upgrading to webpack 4

tresko · 2018-04-10T19:25:19Z

@MitchTalmadgeUofU you can use the following versions; these are the last ones that worked for me:

"html-webpack-plugin": "^3.2.0",
"webpack": "^4.5.0",
"webpack-dev-server": "3.1.0"

I receive Cannot GET / on Windows for all versions which are higher than 3.1.0.

Is this related? webpack/webpack-dev-middleware#270

GuacheSuede · 2018-04-10T20:24:58Z

@tresko I verify your solution works 👍

GuacheSuede · 2018-04-10T21:03:54Z

However Webpack Dev Middleware issue still persists, only Version of 3.0.1 for Webpack Dev Middleware works, below(MIME type issue) or above(Cannot GET /) all fails.

ejnu · 2018-04-12T04:37:10Z

ok i got this - thanks to this issue - #1375
for now - you need remove spaces from the project path

ghost · 2018-04-12T07:21:32Z

@ejnu I can confirm, the problem is solved by removing spaces from the path. Particularly, the contentBase is what must have no spaces in the path.

It is quite clear this is a webpack-dev-middleware bug, so everyone please follow this issue until it is fixed, then we can update the dependency in this repository after a fix is released:

webpack/webpack-dev-middleware#296

kasperhhk · 2018-04-27T20:35:40Z

I think this issue is caused by webpack/webpack-dev-middleware#297 , which has been solved yesterday, and a new release of webpack-dev-middleware has come out (v3.1.3) immediately after. This repo should probably update the version it's using from 3.1.2 to 3.1.3.

s-h-a-d-o-w · 2018-05-01T16:11:31Z

I receive Cannot GET / on Windows for all versions which are higher than 3.1.0.

Odd, 3.1.1 still works for me.

Just created a project from scratch based on the official webpack docs, got the "Cannot GET /" error, downgraded to 3.1.1 and everything is good.

nguyenkhois · 2018-05-10T07:19:15Z

This issue has been fixed in version 3.1.4. It works finne for me now 👍 Thanks so much! 🥇

theliveseven · 2018-06-11T09:22:12Z

@nguyenkhois I had the same issue, upgraded to 3.1.4, and it has been fixed! Thanks!

dandohotaru · 2018-06-11T11:19:40Z

@nguyenkhois, @theliveseven can you you mention what webpack version (and plugins) do you rely on?

nguyenkhois · 2018-06-12T15:34:03Z

@dandohotaru

Webpack Dev Server 3.1.1 or 3.1.4 works fine for me and I rely on 3.1.1. I have not used so much this version 3.1.4 but I think it works very well.
Webpack - I use the latest version and it works without a problem.
Plugins: You decide what fits your project. You can view my simple example here

Have a nice day!

dandohotaru · 2018-06-12T16:14:15Z

@nguyenkhois well, the only reason i'm asking is because i couldn't have webpack-dev-server refresh as expected for any of the versions i've tried (3.1.x)
Check my dependencies in here
In the meantime i tackle the problem with lite-server instead :)

theliveseven · 2018-06-13T00:31:13Z

@dandohotaru

webpack : 4.6.0
webpack-dev-server: 3.1.4

I was previously using webpack-dev-server:3.1.3. I had no issue with this before because I was only using my mac for development. I encountered the issue when I set up the project in my PC (Windows 10). Upgrading the webpack-dev-server to version 3.1.4 fixed the issue.

Here is a part of my package.json file :)

"webpack": "^4.6.0",
"webpack-bundle-analyzer": "^2.11.1",
"webpack-cli": "^2.0.14",
"webpack-dev-server": "^3.1.4",
"webpack-merge": "^4.1.2"

dandohotaru · 2018-06-25T13:43:21Z

As far as I'm concerned I've fixed the issue by

making sure a base path is defined
making sure all 404s are redirected to index.html

module.exports = {
  ...
  output: {
    ...
    publicPath: '/'
  },
  devServer: {
    historyApiFallback: true,
  },
}

"webpack": "^4.12.1",
"webpack-cli": "^3.0.8",
"webpack-dev-server": "^3.1.4",
"webpack-merge": "^4.1.3"

hz9527 · 2018-07-08T08:33:25Z

I also have the same problem(entrypoint undefined = index.html). first, I thought it was a bug of webpack4, but I built it by the config, everything is normal. so I thought it was a bug of webpack-dev-server. but I it not work with some other versions. finally, I add "context: resolve('../')", good running!

PatelDipen92 · 2018-08-01T14:02:02Z

I am using

"webpack": "^4.16.3",
"webpack-cli": "^3.1.0",
"webpack-dev-server": "^3.1.5"

still getting the error.

My webpack.config file looks like

var path = require('path');

module.exports = {
    entry: './src/app.js',


    output: {
        path: path.join(__dirname, 'output'),
        filename: 'bundle.js'
    },

    devServer: {
        contentBase: path.join(__dirname, 'dist'),
        compress: true,
        port: 9000
    }
}

nguyenkhois · 2018-08-01T14:34:52Z

@PatelDipen92 Have you tried to use "./" before output and dist?:

var path = require('path');

module.exports = {
    entry: './src/app.js',


    output: {
        path: path.join(__dirname, './output'),
        filename: 'bundle.js'
    },

    devServer: {
        contentBase: path.join(__dirname, './dist'),
        compress: true,
        port: 9000
    }
}

I use Windows 10 and WDS works fine for me. You can see here on my repo.

PatelDipen92 · 2018-08-01T14:40:00Z

@nguyenkhois I have tried that also but still getting the same error. I am using Windows 8.1

    entry: './src/app.js',

    output: {
        path: path.join(__dirname, './output'),
        filename: 'bundle.js',
        publicPath: '/'
    },

    devServer: {
        contentBase: path.join(__dirname, './dist'),
        compress: true,
        port: 9000,
        historyApiFallback: true
    }

hz9527 · 2018-08-01T15:04:43Z

Duplicate of #1421 e...I try it again. entryPoint undefined = index.html. but I can use devServer. you can set context and set devServer.publicPath = '/' (not './'). so you can get page with inject js & css. @PatelDipen92

dandohotaru · 2018-08-01T15:14:56Z

the setup bellow works for me as expected for quite some time by now...

webpack.config.js

const path = require("path")
const webpack = require('webpack')

module.exports = {
  entry: {
    app: './src/app.js'
  },
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: '[name].bundle.js',
    publicPath: '/',
  },
  ...

webpack.dev.js

const path = require("path")
const webpack = require('webpack')
const merge = require('webpack-merge')
const common = require('./webpack.config.js')

module.exports = merge(common, {
  mode: 'development',
  devtool: 'source-map',
  devServer: {
    contentBase: path.join(__dirname, "dist"),
    port: 8080,
    stats: "minimal",
    watchContentBase: true,
    historyApiFallback: true,
    open: false,
    hot: false
  },
  ...

index.html

<head>
	<base href="./" />
	...
</head>

hz9527 · 2018-08-01T15:23:33Z

you should set context & publicPath
webpack.config.js

const path = require("path")
const webpack = require('webpack')

module.exports = {
 context: path.join(__dirname, '../'),
  entry: {
    app: './src/app.js'
  },
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: '[name].bundle.js',
    publicPath: '/',
  },
  ...

webpack.dev.js

const path = require("path")
const webpack = require('webpack')
const merge = require('webpack-merge')
const common = require('./webpack.config.js')

module.exports = merge(common, {
  mode: 'development',
  devtool: 'source-map',
  devServer: {
    publicPath: '/',
    port: 8080,
    stats: "minimal",
    watchContentBase: true,
    historyApiFallback: true,
    open: false,
    hot: false
  },
  ...

I think contentBase is setting static server(if you need)
so you set context & publicPath(in devServer)

PatelDipen92 · 2018-08-01T16:05:34Z

@hz9527 @dandohotaru I have tried with both solutions you have provided. But none of it worked.

PatelDipen92 · 2018-08-01T17:17:15Z

The problem is resolved. The issue was with the directory name. For the output, I was using "output" directory and for devServer I was providing contentBase from "dist" which was not containing index.html page. So it was throwing "Cannot Get /" error

entry: './src/app.js',

    output: {
        path: path.join(__dirname, 'output'),
        filename: 'bundle.js'        
    },

    devServer: {
        contentBase: path.join(__dirname, 'output'),
        compress: true,
        port: 9000,
        historyApiFallback: true,
        publicPath: '/'
    }

adamklepacz · 2018-10-02T20:01:35Z

Got the same problem after downloading some of the boilerplates. Thank You @PatelDipen92 for resolving a problem

fortinmike · 2018-11-20T17:57:31Z

As far as I'm concerned I've fixed the issue by

making sure a base path is defined

making sure all 404s are redirected to index.html
module.exports = {
  ...
  output: {
    ...
    publicPath: '/'
  },
  devServer: {
    historyApiFallback: true,
  },
}

Thanks @dandohotaru, this works for us too. We didn't have to revert to earlier versions of the packages; just adding the publicPath did the job (we already had historyApiFallback so I can't comment on the effect of that).

zeroone001 · 2019-05-05T00:16:42Z

output: {
    ...
    publicPath: '/'
  }

This is the key

andreygfranca · 2019-05-12T14:20:22Z

I made a copy of index.html in a new folder I called deployment to match what I specified in the output.path

ecarrera · 2019-06-11T04:57:50Z

https://stackoverflow.com/questions/37954809/cannot-get-error-running-hello-world-in-webpack

a-m-dev · 2019-11-09T06:13:07Z

@MitchTalmadgeUofU you can use the following versions; these are the last ones that worked for me:

"html-webpack-plugin": "^3.2.0",
"webpack": "^4.5.0",
"webpack-dev-server": "3.1.0"

I receive Cannot GET / on Windows for all versions which are higher than 3.1.0.

Is this related? webpack/webpack-dev-middleware#270

with webpack-dev-server-@3.1.0 you have to run npm audit fix,

basically does not works now ...
:(((

darnoceloc · 2020-04-15T18:40:52Z

@PatelDipen92 Good eye! This tormented me for quite some time.

    output: {
        path: path.resolve(__dirname, 'output'),
        publicPath: './dist/',
        filename: 'bundle.js'
    },
    devServer: {
        contentBase: path.join(__dirname, 'output'),
        port: 3000,
        writeToDisk: true,
        publicPath: 'http://localhost:3000/dist/',
        hotOnly: true,
        historyApiFallback: true,
    },
    plugins: [
        new HtmlWebpackPlugin({hash: true,
            title: 'My Awesome application',
            myPageHeader: 'Hello World',
            template: './src/index.html',
            filename: './dist/index.html'}),
        new webpack.HotModuleReplacementPlugin(),
        new webpack.HotModuleReplacementPlugin({template: './public/index.html'})
    ]    
};

ghost mentioned this issue Apr 10, 2018

Webpack-Dev-Middleware errors for different Versions. webpack/webpack-dev-middleware#296

Closed

2 tasks

ejnu mentioned this issue Apr 12, 2018

webpack with webpack-dev-server@3.1.3 can't get /index.html generat by html-webpack-plugin #1374

Closed

2 tasks

sebiniemann mentioned this issue Apr 22, 2018

VuePress dev server not working vuejs/vuepress#162

Closed

ErikGrijzen mentioned this issue Jun 14, 2018

Cannot GET / when '#' in directory path #1421

Closed

2 tasks

michael-ciniawsky added the type: bug label Aug 25, 2018

michael-ciniawsky added priority: 1 (critical) severity: 2 (regression) labels Aug 25, 2018

michael-ciniawsky added this to the 3.2.0 milestone Aug 25, 2018

michael-ciniawsky closed this as completed Aug 26, 2018

michael-ciniawsky removed priority: 1 (critical) severity: 2 (regression) type: bug labels Aug 26, 2018

michael-ciniawsky removed this from the 3.2.0 milestone Aug 26, 2018

jong-ah mentioned this issue Oct 21, 2021

(오류) [webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema. jong-ah/vue-webgame#2

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot GET / #1373

Cannot GET / #1373

ghost commented Apr 10, 2018 •

edited by ghost

Loading

tresko commented Apr 10, 2018

ghost commented Apr 10, 2018

tresko commented Apr 10, 2018

GuacheSuede commented Apr 10, 2018

GuacheSuede commented Apr 10, 2018 •

edited

Loading

ejnu commented Apr 12, 2018

ghost commented Apr 12, 2018 •

edited by ghost

Loading

kasperhhk commented Apr 27, 2018

s-h-a-d-o-w commented May 1, 2018

nguyenkhois commented May 10, 2018

theliveseven commented Jun 11, 2018

dandohotaru commented Jun 11, 2018

nguyenkhois commented Jun 12, 2018

dandohotaru commented Jun 12, 2018

theliveseven commented Jun 13, 2018

dandohotaru commented Jun 25, 2018

hz9527 commented Jul 8, 2018

PatelDipen92 commented Aug 1, 2018 •

edited

Loading

nguyenkhois commented Aug 1, 2018

PatelDipen92 commented Aug 1, 2018

hz9527 commented Aug 1, 2018

dandohotaru commented Aug 1, 2018 •

edited

Loading

hz9527 commented Aug 1, 2018

PatelDipen92 commented Aug 1, 2018

PatelDipen92 commented Aug 1, 2018

adamklepacz commented Oct 2, 2018

fortinmike commented Nov 20, 2018

zeroone001 commented May 5, 2019

andreygfranca commented May 12, 2019

ecarrera commented Jun 11, 2019

a-m-dev commented Nov 9, 2019

darnoceloc commented Apr 15, 2020 •

edited

Loading

Cannot GET / #1373

Cannot GET / #1373

Comments

ghost commented Apr 10, 2018 • edited by ghost Loading

Code

Expected Behavior

Actual Behavior

For Bugs; How can we reproduce the behavior?

tresko commented Apr 10, 2018

ghost commented Apr 10, 2018

tresko commented Apr 10, 2018

GuacheSuede commented Apr 10, 2018

GuacheSuede commented Apr 10, 2018 • edited Loading

ejnu commented Apr 12, 2018

ghost commented Apr 12, 2018 • edited by ghost Loading

kasperhhk commented Apr 27, 2018

s-h-a-d-o-w commented May 1, 2018

nguyenkhois commented May 10, 2018

theliveseven commented Jun 11, 2018

dandohotaru commented Jun 11, 2018

nguyenkhois commented Jun 12, 2018

dandohotaru commented Jun 12, 2018

theliveseven commented Jun 13, 2018

dandohotaru commented Jun 25, 2018

hz9527 commented Jul 8, 2018

PatelDipen92 commented Aug 1, 2018 • edited Loading

nguyenkhois commented Aug 1, 2018

PatelDipen92 commented Aug 1, 2018

hz9527 commented Aug 1, 2018

dandohotaru commented Aug 1, 2018 • edited Loading

hz9527 commented Aug 1, 2018

PatelDipen92 commented Aug 1, 2018

PatelDipen92 commented Aug 1, 2018

adamklepacz commented Oct 2, 2018

fortinmike commented Nov 20, 2018

zeroone001 commented May 5, 2019

andreygfranca commented May 12, 2019

ecarrera commented Jun 11, 2019

a-m-dev commented Nov 9, 2019

darnoceloc commented Apr 15, 2020 • edited Loading

ghost commented Apr 10, 2018 •

edited by ghost

Loading

GuacheSuede commented Apr 10, 2018 •

edited

Loading

ghost commented Apr 12, 2018 •

edited by ghost

Loading

PatelDipen92 commented Aug 1, 2018 •

edited

Loading

dandohotaru commented Aug 1, 2018 •

edited

Loading

darnoceloc commented Apr 15, 2020 •

edited

Loading