Skip to content

Baikal authentication error #93

Description

@AkilisUi

What's happening, or what would you like?
I try to add a self-hosted Baikal calendar to Tymeslot but can't get it to connect. The error it's throwing is something along the lines of Authentication failed for tha calendar provider. Please double check your username and password. Check your credentials again and make sure they did not expire. (translated by me from french).
Of course I checked everything I could, from my Baikal docker setup to the whole Tymeslot setup (docker too) and its env file but couldn't figure the issue.
I can access my Baikal setup pretty much everywhere and from outside my local network (reverse proxied with ssl).

If it's a bug, how can we reproduce it? (optional)
Here are my compose and env :

services:
  tymeslot:
    image: luka1thb/tymeslot:latest
    container_name: tymeslot
    restart: unless-stopped
    ports:
      - "${PORT:-4000}:${PORT:-4000}"
    env_file:
      - .env
    environment:
      DEPLOYMENT_TYPE: docker
    volumes:
      - tymeslot_data:/app/data
      - tymeslot_pg:/var/lib/postgresql/data

volumes:
  tymeslot_data:
    name: tymeslot_data
  tymeslot_pg:
    name: tymeslot_pg

networks:
  default:
    name: tymeslot_network
SECRET_KEY_BASE=xxxx
PHX_HOST=tymeslot.example.com (modified of course)
POSTGRES_PASSWORD=My-strong-password

PORT=4000

REGISTRATION_ENABLED=false

EMAIL_ADAPTER=smtp
EMAIL_FROM_NAME="Me"
EMAIL_FROM_ADDRESS="mymail@myprovider.com"
SMTP_HOST=my.provers.host.adress
SMTP_PORT=587
SMTP_USERNAME=mymail@myprovider.com
SMTP_PASSWORD=my-super-mail!passw




ENABLE_GOOGLE_AUTH=false
ENABLE_GITHUB_AUTH=false

# GITHUB_CLIENT_ID=
# GITHUB_CLIENT_SECRET=

ENABLE_OAUTH_AUTH=false

# OAUTH_CLIENT_ID=
# OAUTH_CLIENT_SECRET=
# OAUTH_PROVIDER_URL=      # Base URL of your identity provider (e.g. https://keycloak.example.com)
# OAUTH_AUTHORIZE_URL=     # Authorization endpoint (must be HTTPS)
# OAUTH_TOKEN_URL=         # Token endpoint (must be HTTPS)
# OAUTH_USERINFO_URL=      # Userinfo endpoint (must be HTTPS)

# OAUTH_SCOPE=openid email profile

Anything else? (version, deployment type, logs — please redact anything sensitive)

I can see in my Baikal logs that I'm trying to access my caldav from Tymeslot every time I click the retrieve button. It says 10.0.38.1 - username [08/Sep/2026:18:10:53 +0000] "PROPFIND /dav.php/calendars/username/calendarname HTTP/1.1" 401 436 "-" "req/0.7.4" "192.168.1.254"

192.168.1.254 is my router's local ip so I wonder if I have to export some specific port for Tymeslot to retrieve the info it needs from Baikal. It doesn't seem relevant to me since ports 8080 and 443 are already exposed for all my reverse proxy configs to work and I can already access Baikal from the web, calendars apps on my smartphone and mails app pretty much everywhere.

I have also tried the (irrelevant) ALLOW_PRIVATE_IPS_FOR_CALENDAR line but of course it changed nothing since it's docker + reverse proxy.
Also, I have set a MiroTalk app on Docker with reverse proxy too that paired succesfully with Tymeslot, so I guess it can actually access apps.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions