Skip to content

troubleshooting.md

Latest commit

 

History

History
34 lines (25 loc) · 1.33 KB

troubleshooting.md

File metadata and controls

34 lines (25 loc) · 1.33 KB
title Troubleshooting Weave Flux
menu_order 50

fluxctl returns a 500 Internal Server Error

This usually indicates there's a bug in the flux daemon somewhere -- in which case please tell us about it!

Flux answers everything with git repo is not configured

This means Flux can't read from and write to the git repo. Check that

  • ... you've supplied a git repo URL. If it's of the form https://github.com/user/repo then you will need to use the SSH-style URL, git@github.com:user/repo instead.

  • ... the deploy key has read/write access to the repo. In GitHub, deploy keys are installed in the settings for a repository. To get the deploy key Flux is using, use fluxctl identity.

"The request failed authentication"

If you're using Weave Cloud, this probably means you haven't supplied the token. You can get the token from the settings in Weave Cloud; set the environment variable FLUX_TOKEN to the token.

If you have set Flux up standalone (as in the instructions in ./standalone/installing.md), this probably means Flux is defaulting to using Weave Cloud because you've not set the environment variable FLUX_URL to point at the daemon. See ./standalone/setup.md.