Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excessive Websocket Connection Requests by did:schema #434

Open
Pratap2018 opened this issue Jul 11, 2024 · 1 comment
Open

Excessive Websocket Connection Requests by did:schema #434

Pratap2018 opened this issue Jul 11, 2024 · 1 comment
Labels
driver-issue Issues with a Universal Resolver driver

Comments

@Pratap2018
Copy link
Member

Issue Summary

The did:schema driver sent approximately 365k websocket connection requests within a 24-hour period.

Image

Incident Details

According to @S3bb1, the did:schema from uni-resolver has been generating these websocket connection requests for the past couple of weeks. Eventually, @S3bb1 blocked the IP address of the uni-resolver node and reached out to @Pratap2018. To address the situation, @Pratap2018 restarted the pod, after which @S3bb1 unblocked the IP address since that pod was using their infrastructure.

did:schema schema registry driver repository

This issue is being created to track this incident.

@Pratap2018 Pratap2018 added the driver-issue Issues with a Universal Resolver driver label Jul 11, 2024
@S3bb1
Copy link
Contributor

S3bb1 commented Jul 11, 2024

After 24h no excessive connections have been made. From my point of view, the restart helped to resolve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
driver-issue Issues with a Universal Resolver driver
Projects
None yet
Development

No branches or pull requests

2 participants