Reverse proxy support

[deavmi]

Hi, I am currently trying to run this with an NGINX reverse proxy in front of it, but the URL paths are not playing nicely.

Any advice?

[brendan-kellam]

Hey thanks for raising a issue - do you mind pasting your nginx config so I can try to replicate?

I actually haven't run it in front of a reverse proxy so it's a good question :)

[deavmi]

Let me get that for you

…

On 08 November 2024 09:10:02 SAST, Brendan Kellam ***@***.***> wrote: Hey thanks for raising a issue - do you mind pasting your nginx config so I can try to replicate? I actually haven't run it in front of a reverse proxy so it's a good question :) -- Reply to this email directly or view it on GitHub: #61 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

---- Tristan B. Velloza Kildaire Web: https://deavmi.assigned.network BNET IRC: deavmi Email: ***@***.***

[deavmi]

Here we go:

         # sourcebot
                location ^~ /bot/
        {
                proxy_pass http://sourcebot:3000/;
                proxy_http_version 1.1;
                proxy_set_header Connection "upgrade";
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header X-Forwarded-For $remote_addr;
                proxy_set_header X-Forwarded-Proto $scheme;

                # by default nginx times out connections in one minute
                proxy_read_timeout 1d;
        }

[brendan-kellam]

thanks - I'm heading to bed now but I will try this out in the morning. Could you also send over any logs / further describe what the issue is?

[deavmi]

Sure. Will do when at home

…

On 08 November 2024 09:53:15 SAST, Brendan Kellam ***@***.***> wrote: thanks - I'm heading to bed now but I will try this out in the morning. Could you also send over any logs / further describe what the issue is? -- Reply to this email directly or view it on GitHub: #61 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

---- Tristan B. Velloza Kildaire Web: https://deavmi.assigned.network BNET IRC: deavmi Email: ***@***.***

[deavmi]

Hi, so I don't really have much logs but I can show you what it renders like:

[deavmi]

If I open the Network log, in chromiu, it seems all requests are being made at the root / and not* /bot/, that is the problem

[deavmi]

Any updates on this?

[brendan-kellam]

Sorry I haven't gotten a chance to look into this yet - I will take a look today and get back to you

[deavmi]

Thanks man, appreciate it a lot :-)

…

On 14 November 2024 20:09:35 SAST, Brendan Kellam ***@***.***> wrote: Sorry I haven't gotten a chance to look into this yet - I will take a look today and get back to you -- Reply to this email directly or view it on GitHub: #61 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

---- Tristan B. Velloza Kildaire Web: https://deavmi.assigned.network BNET IRC: deavmi Email: ***@***.***

[brendan-kellam]

Heya - I was able to repro the issue. As you mentioned, all CSS, JS, and image requests are 404'ing since they are referencing the root / and not the redirected /bot path:

I looked into it and Next.js has a basePath config variable that I tested and seemed to work. One fix here may be to make that configurable and expose a BASE_PATH env var that gets passed tobasePath. I can look into that tomorrow.

In the meantime, would it be possible to serve it directly at the root /? Or possibly, use a subdomain?

[deavmi]

I like the `BASE_PATH` envvar approach. Currently it won't be possible for me to serve it at the root as I have other stuff on `/`

…

On 15 November 2024 09:55:32 SAST, Brendan Kellam ***@***.***> wrote: Heya - I was able to repro the issue. As you mentioned, all CSS, JS, and image requests are 404'ing since they are referencing the root `/` and not the redirected `/bot` path: <img width="297" alt="image" src="https://github.com/user-attachments/assets/6899ce2c-6858-4021-9cfa-bd6ba2565650"> I looked into it and Next.js has a [basePath](https://nextjs.org/docs/app/api-reference/next-config-js/basePath) config variable that I tested and seemed to work. One fix here may be to make that configurable and expose a `BASE_PATH` env var that gets passed to`basePath`. I can look into that tomorrow. In the meantime, would it be possible to serve it directly at the root `/`? Or possibly, use a subdomain? -- Reply to this email directly or view it on GitHub: #61 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

---- Tristan B. Velloza Kildaire Web: https://deavmi.assigned.network BNET IRC: deavmi Email: ***@***.***

[brendan-kellam]

Hey @deavmi - I just opened a PR with this change. I have validated it locally with my nginx conf file and all seems to work. If you have a sec, would you mind checking out my branch, building a image, and testing with your config?