Unable to register module in the portal

pberkel · March 16, 2026, 10:44pm

Hi,

I am having trouble registering a module GitHub - pberkel/caddy-tls-permission-policy: Implements a Caddy module for controlling on-demand TLS certificate issuance. · GitHub through the portal and am receiving this fairly cryptic error message:

Sorry, something went wrong:

unable to scan modules in package GitHub - pberkel/caddy-tls-permission-policy: Implements a Caddy module for controlling on-demand TLS certificate issuance. · GitHub

Please include this error ID if reporting:
f8d20a4e-4c1e-4594-a174-a12689e8894d

I believe I supplied the correct package import path “GitHub - pberkel/caddy-tls-permission-policy: Implements a Caddy module for controlling on-demand TLS certificate issuance. · GitHub”. Thanks in advance for advice on rectifying this issue.

regards,

Pieter

matt · March 16, 2026, 10:54pm

What was your exact import path? (Discourse replaced whatever you typed with a link preview.) If it’s a URL, remember that Go modules don’t have schemes (they are not URLs). So no https:// prefix… try that.

pberkel · March 16, 2026, 11:08pm

Thanks for the reply – Not sure why my original post got mangled but I did remove the scheme prefix from the github URL when submitting the module that produced the above errror: github.com/pberkel/caddy-tls-permission-policy

matt · March 16, 2026, 11:58pm

Thanks, yeah that looks correct.

Our static analyzer is very simple, so this constructor will not work:

github.com/pberkel/caddy-tls-permission-policy

tls_permission_policy.go

main


      
          		PermitLocal:       false, // Do not allow certificates to be issued to local / loopback addresses.
          	}
          	return &p
          }
          
          // CaddyModule returns the Caddy module information.
          func (*PermissionByPolicy) CaddyModule() caddy.ModuleInfo {
          	return caddy.ModuleInfo{
          		ID: "tls.permission.policy",
          		New: func() caddy.Module {
          			return New()
          		},
          	}
          }
          
          // UnmarshalCaddyfile implements caddyfile.Unmarshaler.
          func (p *PermissionByPolicy) UnmarshalCaddyfile(d *caddyfile.Dispenser) error {
          
          	for d.Next() {
          
          		for nesting := d.Nesting(); d.NextBlock(nesting); {

Instead, a composite literal (or new()) is required.

Note that that value isn’t used for anything other than calling CaddyModule().

The constructor here doesn’t make sense either: caddy-tls-permission-policy/tls_permission_policy.go at main · pberkel/caddy-tls-permission-policy · GitHub

It fills in all zero values…

Just out of curiosity did you use AI at all?

pberkel · March 17, 2026, 4:52am

Hi Matt,

This New() constructor is a pattern I’ve used in other Caddy modules I’ve developed previously to specify default values before Caddyfile options have been parsed and populated into the module struct, for example:

github.com/pberkel/caddy-storage-redis

caddyfile.go

main


      
          				Use:   "repair --config <path>",
          				Short: "Repair the Redis Storage directory index tree",
          				RunE:  caddycmd.WrapCommandFuncForCobra(cmdRedisStorageRepair),
          			}
          			rebuildCmd.Flags().StringP("config", "c", "", "Caddy configuration file (optional)")
          			cmd.AddCommand(rebuildCmd)
          		},
          	})
          }
          
          func (RedisStorage) CaddyModule() caddy.ModuleInfo {
          	return caddy.ModuleInfo{
          		ID: "caddy.storage.redis",
          		New: func() caddy.Module {
          			return New()
          		},
          	}
          }
          
          func (rs *RedisStorage) CertMagicStorage() (certmagic.Storage, error) {
          	return rs, nil

github.com/pberkel/caddy-storage-redis

storage.go

main


      
          
          type StorageData struct {
          	Value       []byte    `json:"value"`
          	Modified    time.Time `json:"modified"`
          	Size        int64     `json:"size"`
          	Compression int       `json:"compression"`
          	Encryption  int       `json:"encryption"`
          }
          
          // create a new RedisStorage struct with default values
          func New() *RedisStorage {
          
          	rs := RedisStorage{
          		ClientType:  defaultClientType,
          		Host:        []string{defaultHost},
          		Port:        []string{defaultPort},
          		DB:          defaultDb,
          		KeyPrefix:   defaultKeyPrefix,
          		Compression: defaultCompression,
          		TlsEnabled:  defaultTLS,
          		TlsInsecure: defaultTLSInsecure,

It’s useful for initialising default configuration values for the module – admittedly the current version of this module setting default values to zero / false is superfluous but future options planned may require non-zero default values.

Both github.com/pberkel/caddy-storage-redis and github.com/pberkel/caddy-redir-dns modules implement this New() constructor pattern and had no issues being parsed and accepted into the module repository, is there a specific error that is being triggered by the code in github.com/pberkel/caddy-tls-permission-policy that I need to fix?

thanks,
Pieter

pberkel · March 17, 2026, 5:13am

I have updated the code in CaddyModule() to remove the New() pattern but I’m still getting an error when trying to submit the module to the registry:

github.com/pberkel/caddy-tls-permission-policy

tls_permission_policy.go

main


      
          	lookupNetIP   func(context.Context, string, string) ([]netip.Addr, error) `json:"-"`
          	approvalMu    sync.Mutex                                                  `json:"-"`
          	approvedNames map[string]map[string]struct{}                              `json:"-"`
          }
          
          // CaddyModule returns the Caddy module information.
          func (*PermissionByPolicy) CaddyModule() caddy.ModuleInfo {
          	return caddy.ModuleInfo{
          		ID: "tls.permission.policy",
          		New: func() caddy.Module {
          			return new(PermissionByPolicy)
          		},
          	}
          }
          
          // UnmarshalCaddyfile implements caddyfile.Unmarshaler.
          func (p *PermissionByPolicy) UnmarshalCaddyfile(d *caddyfile.Dispenser) error {
          
          	for d.Next() {
          
          		for nesting := d.Nesting(); d.NextBlock(nesting); {

Sorry, something went wrong:

unable to scan modules in package github.com/pberkel/caddy-tls-permission-policy

Please include this error ID if reporting:
46134c87-26b9-4ecb-b0c4-af33538b5092

matt · March 17, 2026, 1:02pm

It’s the same error, but I noticed it is downloading v1.0.2:

go: downloading GitHub - pberkel/caddy-tls-permission-policy: Implements a Caddy module for controlling on-demand TLS certificate issuance. · GitHub v1.0.2

I only see v1.0.0 tagged.

pberkel · March 17, 2026, 8:55pm

I did create a few point releases to try to debug this issue, but without actually knowing the specific error encountered by the module scanner, it’s very difficult to debug.

Not sure if it will cause more issues, but I’ve removed all releases from the repo (I really don’t want to create a dozen different point releases just to debug this issue)
and tried to submit the module setting version to the latest commit in the main branch “f2f57d7c72e0f2bc7b6025a9827fa6110dcf3a93” but it’s still failing:

Sorry, something went wrong:

**unable to scan modules in package github.com/pberkel/caddy-tls-permission-policy**

Please include this error ID if reporting:
63e8141e-adb2-4072-86f3-77a32e1aa364

Is there any way to determine the specific underlying error so I can fix before tagging a release?

matt · March 17, 2026, 9:45pm

Note that you can’t reuse/repeat tags. Go’s module system won’t allow it, for security reasons. Also, tags != releases; you can make releases without tags, and vice-versa. Go’s module proxy will choose the latest tag by default, so you don’t have to release them if you’re not ready for a release. You also don’t have to use any tags, and Go will just choose the latest commit.

When you go to claim your package, you can specify a version to use. this can be any git ref, like a branch name, commit SHA, or tag.

I would fiddle with both creating a new tag that you haven’t used yet, and inputting a specific version into the “Version” textbox in the “Claim Package” form.

pberkel · March 17, 2026, 10:59pm

Thanks for the insight Matt – I’ve created a new unused tag v1.0.3 and tried to claim my package my specifying that tag in the form but ultimately receive a similar error message:

Sorry, something went wrong:

unable to scan modules in package github.com/pberkel/caddy-tls-permission-policy

Please include this error ID if reporting:
9fba5bd4-1fce-4ca0-a2f2-dd7cb7c01c6c

Is it possibly to get some insight into the errors triggering this so I can rectify on my end?

Thanks!
Pieter

matt · March 18, 2026, 3:56am

Thanks, now it’s downloading v1.0.3, but it still shows the same error:

unexpected argument to RegisterModule(): &ast.UnaryExpr{OpPos:35513337, Op:17, X:(*ast.CompositeLit)(0xc048a60e00)} - expect either composite literal or new()

Ahhhhh, looking closely this is actually a less common thing, I think the complaint is on this line:

	caddy.RegisterModule(&PermissionByPolicy{})

Try removing & or using new() there instead.

Sorry, this was me being in a hurry when I replied.