All internal ip addresses show up as loopback #1812

New issue

Open

opened 2026-05-26 04:41:31 +00:00 by Arch515 · 4 comments

Arch515 commented

2026-05-26 04:41:31 +00:00

All of the ip addresses that show up on the server, such as account created messages in the admin room, and the devices list on users' clients, show up as 127.0.0.1.

All of the ip addresses that show up on the server, such as account created messages in the admin room, and the devices list on users' clients, show up as `127.0.0.1`.

stratself commented

2026-05-26 04:47:10 +00:00

Contributor

Does your reverse proxy set the X-Forwarded-For header to pass it to Continuwuity?
Are you using Docker? Can be a Docker issue.

- Does your reverse proxy set the `X-Forwarded-For` header to pass it to Continuwuity? - Are you using Docker? Can be a Docker issue.

Aranjedeath commented

2026-05-26 04:48:57 +00:00

Owner

If I remember correctly, this is caused by axum removing insecure_client_ip feature (and then we upgraded to the version which lacks this)

nex added the

Bug

Matrix/Administration

Status

Confirmed

labels

2026-05-26 09:20:25 +00:00

nex commented

2026-05-26 09:20:54 +00:00

Owner

Have had this on continuwuity.rocks but never got time to investigate, iirc @Jade knew something about the fix? some axum configuration or something?

Jade commented

2026-05-31 19:03:47 +00:00

Owner

Yeah, upgrading the axum-client-ip crate removed the default insecure behavior and requires explicit configuration of a ClientIpSource as a layer. This should be really easy to add to the config.

Yeah, upgrading the axum-client-ip crate removed the default insecure behavior and requires explicit configuration of a [ClientIpSource](https://docs.rs/axum-client-ip/latest/axum_client_ip/enum.ClientIpSource.html) [as a layer](https://github.com/imbolc/axum-client-ip/blob/main/examples/configurable.rs). This should be really easy to add to the config.

Jade added the

Good first issue

Difficulty

Easy

labels

2026-05-31 19:03:58 +00:00