Tracking traefik support in upstream #8

Open
opened 2022-01-19 14:22:58 +00:00 by decentral1se · 2 comments
Owner

We can't go mainline proper until this one is solved:

https://github.com/snikket-im/snikket-server/issues/88

We can't go mainline proper until this one is solved: > https://github.com/snikket-im/snikket-server/issues/88
Owner

I was looking into snikket-web-proxy, I think it's possible to fork it to disable HTTPS entirely and let traefik/caddy manage the TLS termination.

I was looking into snikket-web-proxy, I think it's possible to fork it to disable HTTPS entirely and let traefik/caddy manage the TLS termination.
Owner

i was just thinking that encrypted s2s seems to require a valid certificate on the remote server, not on the server initiating the connection, so i think it'd be possible to completely disable certificates on snikket's side and let traefik manage tls termination from incoming connections?

i'll have to run some tests only running prosody so i don't have to mess with anything else...

i was just thinking that encrypted s2s seems to require a valid certificate on the remote server, not on the server initiating the connection, so i think it'd be possible to completely disable certificates on snikket's side and let traefik manage tls termination from incoming connections? i'll have to run some tests only running prosody so i don't have to mess with anything else...
Sign in to join this conversation.
No description provided.