Invalid response: 413 Request Entity Too Large

The error "Invalid response: 413 Request Entity Too Large" you're experiencing with your AWS SageMaker Jupyter notebook is not a common issue, and it's not directly related to restarting your computer or using different browsers. This error typically indicates that the request being sent to the server is larger than what the server is configured to handle.

Given that you can open the same notebook locally, the issue is likely specific to your SageMaker environment. Here are some steps you can take to troubleshoot and potentially resolve this issue:

1. Check the size of your notebook: If your notebook has grown very large, perhaps due to output cells or embedded data, try clearing all output cells and saving the notebook before attempting to open it again in SageMaker.

2. Split notebook file: Split large notebook files into smaller, more manageable files. This approach reduces overall notebook file size. Break the notebook file into smaller files such that each file is less in size.

3. Review your SageMaker notebook instance configuration: Ensure that your instance has sufficient resources (memory and storage) to handle the notebook. You might need to consider upgrading to a larger instance type if your current one is insufficient.

4. Contact AWS Support: If the issue persists after trying these steps, it would be advisable to contact AWS Support. They can provide more in-depth troubleshooting and potentially identify if this is a issue with the SageMaker service.