Where is the IP?

[Karem-sobhy]

just wanted to know where to find the IPs of the visits because I can't find them.

[acelaya]

The IP address is in the visits table, in the remote_addr column.

[acelaya]

My mistake. I didn't notice you were asking this in the web client repo.

I'm afraid not. Shlink does not expose the IP addresses for security and privacy regulations reasons.

They are only used for geolocation, and then, they are anonymized and stored just in case the location needs to be resolved again.

[eiqnepm]

My mistake. I didn't notice you were asking this in the web client repo.

I'm afraid not. Shlink does not expose the IP addresses for security and privacy regulations reasons.

They are only used for geolocation, and then, they are anonymized and stored just in case the location needs to be resolved again.

Would you be against adding an environment variable for custom hosted shlink-web-client instances to explicitly enable an IP address column in the visits list? I see that shlink has the environment variable ANONYMIZE_REMOTE_ADDR, which if I assume correctly, when set to false stores the visitors IP address in plaintext, however shlink-web-client has no way to display this information.

I'm currently messing around with a few link shortener projects, shlink does seem to come out on top in most regards, however I'd still like to be able to view visit IP addresses from shlink-web-client.

Nevertheless, great project, thanks a bunch for your work and for making it FOSS!

[acelaya]

As explained above, Shlink does not expose the IP addresses at all, for privacy reasons, so it's trickier to change.

What's exactly the use case for this? Can you explain how would knowing the actual IP address help?

[gcarrarom]

It would be interesting to see this for correlating "sessions" between links. I've seen this use-case when I have an user come from one url and I'm not sure if that's the same going to the other. Maybe not the IP address, but could a "session_id" be created?

[acelaya]

@gcarrarom this was discussed some time ago in some issue that I'm trying to find.

As a result, I created this shlinkio/shlink#725, which was never implemented due to other priorities and luck of traction.

If anything was implemented, I would be inclined to go with option 2, and expose a hash identifying the visitor, but without exposing its IP address.