[Self-Hosted] Gateway NATS connection lost, reconnecting on new (and existing) instances

After creating a new Fluxer instance, I am almost able to complete the setup. However, pressing the "Finish setup" button at the end of setup states "Service unavailable." After updating an existing Fluxer instance, I am able to login and occasionally view some information, such as messages, on the instance. However, I am unable to send any messages, for example, and I showcase this (at least partially) on the new instance. I expect the setup and interface to work as usual.

(1-8 is a bit more setup-specific and was performed on both the working instance (a while back) and the new VM I created today for this issue, so you may want to start at 9)

1. Install Alpine Linux (on a VM in my case; 4 cores, 8GB memory, and 32GB disk, exactly the same as my working instance)
2. Install Caddy from community repository (only used to get the caddy user account setup; this is just something I do for every service): apk add caddy
3. Remove caddy: apk del caddy
4. Install caddy-openrc: apk add caddy-openrc
5. Install Caddy (with Cloudflare support in my case) and configure it
6. Install Docker: apk add docker docker-cli-compose
7. Set Caddy and Docker to run at system startup (probably not required): rc-update add caddy default; rc-update add docker default
8. Start Caddy and Docker: rc-service caddy start; rc-service docker start
9. Get the latest install.sh script (I am in /root): curl -fsSLO https://fluxer.dev/install.sh; curl -fsSLO https://fluxer.dev/install.sh.sha256; sha256sum -c install.sh.sha256
10. Make install.sh executable: chmod +x install.sh
11. Run sh install.sh --domain chat-test.example.com --email someaddress@example.com --tls proxy --allow-root (I will note that there was a slight hiccup where fluxer-api-1 reported as unhealthy on the first startup, but this seemed to be a one-off thing as down and up appeared fixed that, allowing me to see the setup page; I have attached a separate log file from only the first startup of api as it might be another bug)
12. Complete the setup and press "Finish setup"
13. Observe "Service unavailable."
14. Observe (in logs) Gateway NATS pool slot connected, Gateway NATS pool slot connection lost, reconnecting, and Gateway NATS RPC connection error, reconnecting
15. Observe that, if you refresh the page, you might be placed into the usual interface, but attempting to view messages or perform actions does not work, at least without a page refresh each time (which may not work either)

--- Adding on to 12-13, enabling single-community mode (as I have on my main Fluxer instance) is how I found that "Service unavailable" message. However, if you do not enable single-community mode, you will not see the message in that spot, and you are placed into the usual main interface (where you see friends). But, when you try to create a community, for example, you will see it there. Although the message shows up, it appears that a refresh of the page would fetch the new community with its default channels (although you cannot fetch messages, even if you send a message and refresh). In addition, when you create a personal note, you will receive an error message, but refreshing the page also appears to show the new note. My experience has been that you can perform some actions, but your client will not receive anything back from the Fluxer server (perhaps the gateway?) "live;" rather, you need to refresh the page (which, again, may not work).

Stable Web 2026.1003.184159, Linux (x86), Chrome 153.0.0.0, Locale en-US

Single Community Enabled

image This log file includes what occurred when trying to setup with single-community mode enabled: setup-with-single-community-mode-enabled.log

Community

During creation: image After refresh: image

Personal Notes

During creation: image After refresh: image This log file includes what occurred when setting up without enabling single-community mode and then attempting to create a community and personal note (I used a backup of the VM to return to before I first used the install.sh command, effectively starting back at step 11 above): no-single-community-create-community-and-personal-message.log

API service issue

This log file includes the fluxer-api-1 issue I noted when using install.sh for the first time (this only includes the api service logs): api-first-use.log