Caddyfile not forwarding IP

[DieSchoeneWolke]

Hello I run caddy2 as a reverse proxy but my IP is not getting forwarded and I cannot see any channels from outside in Element.
Anybody knows what I have done wrong? Thank you for your replies!

Caddyfile according to the example

mydomain.com {
	header /.well-known/matrix/* Content-Type application/json
	header /.well-known/matrix/* Access-Control-Allow-Origin *
	respond /.well-known/matrix/server `{"m.server": "matrix.mydomain.com:443"}`
	respond /.well-known/matrix/client `{"m.homeserver": {"base_url": "https://matrix.mydomain.com"}}`
}

# The actual domain name whereby your Matrix server is accessed.
matrix.mydomain.com {
	# Set localhost:8008 to the address of your Dendrite server, if different
	reverse_proxy /_matrix/* localhost:64614
}

elementwebui.mydomain.com {
    reverse_proxy localhost:64616
}

docker-compose.yml

  monolith:
    container_name: Dendrite-Monolith
    image: matrixdotorg/dendrite-monolith:latest
    ports:
      - "64614:8008"
      - "64615:8448"

dendrite.yaml

# Configuration for the Sync API.
sync_api:
  # This option controls which HTTP header to inspect to find the real remote IP
  # address of the client. This is likely required if Dendrite is running behind
  # a reverse proxy server.
  real_ip_header: X-Real-IP

[S7evinK]

Looks like you need X-Forwarded-For instead of X-Real-IP in your dendrite.yaml when using Caddy.

[DieSchoeneWolke]

Yes that did it!
Thank you very much.

Edit: Just realised I still cannot do something from outside.
Do I need to do something with Port 8448 in my case 64615?

xxxxxxxx.com is not accessible at this time.

Try again later, or ask a room or space admin to check if you have access.

M_UNKNOWN was returned while trying to access the room or space. If you think you're seeing this message in error, please [submit a bug report](https://github.com/vector-im/element-web/issues/new/choose).

dendrite container logs

level=info msg="Sent event to roomserver" 

event_id="$3cP3D8Fbxxxxxxxxx" req.id=w7xxxxxxxxx req.method=PUT req.path="/_matrix/client/r0/rooms/!HT8iev1IGAE4TIx9:xxxxxxxxxx.com/state/m.space.child/!OzC5WFYvxjbdC8VJ:matrix.xxxxxxxxx.com" 

room_id="!HT8iev1IGAE4TIx9:matrix.xxxxxxxxxx.com" room_version=10 user_id="@jaxxxxxxxxxx:matrix.xxxxxxxxxxxx.com"

[S7evinK]

Port 8448 should not be needed, as you're delegating that to port 443 (matrix.mydomain.com:443). Did you check that https://federationtester.matrix.org/ is green?

[DieSchoeneWolke]

Thanks for the link!
I have everything green besides MatchingServerName.

matrix.mydomain.com:443

Got 1 connection report.

Homeserver version: Dendrite 0.13.1+49d75d3
It is possible that the MatchingServerName error below is caused by you entering the wrong URL in the federation tester, not because there is an actual issue with your federation. You should enter the server name into the Federation Tester, not the location where your server is. The server name is the public facing name of your server that appears at the end of usernames and room aliases.

If I test my domain without the port I get this:
matrix.mydomain.com

Connection Errors
Get "https://89.xxx.xxx.xxx:8448/_matrix/key/v2/server": dial tcp 89.xxx.xxx.xxx:8448: connect: no route to host