Edit history

Earlier versions of [Self-hosted] FLUXER_PUBLIC_PORT is ignored by several generated public endpoints when using a non-standard HTTPS port, newest first.

Current version | Edited by Rex
Changes
```Removed: ### EnvironmentVersion: main (also reproduced on v1)Deployment: Docker ComposeReverse proxy: Nginx Proxy ManagerOS: Ubuntu 24.04Browser: Chrome### Logs or screenshotsExample response from /.well-known/fluxer:```JSON{ "endpoints": { "api": "https://chat.example.com:4443/api", "gateway": "wss://chat.example.com:4443/gateway", "media": "https://chat.example.com/media", "marketing": "https://chat.example.com" }}```Browser attempts to connect to:`wss://chat.example.com/livekit`[image](https://feedback.fluxer.com/p/700#f-702)Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched existing issues.Removed: - ☑ I wrote this report in my own words, except for direct translation if needed.
Show

[Self-hosted] FLUXER_PUBLIC_PORT is ignored by several generated public endpoints when using a non-standard HTTPS port

Summary

I'm self-hosting Fluxer behind Nginx Proxy Manager. My ISP blocks ports 80 and 443, so Fluxer is exposed on HTTPS port 4443. Configuration:
FLUXER_PUBLIC_SCHEME=https
FLUXER_PUBLIC_PORT=4443
FLUXER_DOMAIN=chat.example.com
Some generated public endpoints correctly include :4443, while others ignore FLUXER_PUBLIC_PORT. For example, /.well-known/fluxer returns: api: https://chat.example.com:4443/api ✅ gateway: wss://chat.example.com:4443/gateway ✅ media: https://chat.example.com/media ❌ marketing: https://chat.example.com/ ❌ This also affects LiveKit. The client attempts to connect to: wss://chat.example.com/livekit ❌ instead of: wss://chat.example.com:4443/livekit As a result, voice channels cannot be joined when the instance is only exposed on the configured public port. I expected all generated public URLs to consistently respect FLUXER_PUBLIC_PORT.

Steps to reproduce

1. Deploy Fluxer with:
   - `FLUXER_PUBLIC_SCHEME=https`
   - `FLUXER_PUBLIC_PORT=4443`
2. Open `/.well-known/fluxer`.
3. Compare the generated endpoints.
4. Notice that some endpoints include `:4443`, while others do not.

Environment

Version: main (also reproduced on v1) Deployment: Docker Compose Reverse proxy: Nginx Proxy Manager OS: Ubuntu 24.04 Browser: Chrome

Logs or screenshots

Example response from /.well-known/fluxer:
{
  "endpoints": {
    "api": "https://chat.example.com:4443/api",
    "gateway": "wss://chat.example.com:4443/gateway",
    "media": "https://chat.example.com/media",
    "marketing": "https://chat.example.com"
  }
}
Browser attempts to connect to: wss://chat.example.com/livekit image
Original by Rex
Show

[Self-hosted] FLUXER_PUBLIC_PORT is ignored by several generated public endpoints when using a non-standard HTTPS port

Summary

I'm self-hosting Fluxer behind Nginx Proxy Manager. My ISP blocks ports 80 and 443, so Fluxer is exposed on HTTPS port 4443. Configuration:
FLUXER_PUBLIC_SCHEME=https
FLUXER_PUBLIC_PORT=4443
FLUXER_DOMAIN=chat.example.com
Some generated public endpoints correctly include :4443, while others ignore FLUXER_PUBLIC_PORT. For example, /.well-known/fluxer returns: api: https://chat.example.com:4443/api ✅ gateway: wss://chat.example.com:4443/gateway ✅ media: https://chat.example.com/media ❌ marketing: https://chat.example.com/ ❌ This also affects LiveKit. The client attempts to connect to: wss://chat.example.com/livekit ❌ instead of: wss://chat.example.com:4443/livekit As a result, voice channels cannot be joined when the instance is only exposed on the configured public port. I expected all generated public URLs to consistently respect FLUXER_PUBLIC_PORT.

Steps to reproduce

1. Deploy Fluxer with:
   - `FLUXER_PUBLIC_SCHEME=https`
   - `FLUXER_PUBLIC_PORT=4443`
2. Open `/.well-known/fluxer`.
3. Compare the generated endpoints.
4. Notice that some endpoints include `:4443`, while others do not.

Environment

Version: main (also reproduced on v1) Deployment: Docker Compose Reverse proxy: Nginx Proxy Manager OS: Ubuntu 24.04 Browser: Chrome

Logs or screenshots

Example response from /.well-known/fluxer:
{
  "endpoints": {
    "api": "https://chat.example.com:4443/api",
    "gateway": "wss://chat.example.com:4443/gateway",
    "media": "https://chat.example.com/media",
    "marketing": "https://chat.example.com"
  }
}
Browser attempts to connect to: wss://chat.example.com/livekit image

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.