service name does not exist (Temporary failure in name resolution)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- haskell
- Domain
- networking
Research direction
Start at src/Simplex/Messaging/Server.hs:1555, where the connect error is logged, and trace how a client address is resolved and how a failed connection is retried or abandoned. The reported symptom is that resolution failures leave the server unable to reconnect until restart, so compare that retry path with the Docker DNS behaviour described for the self-hosted deployment. Done looks like the server recovering on its own after a transient getAddrInfo failure, verified by reproducing the failure in a test or local Docker setup rather than a one-line change.
Written by the indexing model from the issue text.
Description
I am experiencing intermittent issues with my self-hosted SMP server where messages are neither sent nor received reliably.
The issue has occurred with both the current release (v7.1.0.18) and the previous release.
When checking the server logs, I see the followijng warning:
[WARN 2026-11-15 12:58:22 +0000 src/Simplex/Messaging/Server.hs:1555] Error connecting: smp18.simplex.im,lyqpnwbs2zqfr45jqkncwpywpbtq7jrhxnib5qddtr6npjyezuwd3nqd.onion PCENetworkError (NEConnectError {connectError = "Network.Socket.getAddrInfo (called with preferred socket type/protocol: AddrInfo {addrFlags = [], addrFamily = AF_UNSPEC, addrSocketType = Stream, addrProtocol = 0, addrAddress = 0.0.0.0:0, addrCanonName = Nothing}, host name: Just \"smp18.simplex.im\", service name: Just \"5223\"): does not exist (Temporary failure in name resolution)"})
The error appears to indicate a temporary DNS resolution failure when the server attempts to resolve smp18.simplex.im. The same also happens when trying to resolve my own internal smp-server via FQDN.
Environment:
- Deployment: Self-hosted SMP server running in Docker
- SMP server version: 7.1.0.18
- Previous version: Same issue observed with the previous release
Observed behavior
- The server stops sending and recieving messages, but client reports no connection problems to it.
- The logs contain repeated DNS resolution errors when attempting to connect to the smp-servers FQDN and other SMP servers.
- Restarting the smp-server docker container resolves the issue.
The issue has been observed across two consecutive releases.
Expected behaviour
The SMP server should maintain reliable connectivity to other SMP servers and recover gracefully from temporary DNS resolution failures without requiring a manual container restart.
Happy to provide additional logs or configuration details if needed.
- Dominant language
- Haskell
- Stars
- 865
- Forks
- 125
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 64
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from simplex-chat/simplexmq
-
xftp CLI: Generated web link is missing the /file pathPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
simplex-chat/simplexmq#1853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
simplex-chat/simplexmq#1781 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
simplex-chat/simplexmq#2017 ·
Maintainers usually reply within 1 day
-
resolver: resolve .simplex names, on smp7 and then on the preset routersPossibly taken @shumvgolove claimed this 18 days ago. Open
simplex-chat/simplexmq#2011 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
simplex-chat/simplexmq#1864 ·
Maintainers usually reply within 1 day
All issues in simplex-chat/simplexmq
Similar issues
-
bug desktop
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
simplex-chat/simplex-chat#8291 ·
Maintainers usually reply within 1 day
-
[BUG]: C# programs with top-level statements fail to compilePossibly taken @AsyncNigam claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
compiler-explorer/compiler-explorer#9625 · 1 comment ·
Maintainers usually reply within 1 day
-
needs triage type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
reflex-0.10Open
Difficulty 1/5 Under an hour Newbie friendliness 62/100
commercialhaskell/stackage#8180 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenZeppelin/canton-contracts#140 ·
Maintainers usually reply within 1 day