8000 `codespaces.new` cert has expired, so our Codespaces launcher button doesn't work any more · Issue #6399 · ddev/ddev · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
codespaces.new cert has expired, so our Codespaces launcher button doesn't work any more #6399
Closed
@rfay

Description

@rfay

Preliminary checklist

Output of ddev debug test

Expand `ddev debug test` diagnostic information
[COPY-PASTE HERE THE OUTPUT OF `ddev debug test`]

Expected Behavior

Our codespaces launch button should work (on PR)

Actual Behavior

It goes to codespaces.new, whose cert expired a couple days ago,

image

Steps To Reproduce

Launch a Codepaces button, like https://codespaces.new/?ref=20240714_rfay_codespaces_http_port&repo=80927419

It goes to codespaces.new, which has expired cert.

Anything else?

Github does in fact own codespaces.new (I had no idea there was a new TLD.) So maybe they'll just fix this.

However, I don't see them using it in their setup for running a new codespace.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0