Notebook doesn't run in test mode about analyze HOT 9 CLOSED

Thanks a lot guys, adding the skip parameter did work. Now it's running!

from analyze.

Hello Steven,

Have you tried the suggested "fix" in the last error message? I.e. adding a skipHttpsCertificateVerification: true to the devproxy.json file?

(See https://i2group.github.io/notebook-sdk/guide/devproxy.html#development-proxy-configuration-syntax)

from analyze.

Hi
I am not sure that this is the correct place for this question as we have repositories specifically for the i2 Notebook SDK and for I2 Analyze using Docker Containers.

I will have a chat to both teams and see if someone can help.

Cheers

from analyze.

HI @sdorresteijn88 (Steven)

Dev have come back to me asking if you have started the Liberty server and if so, have you tried to connect to it in a browser directly?

They ask this as the connection is being refused from 9082 not 4000 and the error you are seeing would suggest that the Liberty application server has not been started.

Thanks

from analyze.

from analyze.

Hi Steven

I guess you were trying to attach some screen shots in your reply and that did not work?

Can you attach them directly in a comment so we can see what you were trying to show us please.

The setup for the example says that you need to make devproxy.json point to the URL of an existing i2 Analyze deployment.

In the sample file we have that set as:

{
"$schema": "https://i2group.github.io/notebook-sdk/schemas/devproxy.json",
"port": 4000,
"plugins": ["http://localhost:5001/"],
"server": "http://localhost:9082/opal"
}

The example assumes that the i2 Analyze server, the node server and the proxy are all running locally and are accessible using localhost and are not using secure connections.

Cheers

from analyze.

Hi Anthony,

I added indeed a printscreen. Is it possible to use this when you have an develop environment in Docker, https://i2group.github.io/analyze-containers/content/deploy_config_dev.html?

from analyze.

Hi Steven

It is also good to note that even though you tried earlier to access the opal server using http , the fact that you have set that up in its container to work with secure connections means we do not allow the downgrade to an insecure connection.

Really you should access it using https://i2analyze.eia:9443/opal as the instructions for your environment in docker states and hopefully what Tim is suggesting above should get you working with that.

Cheers

from analyze.

That's great news , if you have further Notebook SDK related issues be sure to raise them on

https://github.com/i2group/notebook-sdk/issues

rather than here, as it will help others who are looking for Notebook SDK solutions to find them.

Cheers

from analyze.