Ok so I ended up grabbing the final proxy.conf file that was available for the letsencrypt docker and replaced the newest Swag one with it. Boom issue solved, Shinobi loads fine via the reverse proxy again. I opened and compared both config files to see what changed. Now I'm no coder but I can understand what most lines are meant to do (I know just enough to be dangerous). After disabling the line "proxy_set_header Upgrade $http_upgrade;" in the Swag proxy.conf file, Shinobi again was working normally though the reverse proxy.
Hoping someone much smarter then me can take a look at both these config files and figure out why I was having an issue and if it would effect others. It did not appear to effect any of my other containers running reverse proxy. For now I'm running the final letsencrpyt proxy.conf to be safe.
If you followed the instructions in the video by spaceinvaderone, and used the config he create, then I believe issue is because the shinobi config file, and the proxy config file both have this line "proxy_set_header Upgrade $http_upgrade;". It can only exist in one of the file. I removed mine from the shinobi config file, and left it in the proxy.conf.
[Support] spaceinvaderone - Shinobi Pro
in Docker Containers
Posted
If you followed the instructions in the video by spaceinvaderone, and used the config he create, then I believe issue is because the shinobi config file, and the proxy config file both have this line "proxy_set_header Upgrade $http_upgrade;". It can only exist in one of the file. I removed mine from the shinobi config file, and left it in the proxy.conf.