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

Localproxy source crashed with "basic_multi_buffer too long" when streaming video #160

Open
jmmk opened this issue Aug 29, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@jmmk
Copy link

jmmk commented Aug 29, 2024

I was running the source Localproxy as a container in ECS. I started viewing a websocket video feed and the process crashed with "fatal: basic_multi_buffer too long" in the logs.

The destination localproxy did not crash.

Neither the source nor the destination are using a custom configuration, so they should both be using the defaults. I confirmed with --export-default-settings that they both produce the same default configuration.

Environment

Docker Image public.ecr.aws/aws-iot-securetunneling-localproxy/ubuntu-bin:arm64-latest

The destination is the same, but using the AMD64 image.

@jmmk jmmk added the bug Something isn't working label Aug 29, 2024
@ig15
Copy link
Contributor

ig15 commented Oct 17, 2024

Hey @jmmk . Thanks for reaching out to us. Can you provide the complete logs and the steps to reproduce the websocket video feed behavior as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants