Got 404 or 502 the first time visiting a container reverse-proxied by SWAG but will be fine after being refreshed

Has anyone encountered this problem? The first time accessing a container reverse-proxied by SWAG, sometimes it reports 404, sometimes 502, but will be fine if I refresh the page.

you haven’t provided enough information for us to reply other than to say that a 502 means swag can’t reach the proxied application.

Thank you for your help. Tried nginx-proxy-manager and caddy and they all work well. I moved to them for now.