Troubleshooting

To view more logging for troubleshooting set LOG_LEVEL=debug in your environment variables, this will introduce many more logs that may be useful, this will also often be requested if you ask a question on the discussion forums.

HTTP → HTTPS redirect loop

During setup it can be useful to first get things working on http, if the browser is redirecting to HTTPS then there are two potential culprits:

Cannot edit documents

The wiki loads and you can create collections but documents appear to be uneditable. This is likely because your proxy is not allowing websocket connections through – websocket support is a requirement of Outline. See discussions for several ways this has been fixed in the past:

https://github.com/outline/outline/discussions/2222

Cannot access Postgres / Redis

If using Docker and you setup your Redis or Postgres on the host machine you could use additional flag --net="host" for docker. In this case you will be able to use localhost as host in your .env file for redis and Postgres.

EADDRINUSE

Something else is already using the port that Outline is trying to run on. You could change the port with the PORT environment variable or find the other service and kill it. It could also be another copy of Outline that is already running.

Error connecting to IDP with self-signed certificate

Please see the guide to using self signed certificates for details on how to make your root certificate authority available to the Outline container.

RangeError: Invalid key length

Your SECRET_KEY environment variable is not formatted correctly, follow the instructions in .env.sample carefully to ensure it is in the correct format and length.

Invalid Request (request has multiple authentication types, please use one) with Minio

The Outline authorization header is likely being passed Minio if it is on the same domain, this is decided by the browser and we have no control over it. The solution is to host Minio on a separate domain which will result in the headers not being forwarded.

Config could not be parsed

This issue is caused when a third-party modifies the HTML output in a manner that breaks Outline’s security policies and prevents scripts from being read correctly. Cloudflare Rocket Loader is often the culprit – the solution is to disable Cloudflare Rocket Loader, it is not necessary with Outline.

You can disable this feature for the whole site, or use a Configuration Rule to disable it on a specific hostname.