Access for added locations

[Nextnx]

Hi

Im trying to switch from caddy and have a problem where I need custom locations to be public and the rest(base) behind auth.

My working caddy config is:

n8n.domain.com {
    tls {$EMAIL}

    handle /webhook-test/* {
        reverse_proxy http://192.168.81.7:5678 {
            header_up X-Real-IP {remote_host}
        }
    }
    handle /webhook/* {
        reverse_proxy http://192.168.81.7:5678 {
            header_up X-Real-IP {remote_host}
        }
    }

    import allowHosts << this is allow on ip, but any auth could be here

    reverse_proxy http://192.168.81.7:5678 {
        header_up X-Real-IP {remote_host}
    }
}

I see I cannot add multiple proxy host of same domain, even if there's a path added. I assume this is per design.
I can add custom location but they are under same auth(basic) as base domain. So I'm looking for the option to set a different auth(or none) on those custom locations or is there another way?

I see auth_request command but not sure howto make it work.
I tried setting auth_request off on a custom location "/webhook" but site status goes offline when saved and I get the "Congratulations" page.

Any help is appreciated. Thanks

[Zoey2936]

what kind of auth do you mean? basic auth?

[Nextnx]

Basic or ip, but prefer basic

[Zoey2936]

for the custom locations you can press the gear button and put auth_basic off; (to disable basic auth) and/or allow all; (to disable ip blockin) in the text box.

[Nextnx]

or if possible use the access list for this

[Zoey2936]

I want to improve auth lists for custom locations in a furture release

[Nextnx]

Thanks will try.

[Nextnx]

auth_basic off; Worked.
allow all; Did not work. It request basic still.
Thanks. Looking forward for more option in future. I appreciate your help and the work you do here 🥇

[amir1376irani]

@Zoey2936 @DavidCraftDev
Hi there,

First off, thanks for this great project – I use it for every project of mine :)

I have a similar need. I'm using NPMplus to manage api.x.ir (in proxy host section), which points to my backend service. I want to protect only the /swagger/ endpoint with Basic Authentication, while keeping the rest public.

I've already created an Access List with my credentials. However, in the "Custom Locations" section of my proxy host, I don't see any option to apply that Access List to a specific location (e.g., /swagger/).

Is it currently possible to do this through the UI? If not, could this be considered as a feature request?

Thank you!

[Zoey2936]

hello, this feauture was merged a few weeks ago and will be released in the future