Christian Scheb

Did you write your own log handler or are you using the standard one that comes with the library? If you're using the battery standard one I'd suggest you try...

I did understand this, but I also don't have an idea where this is coming from. My guess is that something in the way the standard StreamHandler workes is incompatible...

Have a look at these classes: https://github.com/scheb/tombstone/tree/1.x/src/logger/Handler

Sorry, I don't understand what you mean. I wouldn't want to touch the StreamHandler so much as this would potentially break other people's implementations. My recommendation is to implement a...

Seem to be rate-limiting or even blocking scripted user-agents (such as curl or the Guzzle client) more restrictively now. Not sure why the tests on Github are working fine, maybe...

Yes, I've also recognized that. It seems they're also using TLS fingerprinting now, to distingish real browsers from API clients. The best way around this issue that I've found so...

@netcarlos Seems unrelated, I haven't come across this issue yet. If I have to guess, you might get geo-blocked.

This is an `AccessDeniedException` that is raised by the bundle whenever someone tries to access a protected route, while they're still in the process of entering the 2fa code. See:...

You could implement and register your own version of a `CheckTwoFactorCodeListener`, which iterates _all_ the available 2fa-providers and checks the code against them. The bundle's implementation can be taken as...

Please check if your server time and time on the 2fa device is configured correctly and in sync. The Google Authenticator code is time based and when time on the...