https://signoz.io logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
n
AFAIK this is not supported, cc @Yunus M
r
Yeah, this is not supported. Tried that and it is a blocker for me as well
n
@Prashant Shahi incase you have some idea on this.
p
It is not possible as of today. You can opt for 
signoz.company.domain
u
Hi, i also want to access my self-hosted signoz instance (running on docker swarm) via reverse proxy with prefix: mydomain.com/ops/logs 
location /ops/logs/ {
proxy_set_header X-Script-Name /ops/logs;
proxy_set_header X-Scheme $scheme;
proxy_set_header Host $host;
proxy_redirect off;
proxy_pass <http://frontend:3301>;
}
it partially works, requests are beind passed to nginx service (frontend:3301) however static files are referenced to 
/
so reverse proxy can't serve them
frontend statics are build with webpack, is any way to rebuild frontend with diffrent root url?
the only safe way to access signoz instance is via ssh tunnel and 
haproxy
attached to docker swarm overlay network
i want to use nginx reverse proxy, because mydomain is proteced with client cetificate and i don't want sognoz frontend be available for public access
and ssh tunnel requries open connection to server, and i don't want everyone in company to have access to docker swarm manager
p
@Yunus M/@Palash Gupta would be the right ones to answer that
s
@Yunus M @Palash Gupta any updates about this guys ? I am facing the same issue , anyway to rebuilt the frontend with "signoz" as the root url for the frontend statics ?
y
Hi @Sharif Saleh: haven't gotten the time to try this out. I will keep the thready updated once I have a solution
s
THANK YOU SIR @Yunus M
226 Views
Open in Slack
PreviousNext
Powered by