Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profile Inactive Error (2) #2398

Open
zFernand0 opened this issue Jul 26, 2023 · 5 comments
Open

Profile Inactive Error (2) #2398

zFernand0 opened this issue Jul 26, 2023 · 5 comments
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases

Comments

@zFernand0
Copy link
Member

zFernand0 commented Jul 26, 2023

Hi Team,

I am facing same issue, i created new connection of http://ip:port, but it still gives me same error that its an HTTP(S) connection.
Could someone please let me know the solution to fix it ?

Do i need some JAva updates for it, or some CLI ?

I am using VS Code --> Zowe Explorer
:
image

errorDetails: [i [Error]: z/OSMF REST API Error:
http(s) request error event called
Error: write EPROTO 12081672:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:....\third_party\boringssl\src\ssl\tls_record.cc:231:

at o.populateError (c:\Users\Krishan.Singh\.vscode\extensions\zowe.vscode-extension-for-zowe-2.9.1\out\src\extension.js:80:20446)
at ClientRequest.<anonymous> (c:\Users\Krishan.Singh\.vscode\extensions\zowe.vscode-extension-for-zowe-2.9.1\out\src\extension.js:80:12433)
at ClientRequest.emit (node:events:525:35)
at TLSSocket.socketErrorListener (node:_http_client:481:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)] {
mDetails: {
  msg: 'z/OSMF REST API Error:\n' +
    'http(s) request error event called\n' +
    'Error: write EPROTO 12081672:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:..\\..\\third_party\\boringssl\\src\\ssl\\tls_record.cc:231:\n',
  causeErrors: [Error: write EPROTO 12081672:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:..\..\third_party\boringssl\src\ssl\tls_record.cc:231:
  
  	at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)] {
    errno: -4046,
    code: 'EPROTO',
    syscall: 'write'
  },
  source: 'client',
  errorCode: undefined,
  **protocol: 'https',**
  port: 23,
  host: '999.999.99.99',
  basePath: '',
  httpStatus: undefined,
  errno: undefined,
  syscall: undefined,

Originally posted by @Krishan0031 in #1096 (comment)

@zFernand0 zFernand0 added the bug Something isn't working label Jul 26, 2023
@github-actions
Copy link

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

@JillieBeanSim
Copy link
Contributor

Hey @zFernand0 error looks similar to issue I open in cli a while back
zowe/zowe-cli#1329

@zFernand0
Copy link
Member Author

I believe this might be due to the SDKs forcing https by default if no protocol is specified in the profile.
We may need to do some testing around this though 😋

@JillieBeanSim
Copy link
Contributor

It would be nice to see the cli issue fixed as we still see it even when protocol for plugin's profile type is set to http, like it forces https regardless of setting 😺

@zFernand0 zFernand0 added priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases labels Aug 1, 2023
@Madhubalan-p
Copy link

I am facing same issue. zowe explorer, ibm z openeditor are using https by default which creates a problem for we who have setup a zdt machine and trying out the rseapi. any suggestion to workaround this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases
Projects
Status: Low Priority
Development

No branches or pull requests

3 participants