-
-
Notifications
You must be signed in to change notification settings - Fork 17
Self-hosted version provides http src as 127.0.0.1:3000
#109
Comments
127.0.0.0:3000
127.0.0.1:3000
@BackedUpBooty thank you for the bug report. Just to clarify that you are using a load balancer to terminate SSL and then proxy that on? Are you doing it all via docker-compose locally? We'll investigate using the steps you have provided and update this thread with configuration steps or push a fix. |
Hey thanks for the quick reply. I only have the one server which both the proxy and scale8 services are running on. Proxy is a pre-existing SWAG docker container (essentially nginx + LE certificate host) which is pointing at the Yes everything is being run via docker-compose locally. |
Awesome, thank you for the extra info. We'll replicate your setup and get this sorted for you. |
@BackedUpBooty - I have updated docker-compose.yml to reflect the router setting requirement.
If you change
Then in the edge config, change
Please let me know if you have any other issues. |
Hey thanks very much, that did it! I'll close the ticket now, thanks for such a speedy fix. Looking forward to playing around with this now. |
Describe the bug
I created a reverse proxy to access the gui via my sub.domain.com. The documentation I found doesn't really give info for this, however the tags being generated for applications still show
src=http://127.0.0.1:3000/edge/xxxxxxxxxxxxxxxxxxx
. I have tried changing thePROXY_LOCATION
and theS8_EDGE_SERVER
to my sub.domain.com but the generated tags still show the src listed above.How do we change the tag so that it will work via reverse proxy? Doing it manually doesn't seem to work
To Reproduce
Steps to reproduce the behavior:
Expected behavior
<script src="https://sub.domain.com/[platformID]/tm.js" async></script>Generated tag would follow a template which allowed for reverse proxies, something like:
Additional context
Hardware
The text was updated successfully, but these errors were encountered: