Debug issue on vs code

[akshaydarne1-ui]

We are getting when we are trying to debug code from vs code

Error - EQAVS1007E as400.xyz.abc on port 8005 could not be connected
Message received-self signed certificate in certificate chain

We are using ibm I debugger 3.0.0

[sebjulliand]

Hi @akshaydarne1-ui ,
please review the Debug Service configuration steps, especially the part about hte certificate generation from iNav: https://codefori.github.io/docs/developing/debug/#configuring--starting-the-service

Once the certificate is properly generated and the service is started, reconnect from VS Code and then hover over the connection in the bottom bar. Then click on Debugger 3.0.0.

This will take you to the IBM i Debugger view. Both the server and the service should be shown as running at this point:

If a warning is shown on the service, check it out and click on any action it offers to fix the warning.
If both lines are green, you should be able to use the debugger.

[akshaydarne1-ui]

Mentioned steps we have followed but need how we can generate self signed certificate

[mkwan01]

The root cause of the self-signed certificate issue is that the certificate on the client machine does not match the certificate on the host. Please use the following steps to collect trace information:

1. From VSCode client, select View > Command Palette... > IBM i: Connection Settings
2. Select the Debugger tab
3. Check "Debug trace"
4. Start a batch debug session
5. From the Debug Console, you can see the first line of trace in red color like the following:

Connection settings: { 'host': '...', 'port': 8005, 'secure': true, 'capath': '...', 'ignoreCertificateErrors': false, 'TLS_Version': undefined }

6. Paste the above trace statement to this issue. Specifically, we are interesting in the capath value.

[akshaydarne1-ui]

I have checked and only found Cpath value is undefined

[mkwan01]

The capath value is retrieved from the environment variable DEBUG_CA_PATH. Code for IBM i should set this env var before starting a debug session. There was a timing issue before in Code for IBM i v2.16.0, which may cause the env var not to be set when a debug session is started. Please update your Code for IBM i extension to the latest level and see if it fixes the problem.