Unix socket configuration doesn't work #2067

Closed
opened 2026-03-22 13:54:21 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @eirnym on GitHub (Jan 20, 2025).

Description

NOTE: configuration below worked earlier (from few months ago, I haven's saved version, sorry) and server is working using TCP socket

I have configuration which runs vikunja service using unix sockets. Previously it worked like a charm, and currently, server doesn't respond at all.

my config.yaml is following:

service:
  unixsocket: /path/to/vikunja.example.com.sock
  unixsocketmode: 0o666
  publicurl: https://vikunja.example.com
  enableemailreminders: false

domain and TLS has been setup on nginx. Previously vikunja also responded when I've used curl:

curl -X GET --unix-socket /path/to/vikunja.example.com.sock http://vikunja.example.com/

I've tried to enable full logging and put logging everywhere, but it doesn't worked

Vikunja Version

Vikunja version v0.24.1-713-debdcd4dd3

Browser and version

Firefox, curl

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @eirnym on GitHub (Jan 20, 2025). ### Description NOTE: configuration below worked earlier (from few months ago, I haven's saved version, sorry) and server is working using TCP socket I have configuration which runs vikunja service using unix sockets. Previously it worked like a charm, and currently, server doesn't respond at all. my `config.yaml` is following: ```yaml service: unixsocket: /path/to/vikunja.example.com.sock unixsocketmode: 0o666 publicurl: https://vikunja.example.com enableemailreminders: false ``` domain and TLS has been setup on nginx. Previously vikunja also responded when I've used curl: ```zsh curl -X GET --unix-socket /path/to/vikunja.example.com.sock http://vikunja.example.com/ ``` I've tried to enable full logging and put logging everywhere, but it doesn't worked ### Vikunja Version Vikunja version v0.24.1-713-debdcd4dd3 ### Browser and version Firefox, curl ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Jan 20, 2025):

What kind of error do you see?

@kolaente commented on GitHub (Jan 20, 2025): What kind of error do you see?
Author
Owner

@eirnym commented on GitHub (Jan 20, 2025):

I see no error, curl/browser just waits for nothing and I see nothing in logs.

@eirnym commented on GitHub (Jan 20, 2025): I see no error, curl/browser just waits for nothing and I see nothing in logs.
Author
Owner

@eirnym commented on GitHub (Jan 20, 2025):

To narrow down search I tried tags and found that v0.24.6 works perfectly. Probably, something wrong happened since last release.

@eirnym commented on GitHub (Jan 20, 2025): To narrow down search I tried tags and found that `v0.24.6` works perfectly. Probably, something wrong happened since last release.
Author
Owner

@eirnym commented on GitHub (Jan 20, 2025):

full config with all logging and all important options set (most of them are default, but I've searched for a solution)

---
service:
  unixsocket: /path/to/vikunja.example.com.sock
  unixsocketmode: 0o666
  publicurl: https://vikunja.example.com
  enableemailreminders: false
log:
  enabled: true
  level: DEBUG
  echo: stdout
  database: true
  databaselevel: DEBUG
  events: stdout
  eventslevel: DEBUG

ratelimit:
  enabled: false
sentry:
  enabled: false
typesense:
  enabled: false
redis:
  enabled: false
mailer:
  enabled: false
migration:
  todoist:
    enabled: false
  trello:
    enabled: false
  microsofttodo:
    enabled: false
auth:
  openid:
    enabled: false
metrics:
  enabled: false
autotls:
  enabled: false
@eirnym commented on GitHub (Jan 20, 2025): full config with all logging and all important options set (most of them are default, but I've searched for a solution) ```yaml --- service: unixsocket: /path/to/vikunja.example.com.sock unixsocketmode: 0o666 publicurl: https://vikunja.example.com enableemailreminders: false log: enabled: true level: DEBUG echo: stdout database: true databaselevel: DEBUG events: stdout eventslevel: DEBUG ratelimit: enabled: false sentry: enabled: false typesense: enabled: false redis: enabled: false mailer: enabled: false migration: todoist: enabled: false trello: enabled: false microsofttodo: enabled: false auth: openid: enabled: false metrics: enabled: false autotls: enabled: false ```
Author
Owner

@kolaente commented on GitHub (Jan 21, 2025):

Looks like this was introduced in daa7ad053c.

Now fixed in b85befb86a, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

@kolaente commented on GitHub (Jan 21, 2025): Looks like this was introduced in daa7ad053c35a97933ca79aee007c388538bab5d. Now fixed in b85befb86abd6dc5bfb09d9ebaee8a736d1688e6, please check with the next unstable build (should be ready for deployment in ~45min, also on [try](https://try.vikunja.io)).
Author
Owner

@eirnym commented on GitHub (Jan 21, 2025):

Thank you for fast response and fix, now it works well

@eirnym commented on GitHub (Jan 21, 2025): Thank you for fast response and fix, now it works well
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2067