---
title: "File uploads in a Passenger-backed application fail"
date: "2016-05-01"
category: "cgi-passenger"
slug: "file-uploads-in-a-passenger-backed-application-fail"
---

## Overview

File uploads in Ruby, Node, or Python applications running through [[passenger-supported-apps]] may fail due to a conflict with server-side upload screening. This has been confirmed in [RefineryCMS](http://www.refinerycms.com/), where uploads trigger a generic "undefined route" error.

![Example conflict in RefineryCMS. Following upload, RefineryCMS reports the route as undefined.](kb-image:refinerycms-upload-screening-conflict.png)
*RefineryCMS reporting an undefined route after a file upload attempt.*

## Cause

This is caused by a conflict between [[uploads-are-denied-with-406-not-acceptable]] and Passenger. Upload screening was introduced on April 6, 2016 to enhance server security, but it can interfere with Passenger-managed file uploads.

## Solution

Open a support ticket via the [[logging-into-the-control-panel]] to request that upload screening be disabled for your account. Once disabled, file uploads will complete normally.
