[PR #85] [MERGED] fix: add nginx resolver for runtime DNS resolution with variable proxy_pass #88

Closed
opened 2026-08-13 19:11:28 +02:00 by zaph0d · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/niels-emmer/myace/pull/85
Author: @niels-emmer
Created: 8/12/2026
Status: Merged
Merged: 8/12/2026
Merged by: @niels-emmer

Base: mainHead: fix/nginx-resolver


📝 Commits (1)

  • 42ef588 fix: add nginx resolver for runtime DNS resolution with variable proxy_pass

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 frontend/nginx.conf (+4 -0)

📄 Description

Summary

The previous fix (using a variable in proxy_pass for runtime DNS resolution) introduced a new issue: nginx needs an explicit resolver directive when resolving hostnames at runtime via variables. Without it, nginx logs no resolver defined to resolve backend and returns 502.

Fix

Added resolver 127.0.0.11 valid=10s; to the nginx server block. 127.0.0.11 is Docker's embedded DNS resolver; valid=10s sets the cache TTL so DNS is re-resolved every 10 seconds.

Changes

File Change
frontend/nginx.conf Added resolver 127.0.0.11 valid=10s; in server block

Checklist

  • Self-review completed
  • No new warnings
  • Breaking changes: none

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/niels-emmer/myace/pull/85 **Author:** [@niels-emmer](https://github.com/niels-emmer) **Created:** 8/12/2026 **Status:** ✅ Merged **Merged:** 8/12/2026 **Merged by:** [@niels-emmer](https://github.com/niels-emmer) **Base:** `main` ← **Head:** `fix/nginx-resolver` --- ### 📝 Commits (1) - [`42ef588`](https://github.com/niels-emmer/myace/commit/42ef58813126f551881097444e603d4c4d29e831) fix: add nginx resolver for runtime DNS resolution with variable proxy_pass ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `frontend/nginx.conf` (+4 -0) </details> ### 📄 Description ## Summary The previous fix (using a variable in `proxy_pass` for runtime DNS resolution) introduced a new issue: nginx needs an explicit `resolver` directive when resolving hostnames at runtime via variables. Without it, nginx logs `no resolver defined to resolve backend` and returns 502. ## Fix Added `resolver 127.0.0.11 valid=10s;` to the nginx server block. `127.0.0.11` is Docker's embedded DNS resolver; `valid=10s` sets the cache TTL so DNS is re-resolved every 10 seconds. ## Changes | File | Change | |------|--------| | `frontend/nginx.conf` | Added `resolver 127.0.0.11 valid=10s;` in server block | ## Checklist - [x] Self-review completed - [x] No new warnings - [x] Breaking changes: none --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
zaph0d 2026-08-13 19:11:28 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
github-mirrors/myace#88
No description provided.