---
title: "Troubleshooting"
description: "Troubleshooting common Go Issues"
url: https://docs.sentry.io/platforms/go/guides/fiber/troubleshooting/
---

# Troubleshooting | Sentry for Fiber

## [Missing Source Context](https://docs.sentry.io/platforms/go/guides/fiber/troubleshooting.md#missing-source-context)

If your Go stack traces are missing source lines, the most common cause is that SCM Source Context isn't fully set up for the project.

Check that:

* your project has a supported SCM integration installed
* your code mappings point to the correct repository paths
* source context is enabled for the project
* the event is associated with a release or branch that Sentry can resolve through your code mappings

For the full setup, see [Source Context](https://docs.sentry.io/platforms/go/source-context.md).

## [Avoiding Temporary File Leaks In File Upload Handlers](https://docs.sentry.io/platforms/go/guides/fiber/troubleshooting.md#avoiding-temporary-file-leaks-in-file-upload-handlers)

Sentry's Go SDK middleware has to modify the request context in order to function correctly. This results in a shallow copy of the request being passed to upstream handlers. This means that temporary files created from calling `ParseMultipartForm` on this request won't automatically be cleaned up. It's important to clean these files up by calling `request.Multipart.RemoveAll()` after.

See the [multipart documentation](https://pkg.go.dev/mime/multipart#Form.RemoveAll) for more information.