FAQ

I deleted my containers and reinstalled the C2 but I get an error saying a migration failed when trying to start the C2.

Make sure you delete your docker volumes as well as containers when doing a fresh build.

I have built this on localhost but I cannot login and/or a beacon will not call back?

You most likely have not configured your TLS certificates for use on localhost. I have provided a guide on how to do this - ensure you follow that. If you have followed that correctly, please raise an issue on the repo.

My client received a 502 error from the C2, what has gone wrong?

A 502 generally indicates in this ecosystem a panic (either explicit or via a .unwrap() or .expect()). Check the error logs in your C2 Docker container under /data/logs/error.log. For example, a 502 is returned by me entering a .expect() somewhere which is guaranteed to fail for demonstration purposes:

log error

It is also worth saying, a panic does not mean your server will crash, simply that request will ‘crash’. Thanks to the magic of Rust & Axum the C2 will remain stable.

After pulling an update my web server is not working right?

Read the release notes, ensure you do a clean build of changed components, usually:

  • docker compose up -d --build c2
  • docker compose up -d --build nginx
  • docker compose up -d --build client

And make sure to restart nginx for it to have ingested the latest configs.

  • docker compose restart nginx

Sometimes I don’t see the output of the first (few) commands

There’s currently a bug which only happens on rare occasion, where the first few results don’t show in the terminal, but they are being added to your client properly. Do a refresh of the page and they should appear. This bug is irking me, I cannot seem to find it. It likely has something to do with how Leptos is deciding whether (or not) to render the messages.