maggie44

> Hi, > > Can you provide us your tunnel id? > > You mention that the traffic you are doing is via WARP ? but it was not clear...

The restarts were me trying to replicate the issue. This initially occurred around 1am UTC and will likely be the first time it restarted. My Nodes began executing updates and...

A bunch worked ok without issue. Then I did manage to replicate it again just before `13:29:12 WET` (`60f0a274-c3d2-4f01-9ae9-fc51bfa70252`): `API is not reachable. Response code: 503` I don't fully understand...

I managed to replicate it first time this time (`60f0a274-c3d2-4f01-9ae9-fc51bfa70252`): ``` Thu 11 Jan 2024 20:24:26 WET API is not reachable. Response code: 503 ``` It had been running all...

I think that PR is helpful, although it may also be worth reevaluating whether the current `base-debian11` containers still make sense as well. If the goal is to have a...

Wow, big PR! Looking forward to the update, thanks. I’m curious why the bump is to go 1.19? We are currently at 1.21. I thought 1.20 would be a minimum....

> 40 MB flate.Reader 40MB? 🤨. Or Kb?

I did have a swing at compiling with tiny go some time back. It didn’t support the various debugging tools in the code. Stripped those out as they are not...

Cross posting here to some relevant content on this issue for others to find: https://github.com/slackhq/nebula/discussions/823#discussioncomment-6998006

Was able to replicate it on an AMI: ``` aws ec2 run-instances --image-id ami-0799401323b99ed4c \ --count 1 \ --instance-type m5.large \ --tag-specifications \ "ResourceType=instance,Tags=[{Key=Name,Value=test-name}]" \ "ResourceType=volume,Tags=[{Key=Name,Value=test-name}]" \ --user-data "file://config.json" --region...