You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Hank Beatty (JIRA)" <ji...@apache.org> on 2017/08/14 17:43:00 UTC

[jira] [Commented] (TC-301) creating https delivery service and not setting to active still looks for cert. Github Issue #1086

    [ https://issues.apache.org/jira/browse/TC-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126059#comment-16126059 ] 

Hank Beatty commented on TC-301:
--------------------------------

[~dewrich] Is this still an issue? If so, are we planning on fixing for 2.1?

> creating https delivery service and not setting to active still looks for cert. Github Issue #1086
> --------------------------------------------------------------------------------------------------
>
>                 Key: TC-301
>                 URL: https://issues.apache.org/jira/browse/TC-301
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>            Reporter: Dewayne Richardson
>              Labels: Configuration, SSL
>
> Que'ed and snapshotted - delivery service was not set to active. On syncds it err's looking for DS cert.
> ERROR Received error code 400 for https://trafficops/api/1.1/deliveryservices/hostname/deliveryservicename/sslkeys.json from Traffic Ops!
> FATAL SSL URL: https://trafficops/api/1.1/deliveryservices/hostname/deliveryservicename/sslkeys.json returned 400. Exiting.
> Just generating a ssl key and error goes away.
> Copying /tmp/ort/123/trafficserver/config_trops deliveryservicename .cer to /opt/trafficserver/etc/trafficserver/ssl//deliveryservicename_cert.cer
> ERROR Copying /tmp/ort/123/trafficserver/config_trops/deliveryservicename.key to /opt/trafficserver/etc/trafficserver/ssl//deliveryservicename.key



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)