ERR_SSL_UNRECOGNIZED_NAME_ALERT on Nginx Proxy Manager host

[sterile dirge]

I'm trying to use Nginx Proxy Manager in combination with Authentik. When I use NPM alone with my service it works fine, but when I'm adding the Authentik config from https://docs.goauthentik.io/docs/providers/proxy/server_nginx in the Advanced tab in NPM I'm not able to access the service anymore as the browser shows a ERR_SSL_UNRECOGNIZED_NAME_ALERT error.

Is it impossible to use Authentik with NPM and OAuth providers?

[undone arch]

did you set it up in the outspost? also i don't think the new documents work

try this, replace http://IPADDRESS:PORT/outpost.goauthentik.io;

# This is needed only if you get 'upstream sent too big header while reading response
# header from upstream' error when trying to access an application protected by goauthentik
proxy_buffers 8 16k;
proxy_buffer_size 32k;

# Make sure not to redirect traffic to a port 4443
port_in_redirect off;

location / {
    # Put your proxy_pass to your application here
    proxy_pass          $forward_scheme://$server:$port;
    # Set any other headers your application might need
    # proxy_set_header Host $host;
    # proxy_set_header ...

    ##############################
    # authentik-specific config
    ##############################
    auth_request     /outpost.goauthentik.io/auth/nginx;
    error_page       401 = @goauthentik_proxy_signin;
    auth_request_set $auth_cookie $upstream_http_set_cookie;
    add_header       Set-Cookie $auth_cookie;```

    auth_request_set $authentik_username $upstream_http_x_authentik_username;
    auth_request_set $authentik_groups $upstream_http_x_authentik_groups;
    auth_request_set $authentik_email $upstream_http_x_authentik_email;
    auth_request_set $authentik_name $upstream_http_x_authentik_name;
    auth_request_set $authentik_uid $upstream_http_x_authentik_uid;

    proxy_set_header X-authentik-username $authentik_username;
    proxy_set_header X-authentik-groups $authentik_groups;
    proxy_set_header X-authentik-email $authentik_email;
    proxy_set_header X-authentik-name $authentik_name;
    proxy_set_header X-authentik-uid $authentik_uid;
}

# all requests to /outpost.goauthentik.io must be accessible without authentication
location /outpost.goauthentik.io {
    proxy_pass              http://IPADDRESS:PORT/outpost.goauthentik.io;
    # ensure the host of this vserver matches your external URL you've configured
    # in authentik
    proxy_set_header        Host $host;
    proxy_set_header        X-Original-URL $scheme://$http_host$request_uri;
    add_header              Set-Cookie $auth_cookie;
    auth_request_set        $auth_cookie $upstream_http_set_cookie;
    proxy_pass_request_body off;
    proxy_set_header        Content-Length "";
}

# Special location for when the /auth endpoint returns a 401,
# redirect to the /start URL which initiates SSO
location @goauthentik_proxy_signin {
    internal;
    add_header Set-Cookie $auth_cookie;
    return 302 /outpost.goauthentik.io/start?rd=$request_uri;
    # For domain level, use the below error_page to redirect to your authentik server with the full redirect path
    # return 302 https://authentik.company/outpost.goauthentik.io/start?rd=$scheme://$http_host$request_uri;
}```

combine both messages, i couldnt post it all at once

[sterile dirge]

Thanks for the reply! I've created an OAuth provider for it, but that one can't even be selected in the outpost

The list is just empty

[sterile dirge]

With your code I'm not getting an SSL error anymore though, thanks for that, but I'm getting a 500 now. But at least that's progress!

[undone arch]

was there a default outpost already created in authentik?

[glossy latch]

I'm having the same issues. The default outpost, in my case, works but the curl -vs -o /dev/null http://<server_address>/outpost.goauthentik.io/ping responds 404. Also visiting the outpost address results in an Authentik error message that says "not found"

[empty girder]

i also get a 500

[empty girder]

visiting it also gives me not found but the ping works

wait no

it also says 404

@glossy latch @sterile dirge yall i think i fixed the 500

go to your outpost

enable docker integration

then add your app

shit

well

different issue

went to 502 bad gateway next

ugh

oh!

its bc i didnt allow that port thru firewall

sorry

i have a weird setup

yep that was the issue

fixed