Can Akkoma be configured to use HTTPS?

Support
1

I want to install Akkoma on a server behind my reverse proxy. I prefer to use TLS on the internal network, so I’m wondering if Akkoma can be configured to support HTTPS directly instead of requiring the local reverse proxy?

2

hello, welcome :wave:

While i haven’t tested this, Akkoma uses the Phoenix framework, and aparently it’s possible there, so it may also work for Akkoma, but you’ll have to try and see how it goes. The Phoenix docs for this are Using SSL — Phoenix v1.7.18

The config line they show is config :hello, HelloWeb.Endpoint,, for Akkoma it will be config :pleroma, Pleroma.Web.Endpoint,. The config file for OTP installations is /etc/akkoma/config.exs. For from source installations /opt/akkoma/config/prod.secret.exs.

1 Like
3

Thanks for the link. I read through the Akkoma docs and now I see that in the Cheat Sheet.

In the Akkoma Cheat Sheet for HTTP server, it states the following example:

config :pleroma, Pleroma.Web.Endpoint,
  url: [host: "example.com", port: 2020, scheme: "https"],
  http: [
    port: 8080,
    ip: {127, 0, 0, 1}
  ]

This is somewhat aside from the post topic, but why does this example configure the url for port 2020? I was assuming port 443? If I understand this correctly, the example communicates to other servers to find this instance at https://example.com:2020, which seems odd to me, and I see it is the same example in the Pleroma docs.

4

Yeah, my config indeed has 443, that’s also what it should be by default.

From what I see in the git history from those docs, this example was added to these docs from the very beginning and possibly added by some automated tool. I don’t see why port 2020 was chosen. Maybe it made sense to whomever made this example to use a non-standard port, but idk why.