Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to set PENPOT_INTERNAL_RESOLVER env var on frontend deployment #12

Open
a3nick opened this issue Dec 12, 2024 · 2 comments · May be fixed by #13
Open

Unable to set PENPOT_INTERNAL_RESOLVER env var on frontend deployment #12

a3nick opened this issue Dec 12, 2024 · 2 comments · May be fixed by #13

Comments

@a3nick
Copy link

a3nick commented Dec 12, 2024

The Helm chart does not allow to set the environment variable PENPOT_INTERNAL_RESOLVER needed for the deployment of the frontend in a k8s cluster as described here penpot/penpot#3310.
The side effect is that assets (images, etc.) are saved correctly but are not served by the frontend due to the default value of the resolver in the nginx configuration file which is set to 127.0.0.11.
@vipinjn24
Copy link

I am facing the same issue here, the logs says that the dns is not resolved and the connection times out.

2024/12/19 10:00:42 [error] 17#17: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/19 10:00:47 [error] 17#17: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/19 10:00:52 [error] 17#17: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/19 10:00:57 [error] 17#17: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/19 10:01:02 [error] 17#17: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/19 10:01:07 [error] 17#17: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/19 10:01:12 [error] 17#17: *47 minio.REDACTED could not be resolved (110: Operation timed out) while sending to client, client: 10.244.130.151, server: _, request: "GET /assets/by-id/1d7970d0-f032-45e4-9227-f199eda296d7 HTTP/1.1", host: "REDACTED", referrer: "https://REDACTED/"
10.244.130.151 - - [19/Dec/2024:10:01:12 +0000] "GET /assets/by-id/1d7970d0-f032-45e4-9227-f199eda296d7 HTTP/1.1" 502 552 "https://REDACTED/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36"

@vipinjn24 vipinjn24 linked a pull request Dec 19, 2024 that will close this issue
Open
@vipinjn24
Copy link

I have prepared a PR to resolve this. This can be deployed in next version.

However if you need you can use the fork that i created and use the devel readme to deploy the modified chart for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added resolver for frontend. vipinjn24/penpot-helm
2 participants
@vipinjn24 @a3nick