Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show domain name in websites view #2688

Closed
giuseongit opened this issue Apr 17, 2024 · 3 comments
Closed

Show domain name in websites view #2688

giuseongit opened this issue Apr 17, 2024 · 3 comments
Labels

Comments

@giuseongit
Copy link
Contributor

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 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.

@giuseongit
Copy link
Contributor Author

I actually implemented the feature myself, if this feature could be accepted I can work on it to make the PR pass all the validation.

Copy link

This issue is stale because it has been open for 60 days with no activity.

@github-actions github-actions bot added the stale label Jun 18, 2024
Copy link

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant