Guidance Needed for Persistent Proxy Bypass Configuration in TrueNAS SCALE

[Kelvin_Maung]

Hello TrueNAS Community,

I am currently running a TrueNAS SCALE server with an HTTP proxy configured. I would like to implement a proxy bypass for specific domains (e.g., localhost, 127.0.0.1, .example.com) using a NO_PROXY setting.

Has anyone successfully implemented a persistent proxy bypass configuration in TrueNAS SCALE? What are the recommended approaches or best practices—such as using custom startup scripts, application-specific environment settings, or middleware customizations—to achieve this?

Any guidance or examples would be greatly appreciated.

Thank you in advance for your assistance.

Best regards,
Kelvin

[ABain]

There are some great items in resources, have you checked out

HOWTO: Host a Service privately on TrueNAS with a valid SSL Certificate

So you want to securely host services on your TrueNAS? Without opening ports on your router and still having easy to remember valid domains with SSL certificates? If so, this guide may be for you. There are many ways to accomplish this, but in this guide we’ll be leveraging the following: TrueNAS SCALE Cloudflare Managed Domain DNS Tailscale App Nginx Proxy Manager App When finished, you will be able to quickly add new services through the Cloudflare DNS Management and Nginx Proxy Manager (NP…

[Kelvin_Maung]

Thank you for your response, @ABain.

To clarify, my inquiry is not regarding hosting. I specifically want to ensure that the CloudSync service does not use the proxy settings. Currently, the HTTP Proxy is configured under the Network settings, which facilitates updates and Slack alerts. However, for CloudSync’s connection to S3, using the proxy will not work. We are leveraging a Private Endpoint for S3 and direct connectivity within our internal network.

So I am trying to find out If we can set NO_PROXY specifically for CloudSync.