trusted-origins argument incorrectly quoted causing origin validation errors
Description
The Portainer Helm chart currently generates the --trusted-origins argument with extra double quotes around the domain value due to the use of the quote filter in the template. This causes Portainer to reject the origin with an origin invalid error.
Steps to Reproduce
- Deploy Portainer with
trusted_origins.domains set in values.yaml to portainer.example.com.
- The Pod receives the argument as
--trusted-origins="portainer.example.com" (including the quotes).
- Portainer logs show the error:
Failed to validate Origin or Referer | error="origin invalid"
Suggested Fix
Remove the quote filter from the template so that the argument is passed without extra quotes:
- '--trusted-origins={{ .Values.trusted_origins.domains | trim }}'
This results in the argument being:
--trusted-origins=portainer.example.com
which Portainer accepts correctly.
Additional Notes
This issue causes confusion and requires manual workarounds to avoid invalid origin errors in Portainer deployments behind reverse proxies.
Thank you for considering this fix!
trusted-originsargument incorrectly quoted causing origin validation errorsDescription
The Portainer Helm chart currently generates the
--trusted-originsargument with extra double quotes around the domain value due to the use of thequotefilter in the template. This causes Portainer to reject the origin with anorigin invaliderror.Steps to Reproduce
trusted_origins.domainsset invalues.yamltoportainer.example.com.--trusted-origins="portainer.example.com"(including the quotes).Suggested Fix
Remove the
quotefilter from the template so that the argument is passed without extra quotes:- '--trusted-origins={{ .Values.trusted_origins.domains | trim }}'This results in the argument being:
which Portainer accepts correctly.
Additional Notes
This issue causes confusion and requires manual workarounds to avoid invalid origin errors in Portainer deployments behind reverse proxies.
Thank you for considering this fix!