Skip to content

Avatar request fails when Plausible runs on a non-standard port (missing port in URL) #5793

@m-mattia-m

Description

@m-mattia-m

Past Issues Searched

  • I have searched open and closed issues to make sure that the bug has not yet been reported

Issue is a Bug Report

  • This is a bug report and not a feature request, nor asking for self-hosted support

Using official Plausible Cloud hosting or self-hosting?

Self-hosting

Describe the bug

When running Plausible on a port other than 443, user avatars fail to load.

For example, my instance runs on:

https://plausible.domain.tld:9443

The request for the avatar is made to:

https://plausible.domain.tld/avatar/<hash>

However, it should include the port number as well:

https://plausible.domain.tld:9443/avatar/<hash>

All other requests (e.g. Plausible logo, site, etc.) correctly include the port and work fine — only the avatar request is missing it.

Steps to reproduce:

  1. Run Plausible on a custom port (e.g. 9443).
  2. Open the web UI and log in.
  3. Observe that the avatar image fails to load.

Relevant code:

Expected behavior

The avatar request URL should include the port when the Plausible instance runs on a non-standard port.

Screenshots

Image

Environment

- OS: MacOS 26.0.1
- Browser: Arc 
- Browser Version: Arc Version 1.115.0 (69267); Chromium Engine Version 141.0.7390.55

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions