Compose-Up Error Related to authentik.Outpost

[adamzvolanek]

Describe the bug
Upon issuing a compose-up on my docker-compose file (similar to the one provided), I am receiving a repeated stream of the below outpost errors. I have seen a previous issue report on it but don't quite identify the solution. My environment file is located on my repo to reference. Note there are some bogus values for obvious reasons.

To Reproduce
Steps to reproduce the behavior:

1. Go to my repo and run up the docker-compose with my environment file with respective environment variables updated to meet your servers IP or Docker network.
2. View on Authentik (not Worker) logs.
3. Result will be repeated.

Expected behavior
I expect errors perhaps about my lack of geoIP implementation however not for anything else? Looking for some insight for direction so these logs are not spammed repeatedly without reason.

Screenshots

Logs
Repeated as seen below.

{"event": "/api/v3/outposts/instances/", "host": "localhost:8000", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 27, "remote": "127.0.0.1", "request_id": "0c265ddd88174822bd6046aaa91f87b9", "runtime": 18, "scheme": "http", "status": 403, "timestamp": "2022-07-19T02:53:37.914673", "user": "", "user_agent": "goauthentik.io/outpost/2022.7.2"}
{"event": "Forbidden: /api/v3/outposts/instances/", "level": "warning", "logger": "django.request", "timestamp": 1658199217.9152439}
{"error":"403 Forbidden","event":"Failed to fetch outpost configuration, retrying in 3 seconds","level":"error","logger":"authentik.outpost.ak-api-controller","timestamp":"2022-07-19T02:53:37Z"}

Version and Deployment (please complete the following information):

• authentik version: beryju/authentik:latest (2022.7.2)
• Deployment: docker-compose

Additional context
I am able to access the initial setup and Authentik webpage. I have not done any work within Authentik itself yet. Waiting to see if I can iron out this docker-compose portion prior to leaving it running. I am not super familiar with all the concepts Authentik provides, but wanting to learn and desire a simple SSO solution for multiple of my other dockers.

[adamzvolanek]

I just noticed on the Admin Dashboard that the 'Embedded outpost is not configured properly'.

I did see if this was a case of RTFM however I do not see the 'fresh install' outpost in my own Authentik... install?

Looking into my own Outposts I see:

Based on the Core-Concepts/Terminology diagram, I will require Proxy Outposts to support my own Plex app since, as noted, it does not natively support SSO.

[BeryJu]

Same issue as in #3243, fixed release will be out in a bit, tl;dr restart the worker and the error should stop happening