Closed 39ff closed 1 year ago
Ah, this might be as a result of the last few PR's by @random-robbie to try and fix some pathing issues with a reverse proxy. I'll revert in a bit.
Sorry about that!
Certain parts work with the ./
on the main page but when its in /something/ it's messed up sorry!
I'll fork and test fully when I can to ensure it works both ways.
I've reverted the PR's for now @39ff , give the Github Actions some time to rebuild the container. @random-robbie no worries! :) Would you mind elaborating a bit on what you are experiencing maybe that prompted those changes?
So while running nginx as the reverse proxy I was getting 404 for anything under assets as I have gowitness under a subfolder.
Myserver.com/gowitness/
But when loading the webserver I was getting 404 cause all the assets and links were going to
myserver.com/assets
instead of myserver.com/gowitness/assets
Using a nginx configuration block such as the following with the new --base-path
flag set to /gowitness
should now have URL's correctly generated since https://github.com/sensepost/gowitness/commit/e904933ab1d877beca7f88b14b513144c5c23ca0.
server {
listen 80;
server_name localhost;
...
location /gowitness/ {
proxy_pass http://gowitness:7171/;
}
}
Wrote a slightly more verbose example here: https://github.com/sensepost/gowitness/wiki/Report-Server#on-reverse-proxies