Setup Nginx proxy to avoid IP tracking #38

Closed
opened 2023-10-07 16:38:41 +00:00 by decentral1se · 5 comments
Owner

I have been in touch with comrades from Systemli about IP tracking issues in Synapse:

This is happening, at least, in the user sessions[1] and the user_ips
table, which is not possible to disable right now[2]. There's config
to clear this after some time, but as I understand it, it is put back
in the database afterwards.

It's true that Synapse currently doesn't provide an option to disable IP
logging. But regardless of this, you may put a reverse proxy in front
which doesn't forward the actual IP addresses of users to Synapse.

Such a simple solution! We should setup an Nginx proxy in this recipe as a standard.

It's the only way to avoid IP tracking with Synapse right now.

I have been in touch with comrades from Systemli about IP tracking issues in Synapse: > > This is happening, at least, in the user sessions[1] and the user_ips > > table, which is not possible to disable right now[2]. There's config > > to clear this after some time, but as I understand it, it is put back > > in the database afterwards. > > It's true that Synapse currently doesn't provide an option to disable IP > logging. But regardless of this, you may put a reverse proxy in front > which doesn't forward the actual IP addresses of users to Synapse. Such a simple solution! We should setup an Nginx proxy in this recipe as a standard. It's the only way to avoid IP tracking with Synapse right now.
moritz reopened this issue 2023-10-19 19:30:12 +00:00
Member

If I update to version 5.0.0+v1.93.0 I get a 404 error from nginx.
Logs:
nginx: [emerg] host not found in upstream "matrix_example_com_synapse" in /etc/nginx/nginx.conf:17

If I update to version `5.0.0+v1.93.0` I get a `404` error from nginx. Logs: `nginx: [emerg] host not found in upstream "matrix_example_com_synapse" in /etc/nginx/nginx.conf:17`
Author
Owner

@moritz idk why you're seeing matrix_example_com? Is that something to do with how you configured the DOMAIN=...? Can't see anything immediately jumping out as wrong in the config. Also, you need to undeploy/deploy to get the app -> synapse rename of the services too.

@moritz idk why you're seeing `matrix_example_com`? Is that something to do with how you configured the `DOMAIN=...`? Can't see anything immediately jumping out as wrong in the config. Also, you need to undeploy/deploy to get the `app` -> `synapse` rename of the services too.
Member

@moritz idk why you're seeing matrix_example_com? Is that something to do with how you configured the DOMAIN=...? Can't see anything immediately jumping out as wrong in the config. Also, you need to undeploy/deploy to get the app -> synapse rename of the services too.

I just renamed the real domain to example_com here for the report. I deployed it as new app, without any special configuration, only with SSO config. And I can't get it running.

> @moritz idk why you're seeing `matrix_example_com`? Is that something to do with how you configured the `DOMAIN=...`? Can't see anything immediately jumping out as wrong in the config. Also, you need to undeploy/deploy to get the `app` -> `synapse` rename of the services too. I just renamed the real domain to `example_com` here for the report. I deployed it as new app, without any special configuration, only with SSO config. And I can't get it running.
Owner

@moritz is this still happening for you?

@moritz is this still happening for you?
Member

No everything works fine, can be closed.

No everything works fine, can be closed.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/matrix-synapse#38
No description provided.