-
Notifications
You must be signed in to change notification settings - Fork 148
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
problem with Remote Node on v1.15.0 #736
Comments
@kamandir Thanks for reporting the issue! I’ve been trying to reproduce it, but everything seems to work fine in my environment. Here’s my setup:
# admin.yaml
port: 8080
remoteNodes:
- name: "dev"
apiBaseUrl: "http://localhost:8081/api/v1"
isAuthToken: true
authToken: 123456
curl --location 'http://localhost:8080/api/v1/dags?remoteNode=dev' With this setup, both the API and WebUI on Could you share a bit more about your setup so I can dig into this further and try to replicate the issue? Thanks! :) |
i'm running it on a secure port with a certificate installed. Does this make difference?.. PS: I have a side process that utilizes the API and all is fine there, API calls work with no issues. |
Thanks for the information! I'll try to fix. |
@kamandir Thanks for reporting the issue! I've released v1.15.1 that should fix the HTTPS connection problems. You can now configure TLS verification skipping per remote node like this: remoteNodes:
- name: "DEV"
apiBaseUrl: "https://_my_dev_node_.com:8443/api/v1"
isAuthToken: true
authToken: "bla-bla...."
skipTLSVerify: true # Add this line if you need to skip TLS verification Please try it out and let me know if you're still experiencing any issues. Thanks for helping improve Dagu! 🙂 |
tested on v15.1
|
@kamandir, thank you for testing! Could you please share the server's response body from the network tab in your browser? It should include an error message. |
@kamandir Thanks! It looks like a certification issue. Have you tried with |
cool it helped. with the "skipTLSVerify: true" I see no error anymore. Thanks! |
I'm glad to hear the workaround worked! I'll look into why the certificate didn't function properly later. |
hey there!
Thanks for the new nice stuff released! I started some testing and found challenges...
maybe it's me doing something wrong, but i will still report it to find out why it fails... ;)
whatever i do, all the time i hit this error (code 500) when try to change from local node to a remote.
Config:
Error:
The text was updated successfully, but these errors were encountered: