mlco2 / mlco2/codecarbon

Self-hosted carbonserver fails with "Unknown client"

Open
#961 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
1.9k
Forks
323
Avg merge
1d 12h
Merged PRs (30d)
12

Description

Describe the bug

I started a self-hosted carbonserver as described here. The dashboard is available at http://codecarbon.local and the fief server is running at http://fief.localhost. But after login with Fief admin credentials, an error is thrown: "Authorize: Unknown client".

To Reproduce
Steps to reproduce the behavior:

  1. ./deploy/deploy.py setup
  2. adjust /etc/hosts
  3. ./deploy/deploy.py start --traefik --fief --codecarbon
  4. Go to http://codecarbon.local
  5. Click on 'Sign in or create an account'
  6. Login with Fief admin credentials

Expected behavior
See the dashboard

Screenshots

Image

Desktop (please complete the following information):

  • OS: Ubuntu 22.04
  • Python Version 3.10
  • CodeCarbon Version 3.0.8

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the deployment quickstart and deploy/deploy.py, following the setup and start commands from the report. Trace the Fief login configuration that produces “Authorize: Unknown client”; done means the self-hosted dashboard opens successfully after signing in with the Fief admin credentials.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.