Skip to content

bug: all static HTML files used for server rendering still use old Coder logo and CSS styling #18878

@Parkreiner

Description

@Parkreiner

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

EDIT: Actually, this issue affects all of our static files, like oauth2allow.html, too

Our error.html file seems to have missed a lot of aesthetic updates for a while now. For the longest time, that just meant that we were using the 2023-era styling for Coder elements, but now that we've changed our company logo, it also means that the logo itself is wrong.

Image

Per the comment at the top of the file:

This template is used by application handlers to render friendly error pages when there is a proxy error (for example, when the target app isn't running).
Meaning that any customers that run into a proxy error have a risk of seeing this page.

Relevant Log Output

Expected Behavior

When a proxy error happens, the user will see an HTML page that matches our current design systems.

Steps to Reproduce

These steps are based on Coder's internal dogfooding platform, but anything that triggers a proxy error would presumably cause the same problem.

  1. Make sure that GitHub is not configured for the deployment
  2. Go to Coder Dogfood, and log out of your user account
  3. Click the "Log in with Github" button, and wait for the auth flow to redirect you to a server-rendered error page, using error.html as the template

Environment

  • Host OS: MacOS Version 13.6.7 (22G720)
  • Coder version: v2.24.1-devel+dad033ee3

Additional Context

The issue occurs consistently, I have tested this on the latest version

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIssue that require triage

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions