Different blocking mode per client?

yes, that is what meant, sorry for my english

Could you please explain why you would like to have that?

because i’m using pixelserv, so if the client has been installed with pixelserv certificates i’d like to use blockingmode custom ip, for clients that do not have this cert, like friends, i’d like to use blockingmode default.
hope you can understand what i’m trying to say

@ameshkov 🔫 AGH 🤣

@ameshkov 🔫 AGH 🤣

so sad, thought it’d be useful feature
thanks though

No. for @ameshkov
sorry if you misunderstood :)

@regae

Thanks for the explanation! This makes sense, indeed.

Hey @regae , pixelserv-tls is pretty great! I haven't noticed any issues on devices that don't allow me to import the trusted root yet, but I agree that it would be ideal to treat these managed devices differently.

Btw, it makes sense to add something like that to pixelserv-tls: a configurable list of clients where it should try serving HTTPS, for all other clients it can simply reset the connection.

Hi, Another vote for this from me.

I need this feature because I run CA for devices in my homelab but only my devices and a few more have the certificate installed. I would like the blocking mode to be different for clients that have the certificate installed. This way, I can show them a site is blocked page or redirect them to alternatives.

Hi, Another vote for this from me.

I need this feature because I run CA for devices in my homelab but only my devices and a few more have the certificate installed. I would like the blocking mode to be different for clients that have the certificate installed. This way, I can show them a site is blocked page or redirect them to alternatives.

This is my exact situation. I had to create multiple AGH instances and setup DHCP (or the AG client) to override DNS on my devices with the CA.