After creating a server (tested with a Counter-Strike 1.6 server), I ran into a few usability issues that I think would meaningfully improve the day-to-day experience of managing servers through the panel.
- No way to edit the server's startup command after creation
Once a server is created, there doesn't seem to be any way to modify its startup command. It would be very useful to have this editable directly from the panel, without needing to recreate the server from scratch.
- Console output is too noisy / not very useful
The live console prints a large amount of low-value log output that gets in the way more than it helps. For example, sending the simple version command triggers a big block of unrelated log lines (see screenshot) instead of just the actual version info. Filtering out this kind of noise — or making it configurable — would make the console much more usable.
- Console window is too small, and can't be resized
The console panel is quite small, and there's no way to expand it. Being able to resize it (or have a fullscreen/expanded view) would make it much easier to actually read logs and interact with the server.
- More control during installation: custom ports and install path
On my setup, ports 80/443 were already in use by an existing reverse proxy (Coolify/Traefik) running on the same VPS, which is a fairly common setup for anyone self-hosting multiple services. Since the installer doesn't offer a way to configure ports upfront, I had to manually edit the generated docker-compose.yml after installation to move the panel to different ports. That in turn broke the built-in ACME/Let's Encrypt certificate issuance (which requires port 80 for the HTTP challenge), and once the panel was only reachable on non-standard ports, it also triggered CORS errors on login, since the backend's CORS check appears to assume the default domain/port. Being able to set custom ports (and the install path) during setup — or at least documenting how to safely relocate the reverse proxy afterward — would save a lot of trial and error for anyone running this alongside other services.
Thanks for building this, really like the direction of the project — just sharing feedback from actually running it on my own VPS.
After creating a server (tested with a Counter-Strike 1.6 server), I ran into a few usability issues that I think would meaningfully improve the day-to-day experience of managing servers through the panel.
Once a server is created, there doesn't seem to be any way to modify its startup command. It would be very useful to have this editable directly from the panel, without needing to recreate the server from scratch.
The live console prints a large amount of low-value log output that gets in the way more than it helps. For example, sending the simple version command triggers a big block of unrelated log lines (see screenshot) instead of just the actual version info. Filtering out this kind of noise — or making it configurable — would make the console much more usable.
The console panel is quite small, and there's no way to expand it. Being able to resize it (or have a fullscreen/expanded view) would make it much easier to actually read logs and interact with the server.
On my setup, ports 80/443 were already in use by an existing reverse proxy (Coolify/Traefik) running on the same VPS, which is a fairly common setup for anyone self-hosting multiple services. Since the installer doesn't offer a way to configure ports upfront, I had to manually edit the generated docker-compose.yml after installation to move the panel to different ports. That in turn broke the built-in ACME/Let's Encrypt certificate issuance (which requires port 80 for the HTTP challenge), and once the panel was only reachable on non-standard ports, it also triggered CORS errors on login, since the backend's CORS check appears to assume the default domain/port. Being able to set custom ports (and the install path) during setup — or at least documenting how to safely relocate the reverse proxy afterward — would save a lot of trial and error for anyone running this alongside other services.
Thanks for building this, really like the direction of the project — just sharing feedback from actually running it on my own VPS.