Akkoma servers configured with domain port not equal to 443 don't federate? [bug] #464

New Issue

Open

opened 2023-02-12 18:04:21 +00:00 by aoanla · 0 comments

aoanla commented

2023-02-12 18:04:21 +00:00

Your setup

From source

Extra details

Alpine

Version

2023.2

PostgreSQL version

What were you trying to do?

Following the documentation example here: https://docs.akkoma.dev/stable/configuration/cheatsheet/#http-client for HTTP Server, Web Endpoint
(which shows an example config where the domain port is not 443 as its only example) and the documentation here: https://docs.akkoma.dev/develop/configuration/how_to_serve_another_domain_for_webfinger/ for configuring webfinger/host-meta for host != domain, I configured an akkoma instance with

domain: subdomain.example.net port 8443
host: example.net
(obviously not actually example.net)

and appropriately configured the host-meta for example.net to include the port.

What did you expect to happen?

Working, federating Akkoma server accessible via https on port 8443.

What actually happened?

The resulting akkoma server is accessible via its front-end at subdomain.example.net:8443 , and the webfinger response is appropriately forwarded, if example.net is contacted on port 80 (http) or 8443 (https).

However: the webfinger response is not correct (the aliases field and others do not include a port in the URL, for example, so a service will try to contact subdomain.example.net on port 443, rather than 8443), and generally a number of field do not include the port which should.
(Of course, also attempts to access example.net:443/.well-known/host-meta will also fail, but that can't be fixed here, and the http version being visible should allow services to actually find the right place)

The instance seems to be unable to federate - and I assume that this is due to the above deficiencies.

This also seems to break things like Fedi and Husky trying to register with the akkoma server as well.

As I am unable to configure a service using port 443 for unresolvable technical reasons, this renders me unable to run an akkoma server.

(a possibly related issue for Pleroma is https://git.pleroma.social/pleroma/pleroma/-/issues/1881 )

This could be fixed by also amending the docs examples to not imply that this all just works, if it isn't supposed to!

Logs

No response

Severity

I cannot use the software

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup From source ### Extra details Alpine ### Version 2023.2 ### PostgreSQL version 14 ### What were you trying to do? Following the documentation example here: https://docs.akkoma.dev/stable/configuration/cheatsheet/#http-client for HTTP Server, Web Endpoint (which shows an example config where the domain port is not 443 as its only example) and the documentation here: https://docs.akkoma.dev/develop/configuration/how_to_serve_another_domain_for_webfinger/ for configuring webfinger/host-meta for host != domain, I configured an akkoma instance with domain: subdomain.example.net port 8443 host: example.net (obviously not actually example.net) and appropriately configured the host-meta for example.net to include the port. ### What did you expect to happen? Working, federating Akkoma server accessible via https on port 8443. ### What actually happened? The resulting akkoma server *is* accessible via its front-end at subdomain.example.net:8443 , and the webfinger response is appropriately forwarded, if example.net is contacted on port 80 (http) or 8443 (https). However: the webfinger response is not correct (the aliases field and others do not include a port in the URL, for example, so a service will try to contact subdomain.example.net on port 443, rather than 8443), and generally a number of field do not include the port which should. (Of course, also attempts to access example.net:443/.well-known/host-meta will also fail, but that can't be fixed here, and the http version being visible should allow services to actually find the right place) The instance seems to be unable to federate - and I *assume* that this is due to the above deficiencies. This also seems to break things like Fedi and Husky trying to register with the akkoma server as well. As I am unable to configure a service using port 443 for unresolvable technical reasons, this renders me unable to run an akkoma server. (a possibly related issue for Pleroma is https://git.pleroma.social/pleroma/pleroma/-/issues/1881 ) This could be fixed by also amending the docs examples to not imply that this all just works, if it isn't supposed to! ### Logs _No response_ ### Severity I cannot use the software ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

👀 1