codesandbox-client
codesandbox-client copied to clipboard
codesandbox
VMs not starting, cannot create new ones.
🐛 bug report
Preflight Checklist
- [X] I have read the Contributing Guidelines for this project.
- [X] I agree to follow the Code of Conduct that this project adheres to.
- [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
Description of the problem
My VM is restarting and failing. I haven't asked for it. It just started automatically.
"Resuming Micro VM. Still booting" "MicroVM snapshots are created to boot up in less than 2 seconds"
But nothing happens and secondly, I am getting an error after some time:
Unable to start the microVM Your changes were saved, but we could not start the microVM running your project. Please try restarting the microVM by clicking the "Restart microVM" button." All Systems Operational We didn't encounter any issues in our system, which indicates that the issue might be related to your account.
If the issue persists, please contact our support team at [email protected] for further assistance, making sure to copy the error details below, or check the status page.
Error: (502) - URL: https://codesandbox.io/api/beta/sandboxes/branches/<<branch_code>>/instance
- DATA:
Error: Server Error
The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds.
- ERROR: SyntaxError: Unexpected token '<', "
How has this issue affected you? What are you trying to accomplish?
I cannot start any environment. I cannot create a new environment.
Hello! Do you still have this problem? We had a disruption around the time of your message due to a sudden spike in traffic. It should've been fixed relatively quickly after, and we're currently working on adding more nodes to the pool to handle a spike like this in the future.
Hello! Do you still have this problem? We had a disruption around the time of your message due to a sudden spike in traffic. It should've been fixed relatively quickly after, and we're currently working on adding more nodes to the pool to handle a spike like this in the future.
I'm probably late but yeah this is happening today too
it seems Pitcher Manager US-1 is down but im not very sure
You're right, we had a DoS from within the network (from a VM) around that time. It's resolved now and we've added some measures to ensure that this doesn't happen again. Apologies for the inconvenience!