Simon Kern

@jamaalscarlett is absolutely right. However, (at least for webpush notifications) there are cases in which you'll only notice a device is gone, only after getting an exception (e.g. "410 Gone")...

I encounter a similar issue: ``` /tailscale -socket /tmp/tailscale/tailscaled.sock up failed to connect to local tailscaled (which appears to be running as tailscaled, pid 6113). Got error: Failed to connect...

I'm having the same issue. Have you been able to solve this in the meanwhile?

Do you happen to use django-crispyforms? In our case the issue was caused by the combinated use of select2 and crispy forms.

Additionaly, I tried to manually open a path like `/select2/fetch_items/foo/bar/baz/?q=&page=4&page_limit=10`and it shows data, which is really bad in case of PII. Is there a way to restrict access?