log anonymization bugs

[justinrh 274]

What is "host1"?  (my HDHR does not respond to that URL)
Shouldn't the HDHR device IP address be obfuscated?

2026-03-31 00:00:03.011 Info LiveTV: Discovered tuner device HD Homerun at http://192.168.50.163
2026-03-31 00:00:03.012 Info HttpClient: GET http://192.168.50.163/discover.json
2026-03-31 00:00:03.016 Info HttpClient: Http response 200 from http://192.168.50.163/discover.json after 4ms
2026-03-31 00:00:03.068 Info HttpClient: GET https://api.hdhomerun.com/api/lineup?DeviceAuth=ioMZ5KSi95xUFM-lc72nGfYM
2026-03-31 00:00:03.241 Info HttpClient: Http response 200 from https://api.hdhomerun.com/api/lineup?DeviceAuth=ioMZ5KSi95xUFM-lc72nGfYM after 173ms
2026-03-31 00:00:03.250 Info HttpClient: GET https://host1/v1.1/lineups/USA-OTA35810/channels?enhancedCallSign=true
2026-03-31 00:00:03.250 Info HttpClient: Http response served from cache from https://host1/v1.1/lineups/USA-OTA35810/channels?enhancedCallSign=true

 

Why is the server IP address obfuscated on one line but not the vast majority of places?

2026-03-31 10:02:35.836 Info SessionsService-0HNKCUOBGN6D7:00000004: http/1.1 POST http://192.168.50.162:8096/emby/Sessions/Capabilities/Full. Source Ip: host2, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003)

2026-03-31 10:34:47.962 Info SessionsService-0HNKCUOBGN6E3:00000001: http/1.1 POST http://host3:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=6bf416da-37cb-41fe-94e7-04c1bc472974&X-Emby-Client-Version=4.9.3.0&X-Emby-Token=x_secret4_x&X-Emby-Language=en-us&reqformat=json. Source Ip: host4, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0

 

Seems very inconsistent.

 

 

[GrimReaper 4955]

hosts are generally masked remote addresses - you can also see them unmasked if you look at the log directly in the Web UI or toggle-off log anonymization before downloading it so you can easily compare raw vs. sanitized log and find out all the addresses. 

Edited March 31 by GrimReaper

[justinrh 274]

Indeed 

I see the difference now, if a device/endpoint has a host name, it is obfuscated (e.g., "host2") but if the device/endpoint has an IP address then it is ignored and not obfuscated.  (at least in most cases)

What's the point of that?

Edited March 31 by justinrh

[GrimReaper 4955]

5 minutes ago, justinrh said:

but if the device/endpoint has an IP address then it is ignored and not obfuscated

They actually should be, as long as those are remote IPs - but by no means it means it works 100%, you might've just found a bug - but you need to provide specific example. 

[justinrh 274]

Examples above, but I have only local IPs in my log.  Still inconsistent behavior.

[Luke 42342]

local network ip addresses are generally not obfuscated.

[GrimReaper 4955]

11 hours ago, justinrh said:

Examples above, but I have only local IPs in my log

 

11 hours ago, GrimReaper said:

hosts are generally masked remote addresses

 

11 hours ago, GrimReaper said:

They actually should be, as long as those are remote IPs

There's no point in masking local addresses (except making troubleshooting harder by an order of magnitude). 

Edited April 1 by GrimReaper

[justinrh 274]

Yeah, I got the local address thing ... but local device IP addresses are obfuscated:

Source Ip: host4,

Why are local host names obfuscated?

[Luke 42342]

There might be some places that aren't' checking if it's in the local network.