https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
p
@User can you share in more detail what are you trying to accomplish? and why is there a need for proxy pass
n
To access the sinnozui over a dns..
p
@User do you have more ideas on this?
p
@User are you trying to set up Apache2 configuration file to expose SIgNoz UI?
n
Yeah
p
You could use something like this: /etc/apache2/sites-available/000-default.conf
Copy code
<VirtualHost *:80>
    ProxyPreserveHost On

    ProxyPass / http://<localhost-or-signoz-frontend-ip>:3301/
    ProxyPassReverse / http://<localhost-or-signoz-frontend-ip>:3301/
</VirtualHost>
n
Instead of / as context, Yeah I have made the enries with /signoz Ui is loading with blackpage..
p
oh, I see. Unfortunately, we currently don't support custom 
baseURL
.
You would have to expose to a subdomain or a different port.
n
To 3301 port
p
could you tell us how you have deployed SigNoz? Is it using Docker Standalone?
n
Yeah
Installed using script ( it created the docker images)
p
okay, got it.
SigNoz UI (frontend) already runs on top of Nginx server. Having Apache2 would be redundant.
Frontend should already be running in the instance on 
3301
port
You would have to set the firewall rules to expose that 
3301
port so that it would be accessible from your company VPN or publicly (not recommended).
n
Yeah url is up in broswer but page is loading with full black page..
p
could you try exposing to subdomain or a different port externally? Let me know how it goes.
n
In developer tab, could see the below responsecodes While loading the signoz in ui Signoz -304 Main-404 Css-200 Runtime-404
67 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by