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

Document how to use reverse proxy with subpath URLs #213

Closed
1 task done
nakal opened this issue Jun 8, 2024 · 2 comments
Closed
1 task done

Document how to use reverse proxy with subpath URLs #213

nakal opened this issue Jun 8, 2024 · 2 comments
Labels
stale This issue or pull request has been marked as stale due to prolonged inactivity Status: Created The issue has been created but not yet assigned or addressed. Type: Bug Something isn't working

Comments

@nakal
Copy link

nakal commented Jun 8, 2024

Avoid duplicated bug reports

  • I've found a bug and checked that there are no open or closed bug report related to this.

Description

I usually don't want to make a new DNS entry and certificates and just install my containers on my reverse proxy using URLs like https://my.homeserver.domain/webapplicationname.

I could not find how to do this. It's also very difficult to guess how to set up the reverse proxy entries. At no point there is a hint that the entries for Nginx should like similar to this:

        location / {
                proxy_pass http://internal-host:3000/;
                proxy_set_header Host      $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_http_version 1.1;
                auth_basic           "off";
        }

        location /api/ {
                proxy_pass http://internal-host:8080/api/;
                proxy_set_header Host      $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_http_version 1.1;
                auth_basic           "off";
        }

For subpath /plant-it it should probably look like:

        location /plant-it/ {
                proxy_pass http://internal-host:3000/;
                proxy_set_header Host      $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_http_version 1.1;
                auth_basic           "off";
        }

        location /plant-it/api/ {
                proxy_pass http://internal-host:8080/api/;
                proxy_set_header Host      $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_http_version 1.1;
                auth_basic           "off";
        }

But this does not work, because I cannot find out how to set up the server path. The "server URL" does not affect the subpath btw. The home webpage still delivers <base href="/">.

Local environment

  1. backend 0.7.1
  2. frontend 0.6.1
  3. installation via docker-compose
@nakal nakal added Status: Created The issue has been created but not yet assigned or addressed. Type: Bug Something isn't working labels Jun 8, 2024
Copy link

This issue has been marked as stale due to no activity in the last 90 days. It will be closed in 14 days if no further activity occurs.

@github-actions github-actions bot added the stale This issue or pull request has been marked as stale due to prolonged inactivity label Oct 23, 2024
Copy link

github-actions bot commented Nov 7, 2024

Closing this issue as it has been stale for 14 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale This issue or pull request has been marked as stale due to prolonged inactivity Status: Created The issue has been created but not yet assigned or addressed. Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant