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.

Sign up for GitHub

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

Jump to bottom

virtualCommandLine not working #170

Closed
Anzic23 opened this issue Jun 15, 2021 · 4 comments
Closed

virtualCommandLine not working #170

Anzic23 opened this issue Jun 15, 2021 · 4 comments

Comments

@Anzic23
Copy link
Contributor

Anzic23 commented Jun 15, 2021

Describe the bug
ioBroker/ioBroker.js-controller#844

Expected behavior
if I add the --tls-min-v1.0 command to virtualCommandLine, the adapter should start without crashing
Screenshots & Logfiles
image

Versions:

  • Adapter version: 4.0.2
  • JS-Controller version: 3.3.12
  • Node version: v12.22.1
  • Operating system: docker
@Apollon77
Copy link
Collaborator

What is the "virtualCommandLine"?

@Anzic23
Copy link
Contributor Author

Anzic23 commented Jun 15, 2021

What is the "virtualCommandLine"?

image

@Anzic23
Copy link
Contributor Author

Anzic23 commented Jun 15, 2021

in homebridge, it works perfectly!
image

@Apollon77
Copy link
Collaborator

Hm ... I'm not sure if this is the same!!

virtual (!!) command line is kind of injecting command line parameters just for homebridget after the process was started, so it is NOT "node-options" used when the process gets started!

SO this can not work that way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Apollon77 @Anzic23