Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discontinue ams-ps and avoid unnecessary reverse proxying #892

Open
hellais opened this issue Oct 31, 2024 · 0 comments
Open

Discontinue ams-ps and avoid unnecessary reverse proxying #892

hellais opened this issue Oct 31, 2024 · 0 comments
Assignees
Labels
ooni/devops Issues related to https://github.com/ooni/sysadmin priority/medium

Comments

@hellais
Copy link
Member

hellais commented Oct 31, 2024

While updating the tor targets we ran into a situation where the configuration of backend-fsn was reverse proxying requests over to orchestrate.ooni.io (ie. ams-ps).

This lead to the surprise that updates to the target file inside of backend-fsn was not having any effect. We should make sure these targets are in fact retrieved from the backend-fsn host and not orchestrate.

This is the relevant configuration section: https://github.com/ooni/sysadmin/blob/master/ansible/roles/ooni-backend/templates/nginx-api-fsn.conf#L114.

According to #746, we only really need orchestrate still for register and login, but we could probably port those over so we can entirely discontinue this host.

At bare minimum we should adjust the nginx config such that we are only reverse proxying those two paths and not the whole /api/v1/test-list/* prefix.

@hellais hellais added priority/medium ooni/devops Issues related to https://github.com/ooni/sysadmin labels Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ooni/devops Issues related to https://github.com/ooni/sysadmin priority/medium
Projects
None yet
Development

No branches or pull requests

2 participants