Add Fix Explanation for Rexctl Doctor Issues

(#4428) Feature Open: Under consideration self-hosting

Current problem

rexctl doctor is able to identify issues, but it does not tell you how it will attempt to fix those issues.

Proposed change

Provide another flag that we can use with rexctl doctor, to where a server operator can run something like rexctl doctor --how where doctor will show the steps/commands that it will perform to attempt to fix your issue. This allows you to determine if the issue that doctor is reporting is legitimate, or if you have your server set up a specific way by design that doctor is perceiving as an issue when it might not be.

Platform

Self-hosting

Additional information

This is an example of what my rexctl doctor output looks like:
user@fluxer:~$ rexctl doctor
✓ Docker 29.9.2 is running.
✓ This machine has 8 GB of memory.
✓ This machine has 60 GB of free disk space.
✓ *** points to A.A.A.A.
✓ rexctl keeps all of your instance's settings.
✓ Fluxer's files are all in place.
✓ Fluxer starts with this machine.
✓ Your instance's address is *** everywhere.
✓ Browser notifications are set up.
✓ Fluxer is running.
✓ Every Fluxer service runs the version on this machine.
✓ Fluxer answers on this machine.
✓ Apps are told to connect to ***.
✓ The web app loads.
✓ Fluxer can sign in to its database.
✓ The database password works with this release.
! Voice calls use A.A.A.A and this machine's public IP address is B.B.B.B.
  Run rexctl doctor --fix to use B.B.B.B.
✓ People who use your instance show their own IP addresses.
✓ Your last backup is from 27 October.
! Memory overcommit is off, so Fluxer's cache can fail to save data when memory runs low.
  Run rexctl doctor --fix to turn it on.
In this specific output, rexctl doctor is telling me that my domain points to the correct IP of A.A.A.A, yet it's flagging A.A.A.A as an incorrect IP for voice calls because the VM sees a different WAN IP of B.B.B.B. For my specific instance, this is happening because I'm using a Pangolin tunnel, which allows me to expose my Fluxer server at A.A.A.A when the server's IP is actually B.B.B.B. Therefore, this actually isn't supposed to be an issue for me and I am able to confirm with my users that voice calls work with the current configuration.

Comments

Sign in with Fluxer to comment and vote.

No comments yet.