Before you start please confirm the following.

• Yes, I've searched similar issues on GitHub.
• Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description

Attempting to test a Gitea/Forgejo instance fails.

Expected Behavior

Be able to browse packages.

Actual Behavior

Failure: "Invalid management configuration", whether TLS is on or off.

Steps to Reproduce

1. Install Gitea/Forgejo (most people initially set it up on port 3000).
2. Install Portainer (currently using Business Edition).
3. Add custom repo: gitea.example.com:3000 (externally accessible to world)
4. Optionally add authentication and/or (fails in all combinations)

Portainer logs or screenshots

Nothing in the logs at all. A search for the registries turned up nothing. Useless logs.

Portainer version

2.24.0

Portainer Edition

Business Edition (BE/EE) with Starter license

Platform and Version

N/A

OS and Architecture

N/A

Browser

No response

What command did you use to deploy Portainer?

N/A, Bridged and able to access WAN.

Additional Information

It doesn't matter if I use port 3000 or port 443, TLS or non-TLS, authentication or non-authentication. I've tried adding publicly-available registries using Gitea/Forgejo, none of them work. This is a complete show-stopper.

This might also be why Portainer can never tell whether Forgejo images have any updates or not. (Consider code.forgejo.org/forgejo/forgejo:9-rootless for example.)