Not opening local build

I have tried to install Maputnik in an AWS EC2 instance with npm. But when I am trying to do npm start its showing the following codes

> maputnik@1.5.0 start /opt/maputnik/maputnik-editor
> webpack-dev-server --progress --profile --colors --config config/webpack.config.js

11295ms building
16ms finish module graph
1ms sealing
0ms basic dependencies optimization
0ms dependencies optimization
1ms advanced dependencies optimization
0ms after dependencies optimization
34ms chunk graph
0ms after chunk graph
0ms optimizing
0ms basic module optimization
1ms module optimization
0ms advanced module optimization
0ms after module optimization
1ms basic chunk optimization
0ms chunk optimization
16ms advanced chunk optimization
0ms after chunk optimization
0ms module and chunk tree optimization
1ms after module and chunk tree optimization
0ms basic chunk modules optimization
0ms chunk modules optimization
0ms advanced chunk modules optimization
0ms after chunk modules optimization
0ms module reviving
0ms module order optimization
1ms advanced module order optimization
5ms before module ids
0ms module ids
9ms module id optimization
1ms chunk reviving
0ms chunk order optimization
0ms before chunk ids
0ms chunk id optimization
5ms after chunk id optimization
0ms record modules
1ms record chunks
52ms hashing
2ms content hashing
0ms after hashing
0ms record hash
1ms module assets processing
125ms chunk assets processing
3ms additional chunk assets processing
2ms recording
0ms additional asset processing
0ms chunk asset optimization
378ms after chunk asset optimization
0ms asset optimization
0ms after asset optimization
1ms after seal
220ms emitting
1ms after emitting

Then I am trying to get access through my desktop using ip X.X.X.X:8888 but there is nothing appearing. If I use the online editor then I was unable to get access the mbtiles as a source from that EC2 instance but tile server and other things are working quietly ok from EC2. Is there any solution for me?

[orangemug]

@azizul-bkash it’s probably bound to localhost rather than 0.0.0.0, try

npm start -- --host 0.0.0.0

[jdeboer-geoplan]

@pathmapper, great. webpack’s description on https://webpack.js.org/configuration/dev-server/ is

Specify a host to use. By default this is localhost. If you want your server to be accessible externally, specify it like this: --host 0.0.0.0