@cassidyclown@sam@sam@FrailLeaf What I've observed is that pleromer uses hardcoded certificate list from certifi elixir lib, and when changing some TLS-related settings, it could start ignoring the certificate check completely. Not sure how to work around it, HTTP adapter support is fucking abysmal with no signs of improvement (that's why I unpinned my Tor federation thread, btw). Enforcing TLS 1.3, on the other hand, could break federation with instances that don't support it, pretty sure there's at least a bunch of them.
@cassidyclown@FrailLeaf@sam@sam You could try disabling certificate check completely, I don’t use admin-fe, but it goes like this, should work with default Hackney.
@mint@sam@sam@FrailLeaf Explains why everyone except pleromer seemed happy with the certificate. You can enable multiple TLS versions including 1.3 which is what I've done - so hopefully won't break federation with most instances.
@mint@sam@sam@FrailLeaf Thanks tried these hoping media_proxy would fix the broken avi but nothing- get {:tls_alert, {:unknown_ca, 'TLS client: In state wait_cert_cr at ssl_handshake.erl:2111 generated CLIENT ALERT: Fatal - Unknown CA\n'}} in the logs when I @ to preview the avi :niggawhy:
@cassidyclown@sam@sam@FrailLeaf Ok, I think I've figured it out, apologies for delay and false leads; for some reason I thought redirect_on_failure is outside of proxy_opts which resulted in some confusion. ``` config :pleroma, :media_proxy, enabled: true, proxy_opts: [ redirect_on_failure: false, http: [ proxy: "127.0.0.1:8118", ssl_options: [ verify: :verify_none ] ] ] ```
@mint@FrailLeaf@sam@sam whitelisted returns.null and almost lost my mind because the docs recommended putting https://example.com yet nothing happened when I prefixed with https- thankfully worked with the bare returns.null . This isn't really a solution though at least it's a sanity check.