Question 1

Why do file uploads timeout in Sharry, and how to fix it?

Accepted Answer

The upload timeout typically occurs when `sharry.restserver.base-url` is still set to the default `http://localhost:9090`. After deploying Sharry behind a reverse proxy, Cloudflare Tunnel, or any external hostname, you must update `base-url` in `sharry.conf` to the actual public URL (e.g., `https://files.example.com`). This ensures the client can reach the correct backend for chunked uploads. Restart Sharry after changing the configuration. If the issue persists, check browser console logs for failed POST requests and verify the proxy forwards all traffic correctly.

Question 2

How to allow public access to Sharry shares and aliases when using reverse proxy authentication like Authentik?

Accepted Answer

Configure your reverse proxy to bypass authentication for the following paths using Go-compatible regex patterns: ^/app/open/[a-zA-Z1-9-]+, ^/app/share/[a-zA-Z1-9-]+, ^/app/assets/.*, ^/api/v2/open/.*, ^/api/v2/alias/.*. This ensures published shares and aliases remain accessible without login while keeping all other endpoints protected. Verify that sensitive paths (e.g., admin, user management) are not accidentally exposed.

Question 3

How to fix 'FATAL: database "dbuser" does not exist' error when running Postgres in Docker?

Accepted Answer

This error means the Postgres container has no database named 'dbuser'. To fix: 1) Ensure your docker-compose.yml sets `POSTGRES_DB=dbuser` (or omit `POSTGRES_DB` to auto-create a database matching `POSTGRES_USER`). 2) Verify your app’s database connection string matches the actual database name. 3) Check for name collisions: if another Postgres container with the same name runs on the default Docker network, stop it or rename your container. Example working configuration:

```yaml
services:
  db:
    image: postgres:17.1
    container_name: postgres_db
    environment:
      - POSTGRES_USER=dbuser
      - POSTGRES_PASSWORD=dbpass
      - POSTGRES_DB=dbuser  # must match the database your app expects
    healthcheck:
      test: pg_isready -d dbuser
```

As a manual workaround, create the database via `docker exec <container> createdb -U dbuser dbuser`.

sharry

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects