You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Alexey Kuznetsov <ak...@gridgain.com> on 2017/06/14 13:01:51 UTC

Re: Ignite web console not running in browser

Hi!

Did you try exactly: http://localhost:9000/ ?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-web-console-not-running-in-browser-tp13701p13702.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite web console not running in browser

Posted by Andrey Novikov <an...@apache.org>.
You need use web server for deliver web pages and proxying requests to
backend service.

Added documentation for Apache HTTP Server:
https://apacheignite-tools.readme.io/docs/build-and-deploy#section-run-ignite-web-console-in-production-mode



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-web-console-not-running-in-browser-tp13701p14003.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite web console not running in browser

Posted by Andrey Novikov <an...@apache.org>.
Hi,

In Ignite 1.9, Ignite 2.0 developer web server bind only on localhost
interface. This was fixed in master where developer web server bind for all
interfaces.

As temporary workaround you can try to replace localhost with your ip in
https://github.com/apache/ignite/blob/1.9.0/modules/web-console/frontend/gulpfile.babel.js/tasks/bundle.js
for Ignite 1.9 or set environment variable HOST for Ignite 2.0
https://github.com/apache/ignite/blob/ignite-2.0/modules/web-console/frontend/gulpfile.babel.js/webpack/environments/development.js



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-web-console-not-running-in-browser-tp13701p13852.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.