Monitoring - A fix has been created and is being rolled out to affected customers.
This issue affects instances of Tentacle that use SHA1 (an old, unsupported, encryption algorithm), and prevents them from connecting to Octopus Cloud. This was a side effect of the Octopus Server .NET 8 upgrade, and the resulting change to the underlying OS from Debian 11/OpenSSL 1.x to Debian 12/OpenSSL 3.x.
If you continue to be affected by this issue, please try the workaround detailed at https://github.com/OctopusDeploy/Issues/issues/8523, or contact support at https://octopus.com/support.
Dec 08, 2023 - 10:21 UTC
This issue affects instances of Tentacle that use SHA1 (an old, unsupported, encryption algorithm), and prevents them from connecting to Octopus Cloud. This was a side effect of the Octopus Server .NET 8 upgrade, and the resulting change to the underlying OS from Debian 11/OpenSSL 1.x to Debian 12/OpenSSL 3.x.
If you continue to be affected by this issue, please try the workaround detailed at https://github.com/OctopusDeploy/Issues/issues/8523, or contact support at https://octopus.com/support.
Dec 08, 2023 - 10:21 UTC
Identified - The underlying cause has been identified. The issue is currently isolated to cloud customers. A fix is actively being work on.
Dec 08, 2023 - 06:06 UTC
Dec 08, 2023 - 06:06 UTC
Update - We have identified a suspected root cause and workaround.
We suspect this is limited to certificates using a SHA1 algorithm but are investigating further.
If affected please try the workaround detailed in this issue: https://github.com/OctopusDeploy/Issues/issues/8523
Dec 08, 2023 - 03:41 UTC
We suspect this is limited to certificates using a SHA1 algorithm but are investigating further.
If affected please try the workaround detailed in this issue: https://github.com/OctopusDeploy/Issues/issues/8523
Dec 08, 2023 - 03:41 UTC
Investigating - Since the morning of Friday 8th December, cloud customers are reporting issues with communicating to listening and polling tentacles. We are investigating this as a priority incident and will work on a resolution as soon as possible.
Dec 08, 2023 - 01:23 UTC
Dec 08, 2023 - 01:23 UTC
Cloud instances may be missing task log lines or show incorrect status for deployment steps
Subscribe
Update - We have identified a workaround. The issue occurs when a deployment's task log is viewed while the deployment is running. If users navigate away from viewing a running deployment, all task log lines should be successfully saved. This will also avoid the issue where deployment steps may show the wrong status.
We are working with our upstream provider to resolve this issue.
Dec 07, 2023 - 01:17 UTC
We are working with our upstream provider to resolve this issue.
Dec 07, 2023 - 01:17 UTC
Investigating - We have identified an issue where some Octopus Cloud instances since 20 November 2023 are missing some log lines from their task logs.
Deployment steps that encounter this problem could also show the wrong status (e.g. showing as still running) even though the step has completed successfully. The deployment task will have the correct status.
We are investigating this issue as a priority.
Dec 06, 2023 - 06:20 UTC
Deployment steps that encounter this problem could also show the wrong status (e.g. showing as still running) even though the step has completed successfully. The deployment task will have the correct status.
We are investigating this issue as a priority.
Dec 06, 2023 - 06:20 UTC
Octopus.com / OctopusId
?
Operational
Octopus Cloud
?
Degraded Performance
Cloud Control Center (billing.octopus.com)
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.