opnsense / opnsense/plugins

DNSCrypt-Proxy keeps stopping every day

Open
#5,581 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
1.2k
Forks
863
Avg merge
2d 6h
Merged PRs (30d)
10

Description

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug
Every morning I wake up to find that the dnscrypt-proxy service has stopped, and that I need to start it back up again.

Did not have this issue till I upgraded from 26.1.11 to 26.7.1, so the major upgrade has not played well with DNScrypt-proxy

Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)

To Reproduce
Steps to reproduce the behavior:
Go from having a 26.1.x setup with DNSCrypt-proxy being the DNS server that is used with also having
DNSBL setup, then upgrade to 26.7.1 and then it should fail

Expected behavior
DNScrypt-proxy to always be running

Screenshots
If applicable, add screenshots to help explain your problem.

Relevant log files
If applicable, information from log files supporting your claim.

Additional context
I have looked in the UI at DNScrypt-proxy log files and it shows nothing in there why it stopped, so currently I am a bit stumped but need this resolved ASAP

Environment
Software version used and hardware type if relevant.
e.g.:

Versions
OPNsense 26.7.1_1-amd64
FreeBSD 15.1-RELEASE-p1
OpenSSL 3.5.7
and the hardware is https://bsd-hardware.info/?probe=e4978fbdcd

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the upgrade from OPNsense 26.1.x to 26.7.1 with DNSCrypt-proxy and DNSBL enabled. Inspect the DNSCrypt-proxy service state and the UI log files around the failure, since the report says they currently show no cause. Done means the service remains running after the upgrade and through the following day.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.