You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you all for your great work! I recently installed umami on my server and I found it very intuitive and simple to use.
As the title says, could it be possible to show which domains are requested per website?
The use case for this feature is this: all my services are behind a single reverse proxy, and all my domains point to the same ip address, but not all domains expose a web page, some domains are only needed to provide a name instead of using the ip. For example, I have the domain vpn.example.com which is only used for vpn connection but, since all domains points to the same ip and since all my services are exposed by a single reverse proxy, it is still possibile to reach out https://vpn.example.com, so I have setup a custom 503 page for all the incoming requests for domain names which aren't bound to any website and this custom page contains the tracking code for my umami instance.
By exposing also the domain I could easily spot which are the domains requested which cause a 503 response, which now is impossible.
The text was updated successfully, but these errors were encountered:
Describe the feature or enhancement
First of all, thank you all for your great work! I recently installed umami on my server and I found it very intuitive and simple to use.
As the title says, could it be possible to show which domains are requested per website?
The use case for this feature is this: all my services are behind a single reverse proxy, and all my domains point to the same ip address, but not all domains expose a web page, some domains are only needed to provide a name instead of using the ip. For example, I have the domain
vpn.example.com
which is only used for vpn connection but, since all domains points to the same ip and since all my services are exposed by a single reverse proxy, it is still possibile to reach outhttps://vpn.example.com
, so I have setup a custom 503 page for all the incoming requests for domain names which aren't bound to any website and this custom page contains the tracking code for my umami instance.By exposing also the domain I could easily spot which are the domains requested which cause a 503 response, which now is impossible.
The text was updated successfully, but these errors were encountered: