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

Error: The server does not support SSL connections #38

Open
alxgrk opened this issue Jul 2, 2024 · 2 comments
Open

Error: The server does not support SSL connections #38

alxgrk opened this issue Jul 2, 2024 · 2 comments

Comments

@alxgrk
Copy link

alxgrk commented Jul 2, 2024

Hey,

I got an error while trying to debug a workflow:

$ npx dbos-sdk debug -x postgresql://localhost:2345 -u 95f62e02-e9a1-4f65-b061-2e96cfd85838
Debugger attached.
Debugger attached.
2024-07-02 14:39:00 [info]: Running in debug mode! 
2024-07-02 14:39:00 [info]: Debugging mode proxy: localhost:2345 
2024-07-02 14:39:00 [info]: Workflow executor initialized 
2024-07-02 14:39:00 [error]: Debug mode error: The server does not support SSL connections 
    at GlobalLogger.error (.../node_modules/@dbos-inc/dbos-sdk/dist/src/telemetry/logs.js:63:65)
    at debugWorkflow (.../node_modules/@dbos-inc/dbos-sdk/dist/src/dbos-runtime/debug.js:24:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Command.<anonymous> (.../node_modules/@dbos-inc/dbos-sdk/dist/src/dbos-runtime/cli.js:40:5)

Not really sure, how SSL comes into play here. Any idea?

EDIT: ok, maybe I was too quick with opening the issue. Looks like it takes the dbos-config.yaml into account, which included no local url & I didn't expect to be the case.

@devhawk
Copy link
Collaborator

devhawk commented Jul 19, 2024

Thanks for filing the issue @alxgrk! I'd rather have a spuriously opened issue that we can close easily than losing the context on a problem. If this is still an issue, let me know!

@alxgrk
Copy link
Author

alxgrk commented Jul 20, 2024

@devhawk I guess a hint why debug considers the yaml's DB URL in the docs could be an option - or, if it doesn't need that config, it could skip reading it. Apart from that, I would also be fine with closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants