Embedded outpost not accessible | Docker 2024.2.2

[weary comet]

I've just deployed authentik and am looking to start using it to secure proxied domains through npm.
I have the application and provider setup and assigned to the embedded outpost, but when I attempt to access the embedded outpost at either the internal ip (https://sevenofnine:90/outpost.goauthentik.io/ping) or after the reverse proxy, authentik seems to only return a 404.
Pages configured to require authentication return a 500. Anything I can try to make the embedded outpost actually work?

[vapid gull]

A good playlist of videos to follow for first time setups

https://youtube.com/playlist?list=PLH73rprBo7vSkDq-hAuXOoXx2es-1ExOP&si=bxP0s3CwoKOS2DKn

[weary comet]

@vapid gull Yea, so I already have the application and everything setup. The problem I'm running into through is that the endpoint for https://auth.example.com/outpost.goauthentik.io/ping returns a 404. The documentation lists that as a troubleshooting step (and explicitly states that it should be available), but not anything to try to resolve it. I don't believe it's an issue with the proxy because the endpoint doesn't exist on either side of the proxy. /outpost.goauthentik.io/auth/nginx is also unavailable

[vapid gull]

I'm not exactly sure how to fix this, as this doesn't seem to work for me either

[weary comet]

Is there anything I could be missing in the outpost config?

[vapid gull]

Not that I see. The only thing I changed in this was the url that you have blanked out.

[weary comet]

Actually, I have it figured out. Apparently it seems to work if I use the http port?