GLOSSA LISTEN DOCUMENTATION · SERVER

Reverse proxy and HTTPS

Applies to Glossa Listen v1.0.0

A reverse proxy gives your Glossa Listen server one public HTTPS address. It receives requests from browsers and mobile apps, then passes them to the Glossa Listen container on the private network.

Configuration examples coming soon

This page explains the setup and the choices involved. Exact Caddy, Nginx, or Traefik configuration will be added after the supported deployment layout and hostname are confirmed.

How a reverse proxy works

A listener enters a Glossa Listen URL such as https://glossa.example.com. DNS points that name to the server running the proxy. The proxy handles the HTTPS connection and forwards the request to Glossa Listen's private HTTP address. Glossa Listen sends its response back through the proxy to the listener.

Listener device → DNS name → HTTPS reverse proxy → Glossa Listen container

The proxy is the public entry point. The Glossa Listen container can stay reachable only on the Docker network or local host, depending on your deployment. The same URL should work in a browser and in the mobile app's server field.

Before configuring it

  • Have the Glossa Listen container running and confirm its local address and port.
  • Choose a hostname you control and point its DNS record to the server's public address.
  • Choose the reverse proxy already used on the host, or plan to install one.
  • Arrange a valid TLS certificate for the hostname so devices can use HTTPS.

See the Docker setup for the current local start and storage notes.

What the proxy must pass through

Route requests for the Glossa Listen hostname to the Glossa Listen service's internal address and port. Preserve the requested host and tell Glossa Listen that the original connection used HTTPS, using the proxy's normal forwarding headers. If the supported Glossa Listen release uses upgraded connections for live features, its final configuration example will include those headers as well.

A path prefix such as example.com/glossa may require application support for that base path. Use a dedicated hostname for the draft setup until path-prefix support is confirmed.

Check the finished connection

  1. Open the public HTTPS URL from a device outside the server's local network.
  2. Confirm the browser shows a valid certificate and the Glossa Listen sign-in page.
  3. Sign in, open a book, and start playback.
  4. Enter the same URL in the iOS or Android sign-in screen and confirm the library loads.

If the page opens but playback fails, inspect the proxy's upstream routing and Glossa Listen's logs. If the mobile app cannot connect, check DNS, certificate validity, and whether the app is using the public HTTPS URL.

Details to add to this guide

  • A complete configuration for each supported proxy, with the verified Glossa Listen upstream port.
  • Certificate issuance and renewal for the chosen deployment.
  • Required forwarding and connection-upgrade headers for the current Glossa Listen release.
  • Firewall and Docker network examples, plus a troubleshooting table.
Continue setting up your libraryCreate the administrator account