Unable to Proxy Cockpit on Fedora Server 40 OS

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes https://github.com/NginxProxyManager/nginx-proxy-manager/issues/668 did not resolve my issue

Describe the bug

I either get login connection failed error or SSL connection error.

Nginx Proxy Manager Version

v2.12.0

To Reproduce
Steps to reproduce the behavior:

• Followed @jc21's setup (https://github.com/NginxProxyManager/nginx-proxy-manager/issues/668#issuecomment-712623438)
  • Error: 502 Bad Gateway. Turning on httpd connection setsebool -P httpd_can_network_connect on does not resolve the bad gateway error.
• Followed this guide: https://garrett.github.io/cockpit-project.github.io/external/wiki/Proxying-Cockpit-over-NGINX
  • I get SSL connection failed error

Expected behavior

Nginx proxy manager resolves the domain name and directs to an encrypted cockpit login page.

Screenshots

@jc21's setup:

Additional Setup from the guide:

/etc/cockpit/cockpit.conf
[WebService]
Origins = https://cockpit.mydomain.com wss://cockpit.mydomain.com
ProtocolHeader = X-Forwarded-Proto

Operating System

Fedora Server 40

Additional context

podman-compose version 1.2.0
podman version 5.2.3

Start by reviewing the reproduction steps, the linked issue 668 guidance, and the cited Cockpit proxy guide. Reproduce the 502 and SSL connection errors on Fedora Server 40 with podman-compose 1.2.0 and Podman 5.2.3, then inspect the shown /etc/cockpit/cockpit.conf settings. Done means identifying a reproducible cause and documenting a working encrypted Cockpit proxy configuration.