I have a marathon deployment using mantl which uses aws loadbalancing and self-signed

<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="24

certificate invalid error for self-signed cert about depcon HOT 4 CLOSED

containx commented on July 22, 2024

certificate invalid error for self-signed cert

from depcon.

Comments (4)

gondor commented on July 22, 2024

Ok, Just released 0.8.3 which should cover that. Can grab a new binary under the releases.

I will look into making this an option in the config for the environment depending on if this fixes it or not.

A new --insecure flag under all marathon commands is now available.

Example:

depcon -e dev mar app list --insecure

Let me know if this fixes your case

from depcon.

kbroughton commented on July 22, 2024

Thanks for the quick turnaround!

I still see an error with the new binary.
(master)][brew_py2] depcon -e dev mar --insecure app list
2016-04-19 09:41:14 ERROR [depcon]: Get https://k4b4-mantl-control-01.node.c1.io/marathon/v2/apps: x509: certificate signed by unknown authority

I'm going to try and get a proper cert installed in the mean time.

from depcon.

snoby commented on July 22, 2024

I'm using version .86 and I am also seeing this on my mantl cluster.
/work/Official/depcon$ ./depcon-osx64 app list --insecure
2016-05-12 15:03:37 ERROR [depcon]: Get https://control.z.blahblahablah.com/marathon//v2/apps: x509: certificate is valid for localhost, *.node.consul, *.service.consul, not blahblahblahblah.z.tropo.com

from depcon.